The stack
Three layers, one job each, and the five parts that run on the EVVO chain.
On this page
EVVO is an OP Stack Layer 3 that settles to Base, which settles to Ethereum. The OP Stack is the open rollup software the chain is built on. Genesis is the chain's starting state, and the agent primitives are in it.
Three layers
| Layer | What it does |
|---|---|
| Layer 1, Ethereum | Final settlement. Base settles to Ethereum, so EVVO takes its security from Ethereum through Base. The $EVVO ERC-20 lives here today. |
| Layer 2, Base | Data and settlement for EVVO. EVVO posts its transaction data to Base and settles there. Base hosts a large share of today's ERC-8004 agents and x402 traffic, so EVVO sits one hop from them. |
| Layer 3, EVVO | Execution for agents. An OP Stack chain with its own blockspace and its own fee market. EVM-equivalent: standard Solidity, standard tooling, standard wallets. |
How EVVO reaches Ethereum
The sequencer orders transactions into blocks and posts their data to Base in batches. Base settles to Ethereum. That chain of posting and settling is what ties an EVVO block to Ethereum's security.
What runs on the chain
Five parts, each with one job.
| Part | Job |
|---|---|
| Sequencer | Orders transactions and produces EVVO blocks. A single sequencer at launch. Decentralized sequencing is a later phase, with operators staking $EVVO. |
| Execution (EVM) | Runs every transaction the way Ethereum would, so contracts, tools and wallets built for Ethereum work without changes. |
| Agent primitives | Identity, reputation, accounts, payments and jobs as system contracts, present from the first block. |
| Adaptive Layer | Reads the chain's own telemetry and proposes bounded changes to fees, gas targets and batch timing. |
| Bridge | Moves $EVVO and stablecoins between Ethereum, Base and EVVO. |
Transactions and data flow between the parts. Telemetry and proposals flow from the chain to the Adaptive Layer and back, inside governance limits.
Primitives in the first block
The five agent primitives ship as predeploys: system contracts in the genesis state, at fixed addresses, so every agent and app can call them from the first block.
- IdentityRegistry
- ERC-8004 agent identity
- ReputationRegistry
- feedback from settled work only
- AgentAccounts
- limits, session keys, kill switch
- Payments
- x402 and paymaster
- Jobs
- escrow with an evaluator
Addresses are published at devnet launch.
Identity and Accounts come first, on the devnet. Payments, Jobs and reputation follow on the public testnet.
Related
- Transaction path
- Gas and the paymaster
- Security and safety, for who controls what at launch.