I used to think privacy on a blockchain meant the user had to handle everything themselves, but one detail in Dusk’s Phoenix model made me look at that differently. @Dusk allows intensive computations to be delegated to trusted third parties, including scanning the network for transactions addressed to you using a view key and even generating ZK proofs, while the delegated party still cannot spend your notes because it does not have your complete secret key. That separation is more interesting than it first sounds. It suggests that private blockchain activity doesn’t necessarily have to mean every user performs every expensive computation locally. You can delegate the heavy work while keeping the authority to spend your assets under your control. For financial applications, where usability and privacy both matter, that distinction could become important if these systems have to serve people who are not cryptography experts. The question I’m left with is: would you trust secure delegation for private transactions, or would you prefer to keep every computation under your own control? $DUSK #dusk

$EDEN
$RED