Records · Audit

Every contract, and who controls it

The directory lists every contract in the AXON design: its address or "not deployed", its owner, its delays, and who can mint, pause or spend. This page is not an audit. It shows what anyone can check.

Contract directory

4 of 40 contracts are deployed on Ethereum Sepolia testnet. Owners and live values are on-chain · block 12177971. "Today" is what the code allows as written; "Designed" is doc/ownership's plan, not live.

Layer 1: AXON utility

ContractStatusAddress and ownerTodayDesigned
AxonToken (AXON)
The AXON utility token, an ERC-20.
deployed 0x20F1…b712
owner 0x5329…cce1
Total supply: 1,000,000 AXON
Genesis minted: 1,000,000 AXON
Genesis closed: no
Minter (treasury): 0xb684…ec9e
  • The owner can mint while genesis is open (mintGenesis).
  • The owner can name or change the only minter at any time (setTreasury).
  • The minter can mint, and burn only what it holds itself. The token itself sets no cap.
  • Nothing can be paused. Nothing can be upgraded.
  • Owner becomes Timelock P.
  • setTreasury, mintGenesis and closeGenesis take a 30-day constitutional delay.
  • After that, new AXON comes only from Treasury.fundEpoch, under the epoch budget and the supply cap.
Delay: 30 days for supply changes (designed). Pause: No. The token is deployed and immutable.
AxonChannels
Payment channels between two parties.
deployed 0x7430…03bD
  • No owner. It has no privileged functions.
  • Unchanged.
Pause: No.
AXON Treasury
AXON supply controller and sale inventory. It is not an entity treasury.
not deployed not deployed
  • Anyone can call fundEpoch. It mints a finalized epoch's rewards, up to the epoch budget and the supply cap.
  • The owner can release (naming a purpose), releaseOrder, burn and rescue.
  • The owner can change the epoch budget at most 2x up or down, once per 30 days.
  • Only the RewardDistributor can call burnUnclaimed, which burns an epoch's swept rewards in the same transaction.
  • Owner becomes Timelock P (14-day protocol-treasury class), so every release waits in public, tagged with its purpose.
  • Card and compute deliveries come from OrderDesk.deliver, not releaseOrder: with Timelock P as owner, the site's key cannot call it.
  • Renters' deposits go to ServiceEscrow. Swept rewards are burned, never added to the inventory.
Delay: 14 days (designed). Pause: No.
OrderDesk
A small AXON float for card purchases, compute payouts, refunds and small grants.
not deployed not deployed
  • The deliverer key can deliver from the float only, once per order id, at most perOrderMax per order and perDayMax per UTC day.
  • Each delivery names its kind: purchase, compute payout, refund or grant.
  • The admin sets the limits, returns float to the AXON Treasury, unpauses and grants roles.
  • A pauser can pause deliveries. It cannot unpause.
  • The deliverer is the site's hot key. Admin: Timelock P, which also refills the float by a purpose-tagged release.
  • The guardian pauses, through GuardianTerm, while its term lasts. Only Timelock P unpauses.
Delay: 14 days for limit changes (designed). Pause: Deliveries only, by the guardian.
ServiceEscrow
Holds renters' compute deposits apart from the Treasury.
not deployed not deployed
  • The settler key can hold a renter's funds only with the renter's signature over that job, amount and expiry.
  • It can settle a hold, before the hold expires and for at most its amount, to the provider and the revenue recipient. It never touches a free balance.
  • A renter can withdraw a free balance at any time, and release an expired hold.
  • The admin names the revenue recipient, unpauses and grants roles. A pauser can pause deposits and holds.
  • The settler is the site's key. Admin: Timelock P. The revenue recipient is the entity's revenue Safe, which does not exist yet.
  • The guardian can pause new deposits and holds, through GuardianTerm. Withdrawals are never paused.
