nk, ivk, and the
other keys used below.
The commitment
The note commitment is the Poseidon2 hash of the note opening in this canonical order:The fields
The proof for each action binds the opening to the action’s public values
and input notes. A different value produces a different commitment and fails
the proof.
The opening
The eleven fields form the note opening. During a shielded payment, the sender delivers the recipient note opening in an encrypted note memo addressed to the recipient’s incoming viewing key. The recipient wallet or a VASP with delegated viewing access recomputes the note commitment and compares it with the payment effect fixed at initiation. Shield and change note openings remain with their key holders.Spending a note
Spending requires the ownership and authorization checks. Each note has a nullifier derived from its nullifier key and position in the commitment tree: is the note’s position in the tree. During payment initiation, the nullifier remains sealed in the payment effect hash while the input lock ID reserves the note. The pool records the nullifier in the spent set when anAccept resolution or unshield spends the note. An nk holder
who knows the note’s leaf index can connect its nullifier to its commitment;
the public nullifier does not
reveal the diversified address.
What the chain sees
Proofs read the opening and bind it to the public note commitment. The
capability lattice
defines which key bundles can recognize or spend notes, including the MIP410
authority’s regulatory viewing access.