Skip to content ComputeWorksPRELAUNCH
Documentation
Docs/The details

Controls and considerations

Who operates the protocol, what can change, and which dependencies holders should understand.

Prelaunch documentationDescribes the intended protocol. Live contracts, funding, and services remain launch milestones.
On this pageSafes and limited operating rolesEconomic changes are prospectivePhysical assets involve external partiesAutomation still needs operatorsRead the current release

01Safes and limited operating roles

The Treasury/Policy Safe authorizes reviewed purchases, settings, and other administrative actions. A separate Guardian Safe can challenge or pause supported operations. A procurement Safe handles the selected external payment route. These are distinct responsibilities, not token-holder voting rights.

The launch plan currently specifies one owner and one required signature initially, with a later transition to two owners and two signatures. Until that transition, a single owner controls the relevant Safe. The final verified deployment and current onchain owner settings are authoritative; a planned multisignature setup is not an active safeguard.

Server-operated wallets collect fees, publish volume and allocations, authorize settlements, relay transactions, or refill gas. Each role has a defined purpose. A fee keeper is not intended to have general authority to withdraw treasury funds.

02Economic changes are prospective

The retained economic policy framework requires at least 14 days' notice for ordinary changes and at least 30 days for reductions to holder allocation bounds or the cashout rate. Acquisition-cost and growth-calibration changes have a separate minimum 30-day notice. Scheduled changes apply at defined boundaries.

The framework constrains holder-allocation settings to a 10–70% envelope and cashout settings to 75–100%. The initial settings are narrower. Policy notice and bounds do not make all administrative actions delayed, and they do not remove operator discretion over procurement or evidence review.

03Physical assets involve external parties

Equipment procurement, hosting, maintenance, utilization, and rental collection rely on external counterparties. Onchain contracts cannot directly inspect a datacenter or prove that an offchain statement is true. Operators must reconcile evidence and actual funds before the protocol treats them as physical revenue.

Hardware can depreciate, fail, become less competitive, or remain idle. Power and hosting costs can change. Rental demand, vendor delivery, payment processing, and conversion delays affect the available revenue. Reinvestment is a plan, not a promise of permanent income.

04Automation still needs operators

Keepers, data publishers, the holder database, RPC readers, and settlement services must remain available and correctly funded. A smart contract can enforce its rules without being able to schedule its own transactions or independently validate an external invoice.

The holder service can stop new activity when state cannot be reconciled. Holder keys may need containment and an approved recovery before additions reopen; credits already on a key stay on it. Automatic collection does not imply automatic recovery from every interruption.

05Read the current release

Check published token and contract identities, current governance settings, service status, and the policy attached to your credits. A website illustration or estimate does not establish a balance, a hardware purchase, or an available redemption.

The Terms, Privacy Policy, and Risk Disclosures provide additional details. These docs explain the protocol design; the verified release and applicable terms determine what is actually available.

Updated September 22, 2026Read the risk disclosures ↗