One detail I kept coming back to while studying @Dusk is that it runs two live transaction models on the same chain rather than picking one and bolting privacy on later.
Phoenix is UTXO-based: funds exist as encrypted notes, and spending means proving — via zero-knowledge proofs — that a note is valid and unspent, without revealing sender, receiver, or amount on-chain. The trade-off is note discovery: a recipient has to scan the growing Merkle tree of note hashes to find what's theirs, which gets heavier as the tree grows.
Moonlight is account-based and public, closer to Ethereum: balances and nonces sit in the open. It's cheap to audit and simple for exchanges to integrate, but offers no confidentiality by default.
Phoenix protects transaction content, while Moonlight protects transaction simplicity.
Open question: as the note set scales, does client-side scanning stay practical without trusted indexing services quietly becoming a soft dependency for "self-custodial" privacy?
#dusk $DUSK #Dusk #DUSK
Phoenix is UTXO-based: funds exist as encrypted notes, and spending means proving — via zero-knowledge proofs — that a note is valid and unspent, without revealing sender, receiver, or amount on-chain. The trade-off is note discovery: a recipient has to scan the growing Merkle tree of note hashes to find what's theirs, which gets heavier as the tree grows.
Moonlight is account-based and public, closer to Ethereum: balances and nonces sit in the open. It's cheap to audit and simple for exchanges to integrate, but offers no confidentiality by default.
Phoenix protects transaction content, while Moonlight protects transaction simplicity.
Open question: as the note set scales, does client-side scanning stay practical without trusted indexing services quietly becoming a soft dependency for "self-custodial" privacy?
#dusk $DUSK #Dusk #DUSK
