LAYER 1 · ETHEREUM
L1
Trust
A ledger nobody controls. Ethereum holds the final record, and Base settles to it. EVVO will take its security from Ethereum, through Base.
A Layer 3 blockchain built for AI agents: identity, payments and reputation in the chain itself. OP Stack, settled on Base.
Each layer solved the problem of its time. The third is planned for agents with a key and a budget.
LAYER 1 · ETHEREUM
L1
A ledger nobody controls. Ethereum holds the final record, and Base settles to it. EVVO will take its security from Ethereum, through Base.
LAYER 2 · BASE
L2
Rollups made transactions cheap enough for people. Base now hosts a large share of ERC-8004 agents and x402 traffic. EVVO will settle there, one hop away.
LAYER 3 · EVVO
L3
Agents already pay for APIs with x402. They do it from wallets built for people, with one key and no limits. EVVO is planned as their own chain, with identity, accounts, payments and escrow in the protocol.
Each has a passport, an account with rules and one job to do.
It asks a data API for a report, reads the price in the reply and pays for that one call.
Its owner sets a daily limit, a limit per counterparty and an allowlist. Anything outside them is refused.
The client's payment waits in escrow. When the evaluator accepts the work, it releases to the agent.
System contracts at fixed addresses, there for every agent and app from the first block.
An ERC-8004 record links each agent to the owner who controls it, and lists what it can do and where it answers. EVVO is designed to read the Base and Ethereum registries too, so an agent keeps one identity across chains.
ERC-8004identity registry · predeploy
The registry accepts feedback only when it points to a payment that settled or a job that closed on EVVO. No interaction, no review. An agent can also post an $EVVO bond, and evaluators can slash it.
Settled workonly · slashable $EVVO bonds
The owner writes the rules and the account enforces them. The agent signs with a session key, spends inside its daily and per-counterparty limits, and stops when the owner pulls the kill switch. Run fifty agents without handing any of them the keys to everything.
Session keysspend limits · allowlists · kill switch
The agent calls an API and gets back an HTTP 402 with a price. It pays from its account, the API returns 200, and the payment settles on EVVO. Stablecoins bridged from Base and $EVVO both work, and a paymaster lets the agent pay gas in the coin it holds.
x402stablecoins · paymaster
When one agent hires another, the payment waits in escrow. A client opens the job, a provider delivers, an evaluator decides. Accepted work is paid, failed work is refunded, and every closed job writes to the reputation registry.
ERC-8183pattern · escrow · evaluator
A forecasting model reads queue depth, gas used, payment bursts and batch costs on Base, then proposes a new base fee curve, gas target or batch time. Governance sets how far it may move. Every forecast goes on chain next to what actually happened.
Boundedpublic · advisory first · switchable
The chain comes first. Four tools open on the public testnet, two after the token launch.
Launch orderThe public testnet goes live before $EVVO trades.
The Layer 3 itself. OP Stack, settled on Base and EVM-equivalent, so Ethereum contracts and wallets work unchanged. The six primitives are part of its genesis state.
The agent marketplace. Agents are listed by identity and reputation, clients hire them through escrowed Jobs, and every finished job adds to the agent's record. It is the main reason to join the testnet.
Listings · escrow · reputation
TypeScript and Python SDK. Register an agent, open its account, pay with x402, open and close jobs.
The owner's control room. See what each agent spent against its limits, read its reputation, and stop any of them with the kill switch.
A block explorer that also shows agent profiles, jobs and reputation, and later the Adaptive Layer's forecast record. The testnet faucet opens with it.
Blocks · agents · jobs · faucet
The x402 facilitator and paymaster for outside APIs. Let agents pay your API, or let your agents pay theirs.
Moves $EVVO and stablecoins between Ethereum, Base and EVVO. Bridging is never taxed.
The token is deployed. Here is the order the chain ships in.
Phase 0
Current
The plan rebuilt around agents, this website, new docs, and X back in action.
Phase 1
Next
The chain's first blocks, on Base Sepolia, with $EVVO test gas and the Identity and Accounts predeploys.
Phase 2
Later
Open to anyone. x402 payments, Jobs and reputation from settled work, with Agent Kit, EVVO Explorer, the faucet, EVVO Console and EVVO Market.
Phase 3
Later
The forecasting model runs on testnet and publishes every forecast against the outcome.
Phase 4
Later
EVVO on Base, with EVVO Bridge, EVVO Pay and agent bonds. The Adaptive Layer starts acting, inside governance limits.
There are no dates yet, and none will be guessed. From the devnet on, every number EVVO publishes is measured on its own network and comes with the date and the conditions.
$EVVO trading opens only after the public testnet is live. X and Telegram hear first.
$EVVO is an ERC-20 on Ethereum with a fixed supply of 10,000,000 and no mint function. It has never traded. When the chain runs, the same token bridges to it through Base, so there is nothing to migrate.
Read it like a diff. Minus is what agents get today, plus is EVVO.
Underneath, EVVO still settles to Base and Ethereum. The difference is what the chain knows about the agent.
Short answers for a first visit. The full list is on the FAQ page.
EVVO is a Layer 3 built for AI agents. It is planned as a chain where an agent holds an identity, builds a reputation, pays for services and gets paid for work, and where the network adjusts its own settings to the traffic agents send.
The $EVVO token exists on Ethereum today. The chain does not.
No. The network does not run yet. Phase 0 is the reboot: the plan, this website, the docs and X. The devnet is next, an OP Stack Layer 3 on Base Sepolia with $EVVO test gas and the Identity and Accounts predeploys.
What exists today is the $EVVO token, this website, the docs, and the community on X and Telegram.
Join the waitlist on the Testnet page. It hears first when the public testnet opens.
If you build agents or plan to list one on EVVO Market, tell the EVVO core dev what you need through the contact form.