EVVO

About EVVO

EVVO deployed a token and published a plan in 2024. Here is what changed, and the plan it follows now.

EVVONETWORK · DATA PLATETYPELAYER 3 · AGENT CHAINSTACKOP STACKSETTLESBASE → ETHEREUMTOKEN$EVVO · ERC-20 · 2024NETWORKTESTNET FIRST20242026REBOOT · KEYTOKENSITEDOCSDEVNETTESTNET$EVVO · PORTSETTLES · BASEAGENT-NATIVE LAYER 3UNIT 01 · L3DATA PLATELAYER 3 · AGENTSREBOOT KEY2024 → 2026TOKEN$EVVO · 2024SETTLES ON BASEOP STACKAGENT CHAINLAYER 3
MISSION

A Chain of Their Own

Agents are becoming economic actors, and general-purpose chains still treat each one as another wallet.

L1

Layer 1 secured the chain.

L2

Layer 2 scaled it.

L3

Layer 3 puts intelligence to work.

THE STORY

Two Years, Two Plans

Why the 2024 plan was retired, and what replaced it.

  1. EVVO deployed its token on Ethereum and published a concept that put AI models inside consensus, to forecast load, pick validators and set block timing. The website, X and Telegram went live.

  2. The work went into architecture and design, and into checking the plan against how a Layer 3 runs. On X, posts under the first concept continued until January 2026.

    • A Layer 3 does not run its own validator consensus. It orders transactions with a sequencer and settles to the chain below it.
    • A model in the consensus path is an attack surface, not a feature.
    • The headline figures for throughput, finality and AI confidence were never measured. They are retired.
  3. Agents started to transact. ERC-8004 gave Ethereum a standard for agent identity and reputation, and x402 lets agents pay for APIs over HTTP. The rails exist. A chain built around them does not. EVVO rebuilt the plan as an agent-native Layer 3 on Base.

The name and the token stay. The intelligence moved out of consensus and into the agents.

WHAT CHANGED

The Two Plans Side by Side

Topic2024 plan (retired)2026 plan
IntelligenceAI models inside consensusAgents as users, and an Adaptive Layer that moves inside public limits
NetworkIts own validator setOP Stack Layer 3 with a sequencer, settled on Base
NumbersPublished before they were measuredNone until EVVO's own devnet measures them
ProductsWallet, DEX, Bridge, StakeAgent Kit, plus EVVO Console, Market, Pay, Bridge and Explorer
Token$EVVO on EthereumThe same ERC-20, bridged to EVVO through Base
PILLARS

Agents · Evolution · Foundation

  1. Agents

    The users of EVVO are machines with owners, so the protocol tracks who owns an agent, what it may spend and what it has delivered.

    IdentityAccountsPaymentsJobs

  2. Evolution

    A forecasting model reads the chain's own traffic and proposes fee and batch settings. It moves only inside ranges holders set, and every forecast is public.

    BoundedPublicAdvisory firstSwitchable

  3. Foundation

    EVVO posts its data to Base, and Base settles to Ethereum. Standard Solidity, tooling and wallets work on it unchanged.

    OP StackBaseEthereumSolidity

PRINCIPLES

Four Rules for Every Claim

  • Build in the open

    Updates go out on X. The code will be public on GitHub, and a public testnet runs before mainnet. A claim nobody can check does not get made.

  • Measure first

    The network does not run, so this site publishes no throughput, finality or uptime. From the devnet on, a number appears only when EVVO's own network produced it.

  • Dates follow the work

    The roadmap lists six phases in sequence. A phase gets a date only when the work behind it can keep it.

  • Mark what is planned

    Present tense is for what exists: the token, this website, the docs, X and Telegram. The chain and every product are written in the planned tense.

what-exists.json
  1. {
  2. "token": "deployed 2024 (Ethereum)",
  3. "trading": "not yet",
  4. "website": "live",
  5. "x, telegram": "live",
  6. "docs": "live",
  7. "devnet": "next",
  8. "testnet, mainnet": "planned"
  9. }

Next Is the Devnet

Each roadmap phase lists what ships and the condition that closes it. Questions go to Telegram.