Pause: Deposits and holds only. Withdrawals are never paused.
RewardDistributor
Merkle claims of epoch rewards by node operators.
not deployed not deployed
  • Claims are bounded by what the Treasury minted for the epoch, and never exceed its total.
  • After an epoch's claim period, anyone can sweep that epoch's unclaimed rest. It is burned in the same transaction: AXON supply falls, and the Treasury's inventory does not rise.
  • The owner can only wire the NodeRegistry and the Treasury, once each.
  • Owner becomes Timelock P.
  • Unchanged otherwise. Nobody chooses when, how much or where a sweep goes.
Pause: No.
StakeVault
AXON bonds, delayed withdrawal, holds and slashing.
not deployed not deployed
  • The owner can appoint any slasher. A slasher can slash any bond, including stake waiting to withdraw.
  • The owner appoints lockers. A locker holds a bond while an epoch or a dispute can still slash it, and nothing leaves through withdraw while a hold is open.
  • The owner can set the withdrawal delay, between 1 and 30 days.
  • Owner becomes Timelock P, so a new slasher or locker waits out a delay in public.
  • Lockers: EpochManager, from submission until the epoch is final, and DisputeManager, from a challenge until its verdict.
Delay: 7 days (designed). Pause: No.
NodeRegistry
Links a wallet to a node identity and counts infrastructure units.
not deployed not deployed
  • The owner can set the activity recorder, once. It has no power over nodes.
  • Owner becomes Timelock P.
  • Each paid node counts as one unit, with history kept for snapshots.
Pause: No.
EpochManager
Epoch roots, the challenge window and the randomness beacon.
not deployed not deployed
  • The owner can allow-list aggregators. An aggregator must keep the aggregator bond in StakeVault, held until its epoch is final.
  • The owner can set the challenge window, never below 12 hours, and the aggregator bond.
  • Owner becomes Timelock P.
Delay: 7 days (designed). Pause: No. The dispute freeze is its brake.
DisputeManager
Bonded challenges and the 7-of-11 witness quorum.
not deployed not deployed
  • The owner decides disputes below the high-value threshold, and high-value ones only when the witness quorum cannot.
  • A dispute can slash only the epoch's submitter, at most the epoch's total rewards. Half goes to the challenger, the rest to the AXON Treasury.
  • Anyone can sweep forfeited bonds and the Treasury's slash share, only to the AXON Treasury.
  • Owner becomes Timelock P.
Delay: 7 days (designed). Pause: No.
ServicePolicyRegistry
Versioned reward split per service.
not deployed not deployed
  • The owner sets and schedules policy versions.
  • Owner becomes Timelock P (7-day parameters class).
Delay: 7 days (designed). Pause: No.
SettlementKeeper
A small ETH bounty for finalizing epochs.
not deployed not deployed
  • The owner sets the bounty (at most 0.05 ETH) and can withdraw.
  • The Operations Safe, through Timelock P.
Pause: No.
AxonRegistry (names)
Names in one namespace.
not deployed not deployed
  • The governor can prune, seize and restore names.
  • Fees go to a fixed address set at deployment.
  • Governor becomes Timelock P. Fees go to an interim revenue Safe.
Delay: 2 days for content actions (designed). Pause: No.
TLDRegistry (namespaces)
The root zone of namespaces.
not deployed not deployed
  • A governor and an expiring guardian, with timelock floors built in.
  • Governor becomes Timelock P. Guardian becomes the Guardian Safe.
Pause: A guardian freeze, built in.

Network software

ContractStatusAddress and ownerTodayDesigned
ReleaseRegistry (software releases)
The update channel for dendritic-node and anonymOS: each release's version, SHA-256, size and storage-network id. Nodes install a release only if the bytes they fetched match it.
not deployed not deployed
  • The publisher publishes releases. Nodes ignore each one until its activation time, at least the minimum delay after publishing and never less than 1 hour.
  • The publisher and the guardian can revoke a release at once. Nodes then return to the previous release. The guardian can also pause publishing.
  • The owner names the publisher and the guardian, sets the minimum delay and unpauses. Nobody can edit or delete a release, and a version number is never reused.
  • Publisher: the Operations Safe. Guardian: GuardianTerm, for the Guardian Safe, until its term ends. Owner: Timelock P from deployment.
  • Naming the publisher or the guardian is constitutional (30 days). The minimum delay and unpausing are parameter changes (7 days).
