#dusk $DUSK @Dusk At first I thought Phoenix worked like most shielded systems, where the proof checks the math and encryption separately hides who did what, but looking closer at how Dusk's Phoenix actually verifies a transaction, that separation doesn't exist at all. Note ownership, sender authorship, and balance correctness aren't checked outside the proof and then hidden afterward, they're encoded inside the same circuit that proves the transaction is valid in the first place, and that changes what verification even means here, because the network isn't checking a visible transaction and then choosing to mask it, it's checking a proof that was never carrying visible data to begin with, and that proof is enough on its own to confirm nothing was double spent, nothing was forged, and the sender actually owns what they're moving, so nobody needs to see the note to trust that it settled correctly, correctness and visibility stop being tied together, which is a strange thing once you sit with it since you're used to trusting things because you can see them. What I keep coming back to is what that does to compliance on @Dusk , because if visibility isn't required for correctness, then disclosure through a viewing key isn't unlocking hidden truth, it's granting permission to look at something that was already settled and already verified, so the question moves from "can this be proven" to "who gets allowed to see it," which is less a cryptography problem and more a governance one, decided by whoever controls the key, not by the protocol itself. So when a regulator or exchange holds a viewing key and checks a transaction on Dusk, are they actually verifying anything the chain hadn't already verified on its own, or are they just being let into a room that was locked for everyone else? #Dusk