Contracts
V2 brings proof-native contracts to mainnet at H210537. A contract holds NOID under a committed program and spending policy. The same recursive block proof that authenticates payments proves each contract transition. Users share one bounded core; they do not create a new proof system for each application.
Read From live value to live rights for the architectural idea. This section explains how to build and use it.
| Task | Guide |
|---|---|
| Understand terms, deposits, calls and successors | Lifecycle and mechanics |
| Review instructions, counters and authorization | Integer core and ABI |
| Choose a ready-made policy | Six templates |
| Integrate an application or use the CLI | API and integration |
| Create, share and use contracts in the wallet | GUI walkthrough |
| Exchange receipts or recover after being offline | Receipts and recovery |
Activation and capacity
The v2 release understands the contract API before activation. Public terms can
be prepared and shared then; funding and calls require the next candidate
block to use v2. Check getContractProtocol.active_at_next_block together
with runtime_available. Installing the binary does not activate new consensus
rules early. Existing v1 → v1.1 behavior remains unchanged.
| V2 class | Pages | Live inputs | Contract calls |
|---|---|---|---|
| Small, m23 | 63 | 504 | 63 |
| Large, m24 | 206 | 504 | 63 |
Calls and payments share page space. A call uses one page and one live input; an ordinary payment may use several pages and inputs. Small can hold 63 calls or 63 one-page payments. Large can hold 63 calls plus 143 one-page payments, subject to the common 504-input budget. The primary coinbase is separate; an additional mandatory system page takes one page from these budgets.
What to keep
The chain authenticates the current commitment and value. Keep your wallet secret, public contract terms and any receipts you need. A secret alone cannot recreate an arbitrary program or missed counter updates. The wallet discovers locally watched successors and merges received evidence without replacing its own journal. A shared contract file carries terms and at most one matching receipt, rather than a complete archive of all participants' actions.
Saving unfunded terms is free. Funding and calls have their own network fees. Call fee limit is the policy ceiling for a future call, not a creation fee.