Delay: 1 hour before a release activates; 30 days to change the publisher (designed). Pause: Publishing only, by the guardian. Revoking a release is never paused.

Layer 2: contribution points

ContractStatusAddress and ownerTodayDesigned
ContributionPolicy
The versioned scoring policy: categories, budgets, caps, review panels and windows.
not deployed not deployed
  • The policy admin sets new versions and schedules them, for future periods only. A version never changes once set.
  • Through the ordinary path, a category's budget moves at most 5 points per quarter. The constitutional path skips that limit.
  • No function takes an account, and no field is an AXON balance.
  • Policy admin: Timelock P. The ordinary path is the parameters class (7 days), the constitutional path 30 days.
Delay: 7 days, or 30 for a constitutional change (designed). Pause: No.
ConflictRegistry
Declared affiliation groups, so reviewers are not drawn for their own group's work.
not deployed not deployed
  • No owner. Only an account can declare or leave its own group, and leaving takes 30 days.
  • Unchanged.
Pause: No.
ContributionRegistry
Contribution records and their review lifecycle, from submission to final.
not deployed not deployed
  • Validators, appointed by the admin, attest the automated checks. Drawn reviewers decide by signed verdicts.
  • Reviewers are drawn from the policy's published pool, never weighted by points, and never from the contributor's own group.
  • The admin unpauses, names the guardian and grants roles. The guardian can pause submissions and appeals until its term expires.
  • No function awards points to a named account. Forfeited appeal bonds go to the AXON Treasury.
  • Admin: Timelock P. Scoring changes go through ContributionPolicy and apply to future periods only.
Delay: 7 days for policy (designed). Pause: Submissions and appeals, by the guardian. Finalizing a decided record is never paused.
ReputationLedger
Contribution units per period, their scoring into points, and the non-transferable points balance.
not deployed not deployed
  • Only ContributionRegistry adds or revokes record units. It is wired once.
  • Anyone can import a finalized epoch's infrastructure units, seal a period after its end, and credit an account's points as ContributionPolicy computes them.
  • There is no transfer, approve or mint-to function. Points move only by an account rotation, signed by both keys or requested by the recovery admin, after 30 days.
  • Recovery admin: Timelock P.
Pause: No. Imports wait while ContributionRegistry is paused.

Governance

ContractStatusAddress and ownerTodayDesigned
AxonGovernance
Content governance: names, by contribution-weighted vote.
not deployed not deployed
  • No owner. The names registry, the weight source, the class table and Timelock P are fixed at deployment.
  • Weight is read at a snapshot. A passed prune, seize or restore is queued on Timelock P. Jurisdictional categories are refused.
  • Unchanged. A different weighting means a new deployment and a constitutional proposal.
Delay: 2 days for content actions (designed). Pause: No.
ContributionVotes
One voting weight for both governors, and delegation.
not deployed not deployed
  • No admin. The four sources and the 40/30/20/10 split are fixed at deployment.
  • It only reads the weight sources at a past time and records delegation.
  • Unchanged.
Pause: No.
ProtocolGovernor
Contribution-weighted decisions on protocol parameters.
not deployed not deployed
  • A proposal's class is the strictest among its calls in ProposalClasses. An unlisted call is constitutional.
  • Every passed call runs only through Timelock P, after its class delay. Content actions are refused.
  • The guardian can mark interested parties on a pending proposal until its term expires. Their votes are recorded, not counted.
  • Proposer on Timelock P once the bootstrap proposer stops.
Pause: No.
AIPRegistry
Axon Improvement Proposals: the on-chain registry and lifecycle of network-change proposals.
not deployed not deployed
  • Anyone may create an AIP; the author advances it through the early stages and may revise or withdraw it.
  • An owner-set reviewer records technical-review outcomes; owner/governance gates acceptance, scheduling and activation.
  • A category needing a DAO vote cannot be accepted until its linked ProtocolGovernor proposal has passed. Spec text lives off-chain, anchored on chain by hash.
  • Unchanged.
