indexing-factory

Register factory-created contracts dynamically for same-block indexing in HyperIndex workflows.

2|3|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/moose-code/polymarket-indexer --skill indexing-factory-moose-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: indexing-factory
Source: https://github.com/moose-code/polymarket-indexer/tree/main/.claude/skills/indexing-factory
Command: npx skills add https://github.com/moose-code/polymarket-indexer --skill indexing-factory-moose-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Contracts created at runtime by factory contracts require dynamic indexing, automatic registration, and same-block visibility to ensure complete data capture.

Core Features & Use Cases

  • Dynamic contract registration via contractRegister with runtime discovery.
  • Same-block indexing guarantees events from newly created contracts are captured immediately.
  • Supports async registration workflows and zero-address contracts.

Quick Start

Register a newly created contract with contractRegister and then use the handler to index its events in the same block.

Frequently Asked Questions about indexing-factory

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

FAQPage Schema
How do I index factory-created contracts in real time when addresses are unknown at setup?

You can index factory-created contracts through dynamic registration using contractRegister, enabling runtime discovery and real-time indexing across multiple chains where contract addresses are unknown at setup.

How does same-block indexing work for newly deployed factory contracts?

Same-block indexing captures events from newly created contracts immediately within the same block they are deployed, using contractRegister to dynamically register addresses and guarantee no data is missed during runtime discovery.

Can I use dynamic contract registration across multiple blockchain networks?

Dynamic contract registration supports runtime deployments across multiple chains, allowing you to discover and index unknown contract addresses in real time within HyperIndex workflows.

What is the best way to handle zero-address contracts during dynamic indexing?

The indexing workflow supports async registration workflows and zero-address contracts, allowing you to manage dynamic address discovery and register newly created contracts without failing on edge cases.

Why does my factory contract indexing miss events from newly created contracts?

Events are missed without same-block indexing coverage. You need to register newly created contracts with contractRegister immediately upon deployment so the handler can process their events in the same block.

Do I need HyperIndex to manage dynamic address registration for runtime contract deployments?

HyperIndex workflows utilize contractRegister for dynamic address management and same-block coverage, satisfying requirements for indexing contracts created at runtime by factory contracts where addresses must be discovered dynamically.