indexer-multichain

name	indexer-multichain
description	Use when deploying an indexer across multiple chains. Per-chain data mode, entity ID namespacing to avoid collisions, chain-specific configuration patterns, and the context.chain runtime API.
metadata	{"managed-by":"envio"}

Multichain Indexing

Per-Chain Data Mode

By default every entity row and effect cache is shared by all chains, so the same entity id on two chains resolves to one row. Set disable_default_cross_chain to make entities and effect caches per-chain instead:

name: my-indexer
disable_default_cross_chain: true

With it on:

• Entity tables get a composite (id, chainId) primary key. The same id on two chains is two independent rows, in memory, in Postgres and in ClickHouse, and entity history and reorg rollback are scoped per chain too.
• Effects that don't state a crossChain option get one cache per chain.
• Handler code is unchanged: a handler always runs on one chain, so context.Token.get(id) reads that chain's row.

Sharing becomes explicit. Add @crossChain to an entity whose rows should stay shared by every chain:

type Counter {          # per-chain: one row per (id, chain)
  id: ID
   BigInt


 GlobalCounter     
   ID
   BigInt