Pause: Yes, by the guardian: it stops new proposals; lifecycle reads stay open.
ProposalClasses
Which class each call is, and what each class needs: threshold, quorum, majority, coverage, delay.
not deployed not deployed
  • The owner can change a class's parameters, any call's class, and the class of granting a role. A call nobody listed is in the strictest class.
  • Owner: Timelock P. Its own setters are unlisted, so changing the table is constitutional (30 days).
Delay: 30 days (designed). Pause: No.
BootstrapProposer
Lets the Operations Safe queue calls on Timelock P until governance can, then stops for good.
not deployed not deployed
  • The operator can queue calls on Timelock P, each at least its class delay. An unlisted call waits the constitutional delay.
  • It stops at its sunset date, when the operator ends it, or once governance coverage holds for a week.
  • Only Timelock P can change its delays (per call, and per role a call grants) or name the coverage source.
  • Everything it queues waits in Timelock P, where the guardian can cancel it.
Delay: the class delay of each call. Pause: No.
GuardianTerm (Timelock P)
The guardian's powers on Timelock P, the pausable contracts and the release channel, for a fixed term.
not deployed not deployed
  • The guardian can cancel a queued operation, pause intake and revoke a software release, nothing else, and only until the term expires.
  • Only Timelock P can renew the term, at most 365 days ahead, or name a new guardian.
  • The guardian is the Guardian Safe.
Pause: No.
Timelock P (protocol)
The delay on every protocol owner action.
designed, not live not deployed
  • OpenZeppelin's TimelockController, unmodified. Proposers queue, cancellers cancel, and anyone executes once the delay has passed.
  • Proposers: BootstrapProposer until it stops, then the two governors.
  • Canceller: the guardian, through GuardianTerm, whose term expires.
  • Minimum delay 2 days. Each proposal class adds more.
Delay: 2 to 30 days by class (designed). Pause: No.
Timelock O (ownership)
The delay on every ownership-layer action.
designed, not live not deployed
  • OpenZeppelin's TimelockController, unmodified. Proposers queue, cancellers cancel, and anyone executes once the delay has passed.
  • Proposer: EntityProposer, for the entity approvers' Safe, at each call's class delay.
  • Cancellers: the guardian through GuardianTermO, and the entity approvers.
  • Minimum delay 7 days.
Delay: 7 to 30 days (designed). Pause: No.
InfrastructureWeightSource
Infrastructure units from NodeRegistry, read at a past time, for voting weight (40%).
not deployed not deployed
  • No owner functions.
  • Unchanged.
ContributionWeightSource
Decayed governance points from ReputationLedger, read at a past time, for voting weight (30%).
not deployed not deployed
  • No owner functions.
  • Unchanged.
ParticipationWeightSource
Evidence-backed voting participation, for voting weight (20%).
not deployed not deployed
  • The admin names the recorders. Only they record a vote, at most 10 per voter.
  • Recorders: the two governors.
StakeWeightSource
Active StakeVault bonds, read at a past time, for voting weight (10%).
not deployed not deployed
  • No owner functions.
  • Unchanged.

Layer 3: legal ownership (gated on counsel)

ContractStatusAddress and ownerTodayDesigned
OwnershipRegistry
A mirror of a legal entity's ownership register.
not deployed not deployed
  • Whether it is a simulation is fixed at deployment. No legal entity exists.
  • The issuer records grants from an activated round, within pool caps and authorized units.
  • The registrar forfeits unvested units, cancels and reissues grants, and records legal transfers. The registrar's Safe attests register versions and holder eligibility.
  • It has no transfer function and takes no AXON address.
  • On a testnet it may run only as a simulation, with synthetic holders.
  • Issuer: OwnershipAllocator. Registrar and admin: Timelock O, where the guardian can cancel.
Delay: 7 to 30 days (designed). Pause: No.
gated on counsel
OwnershipAllocator
Turns an approved, timelocked round into register entries.
not deployed not deployed
  • Anyone proposes a round and anyone may dispute its inputs during review.
  • The approvers approve after review. Only Timelock O activates, and only then can a round's entries be recorded, within its caps.
  • It holds no role on any AXON or contribution contract.
  • Approvers: the entity approvers' Safe.
