Skip to main content
Squid SDK is modular: a squid combines a chain-specific data source, a store, and optional code-generation and serving tools. This page lists the packages relevant to EVM squids.

One package: @subsquid/squid-sdk

For Portal-native EVM squids, the @subsquid/squid-sdk package bundles the whole toolkit behind one dependency with subpath imports:
Two optional peer packages, @subsquid/evm-rpc and @subsquid/evm-normalization, are required only when the evm/rpc subpath (or an rpc fallback source) is used. The subpaths also work under the classic TypeScript resolution used by standard squid tsconfigs (module: commonjs) — the package ships per-subpath type redirects, so autocomplete works without moduleResolution changes.

Individual packages

The same functionality remains available as standalone packages — existing squids need not migrate:
  • @subsquid/evm-stream + @subsquid/batch-processor — Portal-native data source and runner
  • @subsquid/evm-objects — block augmentation
  • @subsquid/evm-typegen — ABI-based utility module generator; its output imports @subsquid/evm-abi and @subsquid/evm-codec (install both)

Stores

Any store works with any data source: The store contract itself is documented in Store interface.

Serving and tooling