#dusk $DUSK @Dusk
Went looking for where Dusk actually implements "reveal to authorized parties." Found something smaller than the phrase implies. Every Phoenix note has an owner, and that owner holds a View Key. Share it, and whoever's holding it can now detect every output belonging to you — plus decrypt the value on obfuscated notes. That's the access-control layer. Full stop.
$DUSK #dusk @Duskfoundation — as far as I can tell from the key's own spec, it's just a scalar and a point. No role field, no scope, no expiry baked in. Nothing that would let the chain treat a regulator differently than a business partner or a curious ex-employee. If that distinction exists, it's not in the key itself.
What changed for me: "selective disclosure" reads like a policy feature. What's actually there is key custody. The protocol hands owners a lever — share or don't — not a permissions engine. Whether the right party gets that key, for the right reason, is a process question sitting entirely off-chain.
Next thing I want to check: does sharing a View Key expose an owner's full note history in one shot, or can Dusk scope it to a single transaction? Right now the docs read all-or-nothing, but I want that confirmed against the actual wallet implementation, not just the architecture page.
Went looking for where Dusk actually implements "reveal to authorized parties." Found something smaller than the phrase implies. Every Phoenix note has an owner, and that owner holds a View Key. Share it, and whoever's holding it can now detect every output belonging to you — plus decrypt the value on obfuscated notes. That's the access-control layer. Full stop.
$DUSK #dusk @Duskfoundation — as far as I can tell from the key's own spec, it's just a scalar and a point. No role field, no scope, no expiry baked in. Nothing that would let the chain treat a regulator differently than a business partner or a curious ex-employee. If that distinction exists, it's not in the key itself.
What changed for me: "selective disclosure" reads like a policy feature. What's actually there is key custody. The protocol hands owners a lever — share or don't — not a permissions engine. Whether the right party gets that key, for the right reason, is a process question sitting entirely off-chain.
Next thing I want to check: does sharing a View Key expose an owner's full note history in one shot, or can Dusk scope it to a single transaction? Right now the docs read all-or-nothing, but I want that confirmed against the actual wallet implementation, not just the architecture page.