Privacy Without Losing Practical Usability.

Privacy on a blockchain becomes difficult when protecting information also makes the system difficult to use verify or integrate.

Dusk approaches this problem by making different transaction visibility levels part of the network’s architecture.

Its Moonlight model provides public account based transactions. Balances public addresses and transaction activity can remain transparent which is useful when visibility and straightforward verification are required.

Phoenix takes the opposite approach when transaction confidentiality is important. It uses shielded UTXO based transactions built around notes nullifiers and zero knowledge proofs. The network can verify that the transaction is valid without exposing the sender receiver or transferred amount publicly.

But privacy in Phoenix is not simply about hiding information from everyone. The protocol includes view keys allowing users to identify transactions addressed to them while keeping spending authority protected. The whitepaper also describes how view keys can allow delegated transaction scanning without giving the delegated party the ability to spend the notes.

That distinction is important for practical financial infrastructure confidentiality does not necessarily mean abandoning controlled access to information.

For @Dusk privacy is therefore better understood as a configurable property of transactions rather than an obstacle to usability.

$DUSK #dusk


Could selective visibility become the more practical model for blockchain finance than choosing between complete transparency and complete anonymity?