Crypto has a weird privacy problem,.. the moment someone needs to verify your money, you usually give them too much access.

That's what caught my attention about Phoenix's view key.

Phoenix separates viewing from spending. one key lets someone scan the network and find transactions meant for you. another key is what actually gives you control over the funds.

So you can give someone visibility without giving them the ability to spend.

what i find interesting is how far that separation goes.

@Dusk_Foundation also uses dedicated Prover nodes for the computationally heavy work of generating the ZK proofs required by Phoenix transactions. the computation can be delegated without handing over the authority that controls the funds.

That's a meaningful distinction from the usual wallet model, where access to information and access to assets tend to sit much closer together.

The real question for me is how granular that viewing power actually is.

what exactly can a view key holder reconstruct from the shielded transactions, and how much information can the owner choose to reveal?

$DUSK @Dusk #dusk