$DUSK docs and their Aug 15 piece on SME tokenization and one thing keeps nagging at me.
The dual transaction model Moonlight (public, account-based) and Phoenix (shielded UTXO + ZK proofs) is core to the whole pitch. Privacy is opt-in not default. That's actually the interesting part.
Moonlight exposes balances and transaction details openly, suited for compliance reporting and exchange integrations. Phoenix hides amounts, sender-receiver links, and balance changes behind cryptographic commitments and nullifiers.
But here's what I noticed digging through their Aug 15 post on private market workflows: the entire NPEX use case the €200M+ SME securities pipeline relies on selective disclosure for regulatory and servicing needs, not blanket privacy.
Meaning the actual "privacy" in production is tightly scoped, regulator-permissioned visibility, not what most crypto users picture when they hear "zero-knowledge."
What genuinely surprised me: 210M+ @Dusk_Foundation is staked securing the network (dusk) , yet DuskEVM and Hedger (the confidential EVM layer) are still on testnet. That's a large staking base propping up infrastructure that hasn't seen real institutional transaction volume yet.
I can't confirm what share of actual mainnet transactions are Phoenix vs. Moonlight right now the explorer shows tx types but not a clean breakdown I could pull quickly.
Makes me wonder: is privacy here really a feature for end users, or mostly compliance plumbing for the institutions? And does that distinction matter for where the network goes?
#dusk @Dusk
$ACE
$TUT
The dual transaction model Moonlight (public, account-based) and Phoenix (shielded UTXO + ZK proofs) is core to the whole pitch. Privacy is opt-in not default. That's actually the interesting part.
Moonlight exposes balances and transaction details openly, suited for compliance reporting and exchange integrations. Phoenix hides amounts, sender-receiver links, and balance changes behind cryptographic commitments and nullifiers.
But here's what I noticed digging through their Aug 15 post on private market workflows: the entire NPEX use case the €200M+ SME securities pipeline relies on selective disclosure for regulatory and servicing needs, not blanket privacy.
Meaning the actual "privacy" in production is tightly scoped, regulator-permissioned visibility, not what most crypto users picture when they hear "zero-knowledge."
What genuinely surprised me: 210M+ @Dusk_Foundation is staked securing the network (dusk) , yet DuskEVM and Hedger (the confidential EVM layer) are still on testnet. That's a large staking base propping up infrastructure that hasn't seen real institutional transaction volume yet.
I can't confirm what share of actual mainnet transactions are Phoenix vs. Moonlight right now the explorer shows tx types but not a clean breakdown I could pull quickly.
Makes me wonder: is privacy here really a feature for end users, or mostly compliance plumbing for the institutions? And does that distinction matter for where the network goes?
#dusk @Dusk
$ACE
$TUT