Dusk's own whitepaper update contains a line I didn't expect: Phoenix, the shielded transaction model, used to be an anonymity protocol — hiding the sender's identity even from the receiver. Dusk changed that. They added a way for the receiver to identify who sent a Phoenix transaction, and called it a shift from "anonymity" to "privacy." $DUSK #dusk @Dusk k did this specifically to stay compliant with EU rules.
What changed for me: that's not a UI toggle or an optional feature, it's a downgrade to the base guarantee of the flagship privacy model. Before, nobody could trace who paid whom, not even the person receiving funds. Now the receiver always can. The "privacy" branding survived; the anonymity property underneath it didn't.
It's a reasonable tradeoff for a chain courting regulated institutions. But it means Phoenix's confidentiality is narrower than the marketing implies — hidden from the public ledger, not from your counterparty.
Worth checking: whether third-party analytics or wallets already surface sender identity from Phoenix transactions in practice, or if that capability still sits unused.
What changed for me: that's not a UI toggle or an optional feature, it's a downgrade to the base guarantee of the flagship privacy model. Before, nobody could trace who paid whom, not even the person receiving funds. Now the receiver always can. The "privacy" branding survived; the anonymity property underneath it didn't.
It's a reasonable tradeoff for a chain courting regulated institutions. But it means Phoenix's confidentiality is narrower than the marketing implies — hidden from the public ledger, not from your counterparty.
Worth checking: whether third-party analytics or wallets already surface sender identity from Phoenix transactions in practice, or if that capability still sits unused.
