zecpadApprovals and execution
See which actions are automatic, which require approval and when funds are considered spent.
Who approves each action?
| Action | Authorization |
|---|---|
| Create a token | The creator signs with the connected wallet. |
| Finalize creator-fee routing | The creator separately signs and the destination is verified. |
| Optional developer buy | The creator separately approves the purchase. |
| Scheduled fee collection | The treasury signer acts after routing, funding and worker checks pass. |
| ZEC Rewards payouts | An operator must approve the planned payout jobs. |
| Protocol buybacks | Require separate operator approval and execution checks. |
From available funds to confirmation
- A verified receipt makes attributable funds available in the market’s ledger.
- Planning checks the mode, eligible capital and any required finalized snapshot.
- Funds assigned to a job are reserved so another job cannot spend them.
- The required operator approval and execution safety checks must pass.
- The treasury signs and submits the operation, with its signature recorded for reconciliation.
- Only verified execution evidence makes the operation completed or paid.
Why an operation can wait
Jobs can wait for an epoch end, approval, fresh chain data, liquidity or operational SOL. A paused market or unsupported route can also block a new operation.
A known signature is checked before another transaction is attempted. This avoids treating a timeout as proof of failure and submitting the same payment twice.
Connecting a wallet does not grant administrative access. Operator access and approvals are separate from public wallet connection.
Collection is not blanket spending approval
Automatic collection transfers earned fees into the treasury under the verified route. It does not authorize every possible distribution or buyback.
Shield Reserve retains its allocation without automatic holder payments. ZEC Rewards needs its eligibility checks and individual payout approvals.