Delay: 7 days after approval (designed). Pause: New rounds and entries, by the guardian.
gated on counsel
DistributionManager
Pays a legally declared distribution to holders of record.
not deployed not deployed
  • Only Timelock O declares and funds. An approver posts the entitlements. The guardian can cancel before funding.
  • Claims can never exceed the funded amount. It never pays in AXON.
  • Approver: the entity approvers' Safe.
Delay: 7 days each for declare and fund (designed). Pause: New entitlements and funding, by the guardian. Claims of a funded distribution are never paused.
gated on counsel
EntityClasses
Timelock O's class table: 7 days for routine register changes, 30 for authorized units and pool caps.
not deployed not deployed
  • The owner can change a class's delay and any call's class. A call nobody listed is in the strictest class.
  • Owner: Timelock O.
Delay: 30 days (designed). Pause: No.
gated on counsel
EntityProposer
The entity approvers' way into Timelock O, at the delay each call's class requires.
not deployed not deployed
  • Only its operator can schedule or cancel. A batch waits the strictest delay among its calls, never less than the timelock's minimum.
  • Operator: the entity approvers' Safe.
Delay: 7 or 30 days by class (designed). Pause: No.
gated on counsel
GuardianTermO (Timelock O)
The guardian's cancel power on Timelock O, for a fixed term.
not deployed not deployed
  • The guardian can cancel a queued operation, nothing else, and only until the term expires.
  • Only Timelock O can renew the term or name a new guardian.
  • The guardian is the Guardian Safe.
Pause: No.
gated on counsel

Company protocol

ContractStatusAddress and ownerTodayDesigned
CompanyRegistry
The canonical on-chain record of every company created through the CompanyFactory: its share token, admin, designated treasury, metadata and lifecycle status. Discovery (/exchange) reads it directly and through this indexer.
deployed 0xEF55…e93B
owner 0xbbea…be02
Companies registered: 0
Factory: 0x85f6…4c98
  • Only the CompanyFactory can register a company. The registry mints nothing and holds no funds.
  • Each company's own admin sets its metadata and designated treasury, transfers its admin, and may close the company. No admin can touch another company's record.
  • The owner can suspend or restore a company as a listing signal; it cannot resurrect a closed one, and it never touches the company's token or funds, which live in their own immutable contracts.
  • metadataURI is untrusted display data: never an authority for ownership, control or price.
  • Owner becomes the protocol Timelock, so a suspension waits in public.
  • A company's share token is a transferable ERC-20, not legal ownership; it runs as a simulation until a company turns that off after counsel.
Delay: none today; the governance owner is timelocked (designed). Pause: No. Suspending a company is a listing signal, not a token pause.
ShareExchange
An on-chain order book that settles trades between a company's share token and AXON. Makers sign EIP-712 limit orders off chain and the site relays the book; a taker fills a signed order on chain here. The exchange custodies nothing between trades — it moves tokens straight between maker and taker from standing ERC-20 allowances — so it is a settlement venue, not a vault.
deployed 0xb792…c741
owner 0xbbea…be02
Protocol fee (bps): 0
AXON token: 0x20f1…b712
Fee router: 0xc40c…cecc
Company registry: 0xef55…e93b
  • Anyone may fill a live, correctly-signed order, cancel their own order, or cancel all of their own at once. The exchange holds no token between trades and can move nothing on its own.
  • Only a share registered in CompanyRegistry may trade here, checked on every fill, so the venue is the company protocol's own tokens.
  • The owner sets the protocol fee on the AXON leg, capped at 10% and routed through the governed FeeRouter; it can change no order and touch no balance.
  • A price here is a limit a maker signed, or a last trade between two addresses — never a guarantee of realizable value.
  • Owner becomes the protocol Timelock, so a fee change waits in public.
  • A share token is a transferable ERC-20, not legal ownership; it trades as a simulation until a company turns that off after counsel.
Delay: none today; the governance owner is timelocked (designed). Pause: No. There is no pause; an order is voided by its own expiry, a cancel, or the maker's epoch bump.

Contracts that other projects deploy on the same chain are not part of this design and are not listed.

Software releases

