EVVO

Roadmap

Six phases, in order. Each one closes on a condition you can check, and none has a date yet.

Now: Phase 0 · Reboot
012345EVVO ROADMAPSIX PHASES · NO DATES012345PHASE · IN ORDERPHASE0 · REBOOT--.--.--DATE · NONE YETEXIT · DONE WHENSELECTORPHASE 0NEXTDEVNETDATENONE YETEXITA CONDITIONLAMPSSIX PHASES
THE PLAN

Six Phases, In Order

What ships in each phase, and the test it has to pass.

Phase 0Current

Reboot

The plan, rewritten around agents.

Ships

  • This concept: an agent-native Layer 3 on Base
  • The rewritten website
  • New documentation, live at /docs
  • X back in action

Done when

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

Phase 1Next

Devnet

The chain runs for the first time.

Ships

  • 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 2Later

Public Testnet

Anyone can run agents on EVVO.

Ships

  • Agent Payments with x402
  • Jobs: escrow with a client, a provider and an evaluator
  • Reputation from settled work
  • Agent Kit (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.

Phase 3Later

Adaptive Layer, Advisory

The chain starts reading its own traffic.

Ships

  • 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 4Later

Mainnet

$EVVO crosses the bridge, and the model starts to act.

Ships

  • EVVO on Base
  • EVVO Bridge, carrying $EVVO 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 5Later

Beyond

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

Ships

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

Done when

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

PHASE 0 · NOW

The Reboot Checklist

Four pieces of work, and where each one stands.

  1. New concept

    Approved. An agent-native Layer 3, settled on Base.

    Done
  2. Website

    Rewritten to the new concept, page by page.

    Done
  3. Documentation

    Live at /docs, rebuilt around the new plan.

    Done
  4. X

    Quiet since January 2026. Back with build updates as the reboot ships.

    In progress
evvo-status.json
3/4PHASE 0

3 of 4 done

phase
0 · reboot
token
deployed (Ethereum)
trading
not yet
devnet
next
dates
published when real
SHIPPED

What Already Happened

2024 to now, in three entries.

  1. 2024

    Token and Launch

    $EVVO deployed on Ethereum as an ERC-20 with a fixed supply of 10,000,000. The website, X and Telegram went live.

  2. 2025

    Architecture and Design

    Architecture work and the design system behind this site, while X carried the first concept until January 2026.

  3. 2026Now

    Reboot

    A new plan built around AI agents: an agent-native Layer 3 on Base. New concept, new website, new docs.

$EVVO

The Launch Has No Date Yet

$EVVO is deployed on Ethereum and is not trading. The Uniswap pair is empty. Trading opens only after the public testnet is live, and X and Telegram announce the moment liquidity goes in.

Network
Ethereum (ERC-20)
Supply
10,000,000, fixed
Uniswap pair
created, empty
Trading
after the public testnet is live
Launch
announced on X and Telegram
Contract
0x0298868365E3327192C07E1dd90c2a874fB73239
REPORTING

How Progress Is Reported

No dates until they are real

Phases have an order, not a calendar. A date appears when the work behind it can keep it.

Measured on EVVO's own network

Every number EVVO publishes from Phase 1 on is measured on its own network, with the date and the conditions.

Open code, open testnet

Updates land on X. The code will be published in a public GitHub repository, and the public testnet will be open to anyone.

Follow the Build

Progress is posted on X. Questions for the core dev go to Telegram.