I used to think a private blockchain transaction meant hiding information from the network.
Then Phoenix made me question what “verification” actually requires.
Dusk uses encrypted notes and zero-knowledge proofs, so a transaction can be verified without exposing the sender, receiver or amount.
The interesting part isn't simply that those details are hidden.
It's that the network can establish “this is valid” without first learning “this is what happened.”
I had been putting those two questions in the same box.
They're not the same requirement.
Phoenix still gives the network what it needs to verify the transaction, while the underlying financial details remain private.
The proof becomes visible where the transaction itself doesn't have to be.
@Dusk_Foundation
$DUSK #dusk
Then Phoenix made me question what “verification” actually requires.
Dusk uses encrypted notes and zero-knowledge proofs, so a transaction can be verified without exposing the sender, receiver or amount.
The interesting part isn't simply that those details are hidden.
It's that the network can establish “this is valid” without first learning “this is what happened.”
I had been putting those two questions in the same box.
They're not the same requirement.
Phoenix still gives the network what it needs to verify the transaction, while the underlying financial details remain private.
The proof becomes visible where the transaction itself doesn't have to be.
@Dusk_Foundation
$DUSK #dusk