Notes and funding
A Note is a private credential for one asset. The application retains its amount, owner, randomization and recovery material. The chain records a commitment; spending verifies membership and registers a nullifier to prevent reuse.
Three fund paths
Public funding: Shield
shield accepts 1–10 public-amount outputs without a ZK proof or old Note inputs. Funding sources and amount-related information are public. Funds enter the instance and Note commitments are inserted only on successful execution. Constructing an encrypted output alone does not fund it.
Private settlement: Transact
transact can consume Notes, add public funding, create new Notes or withdraw to a public address. Each request handles one token. SDK amounts are integers in token base units.
input Notes + public funding
= output Notes + public withdrawal + same-token service fee
Every selected input is fully consumed. A partial payment needs a change Note; the original Note is not reduced in place. Inputs from different trees require the corresponding membership roots and paths.
Full sweep to the original owner
A holder of a complete Note opening or viewing material capable of recovering it can prove a full withdrawal to its original owner without a free-spending owner signature. This path cannot create private change, add funding, change the recipient or deduct a fee from the credential.
Full disclosure therefore differs from conventional read-only access. A disclosure recipient cannot redirect the money but can reveal the withdrawal amount, affect its timing and compete with a pending owner transaction.
Funding authorization
| Material | Purpose | Does not replace |
|---|---|---|
| ERC-20 allowance / Permit | Allows a token transfer | Authorization of a specific payment |
| Direct payer call | Lets the actual payer submit constrained funding | Authority for another caller to pull arbitrary payer funds |
| Separate funding signature | Allows a relay to execute bound funding terms | Private Note spending authorization |
| Wallet authorization | Binds private terms, destinations, fees and deadline | ERC-20 allowance or network gas |
Core checks the actual received token delta. Do not treat fee-on-transfer or rebasing tokens as ordinary exact-receipt assets. Simulation cannot guarantee later execution.
From output intent to spendable funds
- Construct the output from complete receiving material; verify chain, instance, token and base-unit amount.
- Execute the funding or private spending operation.
- Authenticate the delivery and match its commitment and actual tree position to a successful canonical receipt.
- Verify membership and current consumption, and reconcile local reservations.
An accepted historical root does not establish that a Note is unspent. Distinguish received amounts, discovered inventory and available balance. Read session synchronization and recovery.