- Rust 97.3%
- Shell 2.7%
|
History
|
||
|---|---|---|
| .config | ||
| .github/workflows | ||
| crates | ||
| scripts | ||
| testing | ||
| .gitignore | ||
| Cargo.lock | ||
| Cargo.toml | ||
| clippy.toml | ||
| LICENSE-APACHE | ||
| LICENSE-MIT | ||
| README.md | ||
| rustfmt.toml | ||
stateless
Stateless Ethereum block validation using execution witnesses.
What is stateless?
stateless provides types and functions for validating Ethereum blocks without access to a full node's persistent database. Instead, it relies on pre-generated witness data that proves the specific state accessed during block execution.
It is built on top of reth and revm, and is designed to be no_std compatible for use in constrained environments such as zkVMs.
How it works
- Witness verification — The execution witness is verified against the parent block's state root using a sparse Merkle Patricia trie.
- Block execution — The block is executed in-memory using a witness-backed database (
WitnessDatabase). - Consensus validation — Post-execution consensus checks are performed.
- State root computation — The post-state root is calculated and compared against the block header.
Usage
The primary entry point is stateless_validation:
use stateless::{stateless_validation, ExecutionWitness};
let validation = stateless_validation(
block,
public_keys,
witness,
chain_spec,
evm_config,
)?;
let block_hash = validation.block_hash;
let output = validation.execution_output;
let block_access_list = validation.block_access_list;
no_std
The stateless crate is #![no_std] compatible and builds for RISC-V targets (riscv32imac-unknown-none-elf), making it suitable for use in zkVM environments.
Running EF tests
To run the Ethereum Foundation blockchain tests with stateless validation:
# From the repository root:
./scripts/run_ef_tests.sh default
./scripts/run_ef_tests.sh zeth
Or manually:
# From the repository root:
./scripts/setup_ef_tests.sh
EF_TEST_TRIE=default cargo test -p ef-tests --release --features "asm-keccak ef-tests"
Contributing
Contributions are welcome! Join the conversation in the Telegram group.
License
Licensed under either of Apache License, Version 2.0 or MIT license at your option.