Contracts

Every contract ARKZ runs on chain, and every third-party contract it uses, with its address, its source verification status and its block explorer record. The table below is read from the same public record as the On chain page. No address on this page is typed by hand.

The contracts

Each row links to the contract's page on the block explorer. Where the source is verified, the source link opens the verified code and its ABI, published by the explorer from the deployed bytecode. While no chain is active, the table says so plainly and lists nothing.

What the public set covers

The contracts ARKZ deploys are one fixed set, named in one list that the deploy, the rehearsal and this page all read. A contract outside that list is never deployed, verified or listed here.

• Keys. The Genesis Key, its round schedule and the Master Key, with the ownership policies that govern their transfer.
• The Key account and its items. An ERC-6551 account for each Key, the items it holds, and the personal capsules earned by building.
• Derivatives and licences. ARK Master, ARK Editions and ARK Licence, with the royalty splitters that pay creators on resale (ERC-2981).
• Proof. Content Certificates, the Passport, the Deed and the Passport mover.
• Payments. The payment router, the Key bundle settlement and the Covenant auction. Payments settle in USDC, straight from the buyer's wallet to the seller's wallet and the platform fee in one transaction, and the asset is delivered in that same transaction or nothing moves.
• Agents. The agent registrar, which registers derivatives in the ERC-8004 registries.
• Points. The points epochs contract, which records one Merkle root for each closed epoch.

Third-party contracts the set uses are listed beside it: USDC, the ERC-6551 account registry and the two ERC-8004 registries. ARKZ does not deploy them.

How the set is governed

• Nothing is upgradeable. A contract's code never changes after it is deployed. New behaviour arrives as a new contract.
• A timelock holds the admin roles. A change of role or setting waits 48 hours in public before it can run.
• Operational keys are separate. The minter, the signers, the move approver and the pause guardian are different keys, and the rehearsal checks who holds each role before a deploy is accepted.
• Contracts that move value can be paused while an incident is examined.

Source and tests

Every contract is built and tested in a Foundry project, and the deploy is rehearsed end to end on Base Sepolia before it reaches Base. A public mirror of the set's source, tests and deploy records is being prepared; it is linked here once it is published. Audit reports are listed under Security.