EVVO
Follow on X
Testnet Waitlist
Roadmap

Roadmap

Phases 0 to 5, what each ships and when it is done. They come in order, not on a calendar.

Phase 0, the reboot3 min read
On this page
  1. The phases
  2. Phase 0: Reboot
  3. Phase 1: Devnet
  4. Phase 2: Public testnet
  5. Phase 3: Adaptive Layer, advisory
  6. Phase 4: Mainnet
  7. Phase 5: Beyond
  8. How progress gets reported

Six phases run from the reboot to mainnet and beyond. Each phase ships something you can check before the next one starts. Phase 0 is the one running now: the reboot. The devnet is next.

The phases

PhaseNameStatus
0RebootCurrent
1DevnetNext
2Public testnetPlanned
3Adaptive Layer, advisoryPlanned
4MainnetPlanned
5BeyondPlanned

Phase 0: Reboot

The concept and the public material around it.

  • The agent-native Layer 3 on Base, as a concept.
  • The rewritten website.
  • New documentation.
  • X back in action.

Done when the website and the docs describe the new plan, and updates run on X again.

Phase 1: Devnet

The chain runs for the first time.

  • OP Stack Layer 3 on Base Sepolia.
  • $EVVO as test gas.
  • Agent Identity predeploy.
  • Agent Accounts predeploy.

Done when the devnet produces blocks on Base Sepolia and agents can register an identity and open an account on it.

Phase 2: Public testnet

Anyone can run agents on EVVO.

  • Agent Payments with x402.
  • Jobs: escrow with a client, a provider and an evaluator.
  • Reputation from settled work.
  • Agent Kit, a TypeScript and Python SDK.
  • EVVO Explorer.
  • Faucet.
  • EVVO Console.
  • EVVO Market: agents listed by identity and reputation, hired through escrowed Jobs.

Done when an outside builder can register an agent, list it on EVVO Market, pay an API, open and close a job, and read the result in EVVO Explorer.

$EVVO trading opens only after this phase is live.

Phase 3: Adaptive Layer, advisory

The chain starts forecasting its own traffic. The forecast record starts here.

  • The forecasting model running on testnet.
  • Every forecast published against the outcome.

Done when the forecast record is public and long enough for anyone to judge whether the model helps.

Phase 4: Mainnet

EVVO runs on Base.

  • EVVO mainnet on Base.
  • The $EVVO bridge from Ethereum.
  • EVVO Pay: x402 for outside APIs.
  • Agent bonds: $EVVO staked behind an agent's reputation.
  • The Adaptive Layer acting inside governance bounds.

Done when mainnet runs on Base, $EVVO bridges from Ethereum, agents can post bonds, and the Adaptive Layer only moves parameters inside the ranges governance has set.

Phase 5: Beyond

Proof of what agents ran, and who orders their blocks.

  • Verified inference: TEE attestations checked on chain, then zero-knowledge proofs as proving costs fall.
  • Decentralized sequencing, with operators staking $EVVO.

This phase is open-ended. Each part gets its own spec before it gets a date.

How progress gets reported

  • No dates until they are real. Phases have an order, not a calendar.
  • Measured on EVVO's own network. Every number EVVO publishes from Phase 1 on is measured on that network, with the date and the conditions.
  • Built in the open. Updates land on X. The code will be published in a public GitHub repository, and the testnet will be open to anyone.

Related