#Dusk $BTW $DUSK @Dusk

i keep thinking the weird part of using Moonlight in a Dusk trade is not even that the DUSK payment can be public.

it’s that the payment can be sitting there completely readable while the XSC ownership side is still refusing to expose the holder behind it. and my brain keeps trying to make those two disclosure levels match because... same trade, right? same Dusk L1, same outcome.

except apparently not.

Moonlight can move the public DUSK through the Transfer Contract into the DuskVM side of the trade, where the XSC ownership change still has its own disclosure rules.

but the Confidential Security Contract has a different problem.

can this Dusk wallet actually become the next holder?

and that’s where selective disclosure starts feeling less like “hide everything” and more like... prove this one thing and keep the rest out of it. prove the wallet satisfies the XSC holder condition without dragging the investor identity into public Dusk state.

but if DuskDS still has to settle the XSC ownership result anyway... why does it need the holder result but not the whole identity behind it?

so wait... what actually becomes public here? the Moonlight payment, sure. eventually the fact that the XSC ownership change was accepted too. but the holder information behind that XSC eligibility proof doesn’t have to follow the result all the way into DuskDS.

“same trade. different things allowed to become visible.”

and idk maybe that’s what i was getting wrong.

Moonlight making the DUSK side public never meant the whole Dusk trade became public with it.

the XSC holder can still stay behind the eligibility proof even after DuskDS settles what that proof allowed.