ReleaseRegistry is not deployed.

No release channel exists on this chain yet, so nodes update only by hand. When it is deployed, every release published to the network is listed here.

What the fleet runs

20 nodes reported in the last 15 minutes, each about itself: self-reported, not checked.

Versions
  • dev: 20
Last self-update
  • failed: 20
NodeUpdateReleaseRunningWhat it said
12D3KooWLs5pfailed 0 devbinary directory not writable: mkdir /usr/local/bin/.dendritic-node.update: read-only file system
12D3KooWMyzUfailed 0 devbinary directory not writable: mkdir /usr/local/bin/.dendritic-node.update: read-only file system
12D3KooWT1kXfailed 0 devbinary directory not writable: mkdir /usr/local/bin/.dendritic-node.update: read-only file system
12D3KooWSD9zfailed 0 devbinary directory not writable: mkdir /usr/local/bin/.dendritic-node.update: read-only file system
12D3KooWKirtfailed 0 devbinary directory not writable: mkdir /usr/local/bin/.dendritic-node.update: read-only file system
12D3KooWGypUfailed 0 devbinary directory not writable: mkdir /usr/local/bin/.dendritic-node.update: read-only file system
12D3KooWAjYzfailed 0 devbinary directory not writable: mkdir /usr/local/bin/.dendritic-node.update: read-only file system
12D3KooWG9p4failed 0 devbinary directory not writable: mkdir /usr/local/bin/.dendritic-node.update: read-only file system
12D3KooWEUFefailed 0 devbinary directory not writable: mkdir /usr/local/bin/.dendritic-node.update: read-only file system
12D3KooWSpxHfailed 0 devbinary directory not writable: mkdir /usr/local/bin/.dendritic-node.update: read-only file system
12D3KooWCE9Kfailed 0 devbinary directory not writable: mkdir /usr/local/bin/.dendritic-node.update: read-only file system
12D3KooWDUMtfailed 0 devbinary directory not writable: mkdir /usr/local/bin/.dendritic-node.update: read-only file system
12D3KooWE8Wrfailed 0 devbinary directory not writable: mkdir /usr/local/bin/.dendritic-node.update: read-only file system
12D3KooWCdeDfailed 0 devbinary directory not writable: mkdir /usr/local/bin/.dendritic-node.update: read-only file system
12D3KooWH7mdfailed 0 devbinary directory not writable: mkdir /usr/local/bin/.dendritic-node.update: read-only file system
12D3KooWQAKVfailed 0 devbinary directory not writable: mkdir /usr/local/bin/.dendritic-node.update: read-only file system
12D3KooWJY4hfailed 0 devbinary directory not writable: mkdir /usr/local/bin/.dendritic-node.update: read-only file system
12D3KooWKnj4failed 0 devbinary directory not writable: mkdir /usr/local/bin/.dendritic-node.update: read-only file system
12D3KooWAXbrfailed 0 devbinary directory not writable: mkdir /usr/local/bin/.dendritic-node.update: read-only file system
12D3KooWHZaqfailed 0 devbinary directory not writable: mkdir /usr/local/bin/.dendritic-node.update: read-only file system

Who can mint, pause, upgrade and spend

