Block input
Blocks, receipts and uncles decoded straight from bytes into typed values, ahead of execution.
Eita is an Ethereum Virtual Machine specified in Lean 4 and derived from its proof — correct by construction, not by audit. The correctness layer for financial software.
Eita replays Circle’s Arc chain from genesis and follows it live. Every number on the Arc pages is folded from the fact log that replay writes — USDC supply, holders, fees, protocols and lending — and each window states its block range, the state roots checked in it, and the fact-log shards behind it.
The Lean specification is the only place the EVM’s rules are written. Everything that executes is generated from it, and everything the engine produces is checked against the chain as it runs.
The Ethereum execution specs, ported fork by fork. Gas, state effects, and the parallel schedule are theorems, not comments.
The host effect layer and gas formulas are emitted from the spec; a gate re-checks every proof on each change.
Opcode handlers for ARM64 and x86-64, a JIT for hot contracts, and a Common Lisp host you can open up while it runs.
Blocks, receipts and uncles decoded straight from bytes into typed values, ahead of execution.
Transactions run in order against an in-memory hot set; cold state is read from the snapshot through an in-memory index.
Gas, bloom, receipts and transactions roots recomputed and compared. Nothing durable claims an unverified block.
Every call, log, transfer and state change into a binary columnar log with a history index — one encoder lane per table.
The hot set freezes into a delta layer in 0 ms; layers compact into a new base in the background, where the full state root is checked.
As of 28 October 2026.
Vibecoding is fast, but unproven. Put a machine-checked specification between the AI and the code, and you keep the speed — with a proof underneath.
The model writes the implementation; a formal proof in Lean is the gate. The result is correct by construction, not correct by hope. Eita is the existence proof that this works at the scale of a whole EVM — built by one engineer and the verification loop.
For programmable money, a single execution or accounting bug is a consensus split, a frozen settlement, or a regulatory event. Today that risk is held back by audits and testing — best effort, not proof. Eita turns “trust us” into “here’s the proof”: a verified execution and state engine that indexers, block builders, and searchers can all build on, knowing the state they see is exactly the state the chain produced.
A formally-verified reference client, conformance harness, and differential oracle — the correctness backstop for a chain and the state substrate beneath its tooling.
AI-generated stablecoin-finance contracts — paymasters, FX, upgrades — written against machine-checked specs and shipped with their proofs.
Correct-by-construction financial software beyond the EVM: ledgers, settlement, compliance as code. How regulated financial systems get built.