Practical overview
When it fits
Use Etherfold when an application needs contract-event indexing and the team wants to keep processor logic separate from its storage backend and operating mode.
Who it is for
- Developers building applications that need indexed smart-contract event data.
- Teams comparing browser-based indexing with server-side indexing.
- TypeScript developers creating modular indexers for Ethereum or other RPC-compatible chains.
Documented uses
- Index ERC-721 collection events for an NFT application.
- Turn contract events into entity state using declared fields and event handlers.
- Reuse one processor across browser IndexedDB and server SQLite storage.
- Build an index to the chain tip or keep following the chain with the CLI.
Requirements & limits
The repository is public and specifies the MIT license.
- The engine is documented for EIP-1193 providers and a restricted set of chain-facing methods.
- The documented storage choices include browser IndexedDB, server SQLite, and a memory-only patch store.
- The CLI's
buildmode stops at the chain tip, whileruncontinues following the chain and serves HTTP reads. - Historical reads are subject to an explicit retention window.
- Repository example commands use pnpm; the package installation example uses npm.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Define an event processor for a contract event
Set up the documented entity-and-handler structure for indexing a contract event.
Before you start
- A TypeScript project.
- Install
@etherfold/browserand@etherfold/processor-entitieswith npm. - The contract event ABI and its event fields.
Steps
Install the packages with the command below.
npm i @etherfold/browser @etherfold/processor-entitiesDeclare the event ABI and create an
EntityProcessortyped to that ABI.Define the entity name, identifier fields, and stored fields.
Add an event handler that writes the event values to the entity state.
Expected outcome
A typed processor definition with entity declarations and an event handler, ready to be connected to a storage and indexing setup.
Guide limitations
- This guide covers processor definition only; it does not configure a chain connection or demonstrate execution.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 14 October 2026
- Original website title
- wighawag/etherfold · Official homepage title · retained in its source language

