skills.rest
moose-code
moose-codeCOMMUNITY
Explore all skills by this author →
𝕏@jonjonclarkGitHub

indexing-multichain

Namespace entity IDs by chainId to prevent cross-chain collisions in multi-chain indexers.

2|3|Updated Mar 4, 2026
Search Tags:#indexing#config#blockchain#multichain#runtime-api#entity-ids#chainid
One-click install
npx skills add https://github.com/moose-code/polymarket-indexer --skill indexing-multichain-moose-code
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: indexing-multichain
Source: https://github.com/moose-code/polymarket-indexer/tree/main/.claude/skills/indexing-multichain
Command: npx skills add https://github.com/moose-code/polymarket-indexer --skill indexing-multichain-moose-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploying an indexer across multiple chains can cause cross-chain ID collisions and inconsistent configuration. This Skill provides a pattern to namespace IDs with chainId and to apply chain-aware runtime behavior.

Core Features & Use Cases

  • Entity ID Namespacing: prefix IDs with the active chainId to avoid collisions across networks.
  • Chain-Specific Logic: branch handling based on context.chain for per-network behavior and config.
  • Per-Chain Config: define a global config with separate contract addresses per chain and a scalable pattern for multi-network deployments.

Quick Start

Configure your multi-chain indexer to namespace IDs by chainId and supply per-chain addresses in the config, then deploy across networks.

Frequently Asked Questions about indexing-multichain

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent cross-chain ID collisions in a multi-chain indexer?▼

Prevent cross-chain ID collisions in a multi-chain indexer by namespacing entity IDs with the active chainId, which creates safe, scoped identifiers to avoid conflicts across networks.

How do I configure per-chain contract addresses for multi-chain indexing?▼

Configure per-chain contract addresses for multi-chain indexing by defining a global config that supplies separate contract addresses for each chain, establishing a scalable pattern for multi-network deployments.

How do I apply chain-specific runtime logic in a multi-chain indexer?▼

Apply chain-specific runtime logic in a multi-chain indexer by branching handler behavior based on context.chain, enabling per-network configuration and context-aware processing across networks.

When do I need chain-aware context handling for blockchain indexing?▼

You need chain-aware context handling for blockchain indexing when deploying a single indexer across multiple networks, which requires applying per-chain configurations and namespacing IDs by chainId.

What is the best way to structure entity IDs for multi-chain deployments?▼

The best way to structure entity IDs for multi-chain deployments is prefixing them with the active chainId to ensure safe, scoped IDs and prevent cross-chain collisions across networks.

Related Skills

Explore More Software Engineering Skills→
cyoteecyotee

permit2-addresses

Standardize Permit2 contract addresses per chain for multi-chain applications.

Community
Basic
enviodevenviodev
43

indexing-multichain

Enforce chainId-prefixed entity IDs and per-chain configuration for multichain indexing.

Official
Advanced
enviodevenviodev
43

indexing-handler-syntax

Define event handlers with a consistent syntax and context API for the Polymarket indexer.

Official
Advanced
widnyanawidnyana
4

evm-decimal-validation

Validate ERC20 token decimals against on-chain values across EVM chains.

Community
Intermediate