The Adaptive Layer
A forecasting model that tunes fees and batching inside public ranges and publishes each forecast against the outcome.
On this page
The Adaptive Layer is the part of EVVO that evolves. A forecasting model reads the chain's telemetry, the data the chain records about itself, and proposes changes to its fees, block targets and batch timing. It works inside limits set by governance, and every step is on the record.
What it reads, what it moves
The model sees only what the chain records. It can touch three settings.
| Reads | What it is |
|---|---|
| Queue depth | How many transactions are waiting for the next block |
| Gas used | How full recent blocks were, against their target |
| Payment bursts | Spikes of x402 payments as agents call APIs in waves |
| Batch costs on Base | What it costs to post EVVO's data to Base right now |
| Moves | What it is |
|---|---|
| Base fee curve | How fast the base fee rises and falls with demand |
| Block gas target | How full a block aims to be before fees start to climb |
| Batch posting to Base | When EVVO posts its next batch of data to Base |
Balances, accounts and the order of transactions are out of reach.
The loop
- Read. The model reads the chain's telemetry.
- Forecast. It forecasts the traffic ahead: when demand will rise, when it will fall, and when posting to Base is cheaper.
- Propose. It proposes new values for the three settings. The proposal and its forecast are written on chain before anything changes.
- Apply within bounds. A proposal inside the range governance has set can be applied. A proposal outside the range is not applied, and the setting holds its current value. On testnet nothing is applied.
- Publish the outcome. When the window closes, the real traffic is written next to the forecast. Over time the pairs become the model's public record.
Four rules
- Bounded. The model moves a setting only inside a range that governance has set. $EVVO holders will set those ranges, and they will be public.
- Public. Every forecast, every change and every outcome is written on chain, so anyone can check whether it helped.
- Advisory first. On testnet it only recommends. It acts on mainnet only after its record is public.
- Switchable. A fixed default always exists and the model can be turned off. Without the model, the chain runs on the default.
The shape of a record
- window
- a range of upcoming blocks
- inputs
- queue, gas used, payments, batch cost
- forecast
- demand rising
- proposal
- base fee curve, steeper
- bounds
- inside governance range
- applied
- no (advisory)
- outcome
- written when the window closes
The shape of a record. Values appear when the testnet runs.
Two stages
| Stage | What happens |
|---|---|
| Phase 3, advisory | The forecasting model runs on testnet and publishes every forecast against the outcome. The chain keeps its fixed settings. The forecast record starts here. |
| Phase 4, mainnet | The Adaptive Layer acts inside governance bounds, and only once its record is public. |
From Phase 3 on, anyone can read the record in EVVO Explorer and judge it.
What it cannot do
- It cannot touch consensus. A Layer 3 orders transactions with a sequencer, and the model is not in that path. It does not pick who produces blocks or which transactions go in.
- It cannot act unseen. Its inputs are the chain's own telemetry, its outputs are three named settings, and every forecast, change and outcome is on chain.
- It cannot be mandatory. Turn it off and the chain runs on the fixed default.
Related
- Governance, where holders set the ranges.
- The stack, for where the Adaptive Layer sits.