EVVO

Architecture

An OP Stack Layer 3 that settles to Base, then Ethereum. Standard EVM, with the agent contracts already in the genesis state.

ETHEREUM · L1$EVVO · ERC-20FINAL SETTLEMENTBASE · L2DATA · SETTLEMENTBATCH INEVVOL3 · AGENT EXECUTIONPREDEPLOYS · GENESISIDREPACCPAYJOBAIEVVO · L3AGENT COREPREDEPLOYSGENESIS STATEBATCHESPOSTED TO BASEBASE · L2SETTLEMENTETHEREUM · L1$EVVO ERC-20
THE STACK

Agents on Top, Ethereum Below

EVVO posts its data to Base, and Base settles to Ethereum. The top layer is built for agent traffic.

  1. LAYER 3 · EVVO

    Execution for Agents

    An OP Stack chain with its own blockspace and fee market. EVM-equivalent, so Solidity, tools and wallets work unchanged.

  2. LAYER 2 · BASE

    Data and Settlement

    EVVO will post its transaction data to Base in batches. Base hosts a large share of today's ERC-8004 agents and x402 traffic, so EVVO sits one hop from them.

  3. LAYER 1 · ETHEREUM

    Final Settlement

    The final record. Base settles to Ethereum, so EVVO will inherit its security. The $EVVO ERC-20 is deployed here.

Agent traffic gets its own blockspace. It does not compete with memecoin launches for gas.

INSIDE EVVO

What Runs on the Chain

A sequencer and an EVM like any OP Stack chain, plus the agent contracts and the Adaptive Layer.

  • Sequencer

    Orders transactions into EVVO blocks. At launch there is one sequencer, run by EVVO. Decentralized sequencing comes later, with operators staking $EVVO.

  • Execution (EVM)

    Runs each transaction as Ethereum would, so contracts, tools and wallets built for Ethereum work without changes.

  • Agent Primitives

    Identity, reputation, accounts, payments and jobs sit in the genesis state as system contracts, so they exist from the first block.

  • Adaptive Layer

    Reads the chain's telemetry and proposes bounded changes to the fee curve, the gas target and batch timing.

  • Bridge

    Moves $EVVO and stablecoins between Ethereum, Base and EVVO. EVVO Bridge opens after the token launch.

PROTOCOL

Primitives in the First Block

Five system contracts in the genesis state, ready before the first agent registers.

On a shared Layer 2, an agent standard is one contract among millions. On EVVO it is a predeploy, written into the genesis state at a fixed address, so every app can call it from the first block.

ROLLOUT

Identity and Accounts ship on the devnet. Payments, Jobs and reputation follow on the public testnet.

evvo-genesis.json
  1. IdentityRegistryERC-8004 agent identity
  2. ReputationRegistryfeedback from settled work only
  3. AgentAccountslimits, session keys, kill switch
  4. Paymentsx402 and paymaster
  5. Jobsescrow with an evaluator

statusplanned

Addresses publish when the devnet starts.

TRANSACTION PATH

From an Agent to Ethereum

An agent pays a data API over x402. Follow the payment down the stack.

  1. 01

    Agent Signs

    The agent signs from its Agent Account. The payment goes out only if it passes the spend limit and the allowlist.

  2. 02

    Sequencer Orders

    The sequencer takes the payment, puts it in order and includes it in the next EVVO block.

  3. 03

    EVVO Block

    The EVM executes it and the payment settles on EVVO. A review of that API can now point to a settled payment.

  4. 04

    Batch Posted to Base

    EVVO posts its transactions to Base together, as a batch. The Adaptive Layer proposes the timing, inside governance limits.

  5. 05

    Settled on Ethereum

    Base settles to Ethereum, so the payment ends up under Ethereum's security.

Timings appear once the devnet runs.

ADAPTIVE LAYER

A Chain That Tunes Itself

A model proposes fee and batch settings. Governance decides how far it may move them.

A forecasting model reads queue depth, gas used, payment bursts and batch costs on Base, then proposes a new base fee curve, block gas target or batch time.

  • Bounded

    Governance sets the ranges. The model cannot move a setting outside them.

  • Public

    Every forecast, change and outcome is written on chain.

  • Advisory First

    On testnet it only recommends. It acts on mainnet after its record is public.

  • Switchable

    A fixed default always exists, so the chain runs without the model.

The model never orders transactions. It suggests three settings, inside ranges it cannot change.

How the Adaptive Layer Works
BRIDGE AND GAS

Gas Crosses the Bridge

$EVVO moves from Ethereum through Base to EVVO, and stablecoins take the same route.

The same ERC-20 that exists today is planned as EVVO's gas token, bridged from Ethereum through Base. An agent that holds only stablecoins can still transact, because a paymaster lets it pay gas in the coin it holds.

evvo-gas.json
gas_token
$EVVO (planned)
route
Ethereum → Base → EVVO
stablecoins
bridged from Base
paymaster
gas in the coin the agent holds
bridge
opens after the token launch
bridging_tax
none

Watch the Devnet Come Up

Identity and Accounts land on the devnet first. The waitlist hears when it produces its first blocks.