#dusk $TAC $SPK $DUSK @Dusk
i keep thinking if my wallet already passed the KYC side
for an Dusk XSC security, then that should basically be the annoying part done.
like okay. the Dusk zero-knowledge proof already satisfied the holder requirement, my identity doesnt need to sit there publicly, and DuskVM has enough from that proof to satisfy that XSC condition.
so why would the XSC still stop me?
apparently because “allowed holder” isnt one giant yes.
the Dusk Confidential Security Contract can still care about what happens after i receive the security. maybe my wallet already qualifies as a holder, but this exact transfer pushes me past the shareholder limit written around that XSC.
and thats where i keep tripping over it.
i was treating Dusk KYC like permission for the whole security, when really it only answered whether my wallet could qualify as a holder. it still didnt answer whether this exact amount leaves me inside the Dusk XSC ownership limit.
so i can pass one rule and still fail the transfer anyway.
DuskVM can already have the zero-knowledge proof for the holder requirement and still not move that XSC ownership because the shareholder-limit condition is sitting there unsatisfied.
which makes “verified” feel way less complete than i thought.
and until that limit fits too, there isnt an XSC ownership change for DuskDS to make final on Dusk L1.
so apparently i can already be a valid Dusk XSC holder.
and still be the wrong receiver for this exact amount.
that part still feels backwards.
i keep thinking if my wallet already passed the KYC side
for an Dusk XSC security, then that should basically be the annoying part done.
like okay. the Dusk zero-knowledge proof already satisfied the holder requirement, my identity doesnt need to sit there publicly, and DuskVM has enough from that proof to satisfy that XSC condition.
so why would the XSC still stop me?
apparently because “allowed holder” isnt one giant yes.
the Dusk Confidential Security Contract can still care about what happens after i receive the security. maybe my wallet already qualifies as a holder, but this exact transfer pushes me past the shareholder limit written around that XSC.
and thats where i keep tripping over it.
i was treating Dusk KYC like permission for the whole security, when really it only answered whether my wallet could qualify as a holder. it still didnt answer whether this exact amount leaves me inside the Dusk XSC ownership limit.
so i can pass one rule and still fail the transfer anyway.
DuskVM can already have the zero-knowledge proof for the holder requirement and still not move that XSC ownership because the shareholder-limit condition is sitting there unsatisfied.
which makes “verified” feel way less complete than i thought.
and until that limit fits too, there isnt an XSC ownership change for DuskDS to make final on Dusk L1.
so apparently i can already be a valid Dusk XSC holder.
and still be the wrong receiver for this exact amount.
that part still feels backwards.
