Event Scanner
⚠️ WARNING: ACTIVE DEVELOPMENT ⚠️
This project is under active development and likely contains bugs. APIs and behaviour may change without notice. Use at your own risk.
About
Event Scanner is a Rust library for streaming EVM-based smart contract events. It is built on top of the alloy ecosystem and focuses on in-memory scanning without a backing database. Applications provide event filters; the scanner takes care of fetching historical ranges, bridging into live streaming mode, all whilst delivering the events as streams of data.
Table of Contents
Features
- Historical replay – stream events from past block ranges.
- Live subscriptions – stay up to date with latest events via WebSocket or IPC transports.
- Hybrid flow – automatically transition from historical catch-up into streaming mode.
- Composable filters – register one or many contract + event signature pairs.
- No database – processing happens in-memory; persistence is left to the host application.
Architecture Overview
The library exposes two primary layers:
EventScanner– the main module the application will interact with.BlockRangeScanner– lower-level component that streams block ranges, handles reorg, batching, and provider subscriptions.
Quick Start
Add event-scanner to your Cargo.toml:
[]
= "0.2.0-alpha"
Create an event stream for the given event filters registered with the EventScanner:
use ;
use ;
use StreamExt;
use crateMyContract;
async
Usage
Building a Scanner
EventScanner supports:
with_blocks_read_per_epoch- how many blocks are read at a time in a single batch (taken into consideration when fetching historical blocks)with_reorg_rewind_depth- how many blocks to rewind when a reorg is detected (NOTE ⚠️: still WIP)with_block_confirmations- how many confirmations to wait for before considering a block final (NOTE ⚠️: still WIP)
Once configured, connect using either connect_ws::<Ethereum>(ws_url) or connect_ipc::<Ethereum>(path). This will connect the EventScanner and allow you to create event streams and start scanning in various modes.
Defining Event Filters
Create an EventFilter for each event stream you wish to process. The filter specifies the contract address where events originated, and event signatures (tip: you can use the value stored in SolEvent::SIGNATURE).
// Track a SPECIFIC event from a SPECIFIC contract
let specific_filter = new
.with_contract_address
.with_event;
// Track a multiple events from a SPECIFIC contract
let specific_filter = new
.with_contract_address
.with_event
.with_event;
// Track a SPECIFIC event from a ALL contracts
let specific_filter = new
.with_event;
// Track ALL events from a SPECIFIC contracts
let all_contract_events_filter = new
.with_contract_address
.with_contract_address;
// Track ALL events from ALL contracts in the block range
let all_events_filter = new;
Register multiple filters by invoking create_event_stream repeatedly.
The flexibility provided by EventFilter allows you to build sophisticated event monitoring systems that can track events at different granularities depending on your application's needs.
Scanning Modes
- Live mode –
start_scanner(BlockNumberOrTag::Latest, None)subscribes to new blocks only. - Historical mode –
start_scanner(BlockNumberOrTag::Number(start), Some(BlockNumberOrTag::Number(end))), scanner fetches events from a historical block range. - Historical → Live –
start_scanner(BlockNumberOrTag::Number(start), None)replays fromstartto current head, then streams future blocks.
For now modes are deduced from the start and end parameters. In the future, we might add explicit commands to select the mode.
See the integration tests under tests/live_mode, tests/historic_mode, and tests/historic_to_live for concrete examples.
Examples
examples/simple_counter– minimal live-mode scannerexamples/historical_scanning– demonstrates replaying from genesis (block 0) before continuing streaming latest blocks
Run an example with:
RUST_LOG=info
# or
RUST_LOG=info
Both examples spin up a local anvil instance, deploy a demo counter contract, and demonstrate using event streams to process events.
Testing
Integration tests cover live, historical, and hybrid flows: (We recommend using nextest to run the tests)