After spending some time going through the Phoenix design, one detail genuinely caught my attention:
privacy doesn’t necessarily mean doing every computation yourself.
The Dusk whitepaper describes a delegation model where some of the heavier work can be handed to a trusted third party without giving that party everything needed to spend your notes.
For network scanning, Phoenix uses view keys. A user can delegate the task of looking through the network for transactions addressed to them, while the delegated party still cannot spend those notes because it doesn't have the user's complete secret keys.
The second part is even more interesting.
Phoenix also allows the generation of ZK proofs for transactions to be delegated through signatures, while keeping the transaction's integrity intact.
So the design separates two things that are easy to confuse:
seeing enough to perform a task ≠ having enough authority to spend the funds.
That distinction matters in a privacy system.
Instead of making privacy dependent on one party holding complete control, the model divides responsibilities around what actually needs to be known or performed.
That’s probably the part of Phoenix I find most interesting: delegating computation without simply delegating ownership.
@Dusk $DUSK
#dusk
#dusk $DUSK @Dusk
privacy doesn’t necessarily mean doing every computation yourself.
The Dusk whitepaper describes a delegation model where some of the heavier work can be handed to a trusted third party without giving that party everything needed to spend your notes.
For network scanning, Phoenix uses view keys. A user can delegate the task of looking through the network for transactions addressed to them, while the delegated party still cannot spend those notes because it doesn't have the user's complete secret keys.
The second part is even more interesting.
Phoenix also allows the generation of ZK proofs for transactions to be delegated through signatures, while keeping the transaction's integrity intact.
So the design separates two things that are easy to confuse:
seeing enough to perform a task ≠ having enough authority to spend the funds.
That distinction matters in a privacy system.
Instead of making privacy dependent on one party holding complete control, the model divides responsibilities around what actually needs to be known or performed.
That’s probably the part of Phoenix I find most interesting: delegating computation without simply delegating ownership.
@Dusk $DUSK
#dusk
#dusk $DUSK @Dusk
