#dusk $DUSK @Dusk
"The Moment The Privacy Comes Off"
Privacy chains usually get judged on what they can hide. The more useful question is where the hiding has to stop, because that boundary tends to be documented plainly somewhere in the developer material rather than in the marketing.
On Dusk (@DuskFoundation) it shows up in two places. The deposit scanning page says the scanner intentionally accepts only direct Moonlight transfers, Moonlight being the public account model. The DuskEVM bridge guide tells you to unshield the amount needed for Dusk L1 bridge actions, and to keep enough unshielded DUSK on the Dusk L1 to pay for both the proof and finalization transactions.
I went in assuming ordinary fees forced the same exit. They don't. Phoenix pays its own gas from shielded notes, and the contract docs say the gas will always be paid in phoenix notes. Shielding survives normal use on the chain. It comes off at the regulated edges.
Dusk is open about why, which matters. The updated whitepaper says Moonlight was added because integration with exchanges would be simplified by a public transaction model, and that this approach keeps us compliant and removes any risk of being delisted. That is a deliberate design, stated in advance.
Which puts the weight on one legal sentence. AMLR Article 79(1), applicable 10 July 2027, prohibits credit institutions, financial institutions and crypto-asset service providers from keeping anonymous crypto-asset accounts, or any account otherwise allowing the anonymisation or increased obfuscation of transactions, including through anonymity-enhancing coins. The regulation never defines that last term. No official list exists, and neither the EBA nor AMLA has published a standard on it.
Kraken pulled Monero across the EEA on 31 October 2024. DUSK has not been touched.
So does exiting the shielded model before any regulated venue sees you read as the design working, or as the argument already conceded?
"The Moment The Privacy Comes Off"
Privacy chains usually get judged on what they can hide. The more useful question is where the hiding has to stop, because that boundary tends to be documented plainly somewhere in the developer material rather than in the marketing.
On Dusk (@DuskFoundation) it shows up in two places. The deposit scanning page says the scanner intentionally accepts only direct Moonlight transfers, Moonlight being the public account model. The DuskEVM bridge guide tells you to unshield the amount needed for Dusk L1 bridge actions, and to keep enough unshielded DUSK on the Dusk L1 to pay for both the proof and finalization transactions.
I went in assuming ordinary fees forced the same exit. They don't. Phoenix pays its own gas from shielded notes, and the contract docs say the gas will always be paid in phoenix notes. Shielding survives normal use on the chain. It comes off at the regulated edges.
Dusk is open about why, which matters. The updated whitepaper says Moonlight was added because integration with exchanges would be simplified by a public transaction model, and that this approach keeps us compliant and removes any risk of being delisted. That is a deliberate design, stated in advance.
Which puts the weight on one legal sentence. AMLR Article 79(1), applicable 10 July 2027, prohibits credit institutions, financial institutions and crypto-asset service providers from keeping anonymous crypto-asset accounts, or any account otherwise allowing the anonymisation or increased obfuscation of transactions, including through anonymity-enhancing coins. The regulation never defines that last term. No official list exists, and neither the EBA nor AMLA has published a standard on it.
Kraken pulled Monero across the EEA on 31 October 2024. DUSK has not been touched.
So does exiting the shielded model before any regulated venue sees you read as the design working, or as the argument already conceded?