PowerTodayHeld by todayDesigned
Mint AXON mintGenesis while genesis is open, and any minter the owner names with setTreasury. owner of AxonToken (AXON): 0x5329…cce1 Only Treasury.fundEpoch, under the epoch budget and the supply cap. Changing the minter takes 30 days.
Spend the AXON Treasury release (naming a purpose), releaseOrder, burn and rescue, by the Treasury's owner. nobody: AXON Treasury is not deployed Timelock P after 14 days, every release tagged with its purpose. Day-to-day deliveries come from OrderDesk's capped float, not releaseOrder.
Change the emission rate Treasury.setEpochBudget, by the owner, at most 2x up or down once per 30 days. nobody: AXON Treasury is not deployed Timelock P after 14 days, within the same limit.
Burn AXON The token's minter burns only what it holds. The Treasury burns by its owner's burn, and burns every swept reward in the sweep's own transaction. nobody: AXON Treasury is not deployed Unchanged. Unclaimed rewards are burned, never kept as inventory.
Decide what an epoch pays submitEpoch, by an allow-listed aggregator holding the aggregator bond. nobody: EpochManager is not deployed Bonded aggregators, a challenge window of at least 12 hours, and disputes.
Slash bonds StakeVault.slash, by any slasher the owner appoints. nobody: StakeVault is not deployed Slashers appointed only through Timelock P. A dispute slashes only the epoch's submitter, split between the challenger and the AXON Treasury.
Queue protocol changes No one. Timelock P is not part of anything deployed. — BootstrapProposer, for the Operations Safe, until it stops; then the two governors. Each call waits its class delay.
Change governance weighting No function does it. ContributionVotes fixes its four sources and the 40/30/20/10 split at deployment. — A new ContributionVotes, by a constitutional proposal: 75% and 30 days.
Pause Nothing can be paused. — The guardian, through GuardianTerm until its term expires, pauses intake on the new contracts. Only a timelock unpauses.
Ship software to the nodes The ReleaseRegistry's publisher. Nodes act on a release only after its activation delay (at least 1 hour), and only if the bytes match its SHA-256. The publisher and the guardian can revoke one at once. nobody: ReleaseRegistry (software releases) is not deployed Publisher: the Operations Safe. Naming another publisher is constitutional (30 days). The guardian, through GuardianTerm, revokes and pauses.
Upgrade Nothing is upgradeable. A change means a new deployment. — Unchanged. Migrations are announced through the constitutional class.
Move channel funds No one. AxonChannels has no owner. — Unchanged.
Change the ownership record No one. No ownership record exists. — Only an approved round or a registrar action, through Timelock O at its class delay (EntityProposer). Gated on counsel.

Timelock delays

designed, not live No timelock is deployed yet, so no action waits today.

ActionDelayWho can cancel while it waits
Content action (prune, seize, restore)2 daysGuardian
Parameter change (service policy, disputes, contribution policy, release activation delay)7 daysGuardian
Protocol treasury (epoch budget, Treasury release, OrderDesk limits)14 daysGuardian
Constitutional (weights, classes, delays, guardian, contract ownership, release publisher, setTreasury, mintGenesis, closeGenesis)30 daysGuardian
Ownership round activation7 days after approvalGuardian, entity approvers
Forfeit, cancel or record a legal transfer of a grant7 daysGuardian, entity approvers
Authorized units and pool caps30 daysGuardian
Distribution declare and fund7 days eachGuardian

Event index

This site keeps a copy of every event from the deployed contracts, up to the chain's finalized block. The background indexer is off on this server. An operator turns it on with CHAIN_INDEX_ENABLED.

ContractIndexed toFinalizedBehindHistoryLast error
AxonToken
0x20f1…b712
— — not indexed —
AxonChannels
0x7430…03bd
— — not indexed —
CompanyRegistry
0xef55…e93b
— — not indexed —
ShareExchange
0xb792…c741
— — not indexed —

Reconciliation

Each check compares a total built from indexed events with what the contract holds at the same block. All runs →

No reconciliation has run on this server yet.

The checks it will run:

  • AXON supply. totalSupply equals everything minted minus everything burned, from Transfer events.
  • AXON held by each pot. Each pot's balance equals AXON sent to it minus AXON sent from it, from Transfer events.
  • Reward claims. Per epoch, claims plus the swept rest never exceed the epoch's total, and the contract's claimed total matches the events.
  • Unclaimed rewards burned. Every RewardDistributor sweep is a burn: in the sweep's transaction AXON supply falls by the amount swept, and the AXON Treasury's balance does not rise.
  • Contribution points. Per period, the ledger's total equals credits minus debits.
  • Ownership units (simulation). Total units equal issued minus forfeited minus cancelled.
  • Distributions (simulation). Per distribution, claims never exceed what was posted, and claimed plus returned equals funded.
  • Site orders against OrderDesk. Every card purchase and compute payout in the site's ledger matches exactly one OrderDesk delivery.

Recent events

No events indexed.

Events appear here once a deployed contract emits them and the indexer has read them.