Skip to content
ROBO26

Tokenomics

Holdings, statistics and documents

$ROBO · settled on EVM

$ROBO is the settlement asset of a compute network. What follows is what it is structurally used for, how supply is held, and what it would take for compute to behave like any other market on an EVM chain.

Supply at a glance

Total supply

1,000,000,000

Total supply

fixed; no mint function

Circulating

58%

Circulating

unstaked and unlocked

Staked

18%

Staked

posted as operator bonds

Locked in job escrow

9%

Locked in job escrow

a float, not a lockup

What the asset is for

1. Three structural uses, and one honest omission

$ROBO is not a claim on ROBO Labs' revenue, and holding it does not entitle anyone to anything the network earns. It is the unit the network settles in, and its demand is a function of how much compute is moving through it rather than of sentiment about the network's future.

That demand has three structural sources. Every scheduled job escrows its budget, so throughput itself locks a float. Every operator posts a bond proportional to the capacity they have attached, so supply growth locks more. Every delegator backing an operator stakes behind that bond. None of these are speculative positions — they are working capital the network requires in order to function.

The omission worth stating plainly: none of that sets a price. A network can be busy and the asset can still be volatile. Anyone modelling this should model the float and the bond requirement, which are mechanical, and treat everything else as unknown.

$ROBO supply by use

Deltas compare against Q1 2025.

Circulating, unstaked-9pts

58%

Staked behind operators+7pts

18%

Treasury and unemitted-2pts

15%

Held in job escrow+4pts

9%

Source: ROBO on-chain state, Q1 2026

Holdings and unlocks

2. Who holds what, and when it becomes liquid

Allocation is published because the alternative — asking people to attach hardware to a network whose supply schedule they cannot see — does not work. Team and backer allocations vest over four years from a one-year cliff, and the cliff has passed.

Allocation of total supply
  • Operator emissions34%
  • Ecosystem and treasury22%
  • Team, 4-year vest18%
  • Early backers, 4-year vest16%
  • Public liquidity10%

Source: ROBO token contract, genesis allocation

Annual emissions as a share of total supply

Emissions pay operators to attach capacity before demand can. They decay to a maintenance tail.

2025

9%

2026

5%

2027 (scheduled)

2%

2028 (scheduled)

1%

2029 onward (tail)

1%

Source: ROBO published emissions schedule

Compute as a market

3. Compute is a commodity that has never had a market structure

Every other input at this scale — electricity, bandwidth, storage, freight — has forwards, an index, and someone willing to take the other side of your risk. Compute has purchase orders and a sales call. That is the gap putting settlement on a public chain actually addresses, and it matters more than the payment rail does.

Once a reservation is a transferable on-chain position rather than a line in a contract, ordinary market structure becomes possible without ROBO having to build any of it. A team that over-reserved can sell the remainder instead of eating it. A team that needs certainty in six months can buy it now from someone with a different view of demand.

Reserved capacity: how positions are used

Resale and collateral use only became possible once reservations were transferable.

20262025

Held to expiry, consumed

71%
92%

Resold before expiry

17%
3%

Used as collateral

8%
0%

Expired unused

4%
5%

Source: ROBO on-chain state, reserved positions

We stopped treating a reservation as a cost we had committed to and started treating it as a position we could manage. That single change is worth more to us than the unit price.

Anouk Weisz

Treasury Lead, TIDEMARK

Further integration

4. What is shipped, what is in progress, what is only a sketch

Roadmaps age badly, so this one is split by how much is actually built rather than by quarter. Everything in the first column is live on mainnet today; everything in the third is an argument we find persuasive and have not yet had to defend in production.

Integration status

Shipped

  • Escrowed job settlement
  • Operator bonds and slashing
  • Delegated staking
  • Batched settlement epochs
  • On-chain clearing price

In progress

  • Transferable capacity forwards
  • Collateral adapters
  • Cross-chain settlement
  • Agent-callable inference

Exploring

  • Compute index products
  • Underwriting from receipts
  • Regional capacity markets
  • Proof-carrying inference

Not planned

  • A governance token separate from $ROBO
  • Lock-ups for buyers
  • Off-chain IOU settlement
  • Rebasing supply

Source: ROBO protocol roadmap

Documents

Everything the claims above rest on

These are illustrative entries for a fictional protocol — the links do not resolve.

  • Protocol whitepaperPDF · 48 pages · v2.1 · Feb 2026
  • Token contract and allocationSolidity · verified source
  • Emissions scheduleCSV · through 2031
  • Settlement and slashing auditPDF · third-party · Jan 2026
  • Governance charterPDF · 12 pages
  • Quarterly network reportPDF · Q1 2026

Please read

Nothing on this page is an offer, a solicitation, or investment advice. ROBO, $ROBO, and every figure, document and quote here are fictional and were invented for a design exercise.