Understanding Mandates
The core primitive of financial authority: authorized budgets, per-tx limits, and lifecycle states.
What is a Mandate?
A Mandate is a legally and cryptographically binding contract between the user and the Mandate execution engine. It establishes the immutable financial perimeter within which autonomous agents are permitted to operate.
No agent, task, or objective can spend even a single yoctoNEAR without being attached to an active, non-expired mandate that has sufficient available budget.
Mandate Policy Parameters
The absolute maximum amount of NEAR the mandate can authorize over its entire lifetime.
The ceiling for any single transaction proposal. Any request exceeding this limit is rejected immediately.
Transactions below this execute autonomously. Transactions above this threshold are escrowed pending human review.
An explicit set of approved NEAR addresses. Transfers to any other recipient result in policy DENIAL.
Mathematical Accounting: Spent vs Reserved vs Available
Mandate tracks balance state using strict integer math in yoctoNEAR (1 NEAR = 1024 yoctoNEAR). Budget availability is governed by the invariant:
Mandate Lifecycle States
| State | Description | Can Spend? |
|---|---|---|
| active | Normal operating state; available budget can be allocated | YES |
| paused | Temporarily suspended by user; no new transactions permitted | NO |
| budget_exhausted | Authorized budget completely consumed or reserved | NO |
| expired | Mandate expiration date elapsed; terminal state | NO |
| revoked | Explicitly killed by user; all pending approvals canceled | NO |