indexing-factory

Index runtime factory-created contracts with same-block event coverage.

43|9|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/enviodev/polymarket-v2-indexer --skill indexing-factory
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: indexing-factory
Source: https://github.com/enviodev/polymarket-v2-indexer/tree/main/.claude/skills/indexing-factory
Command: npx skills add https://github.com/enviodev/polymarket-v2-indexer --skill indexing-factory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Contracts created at runtime by factory contracts require dynamic registration and indexing; this skill enables automatic tracking and event coverage without fixed addresses.

Core Features & Use Cases

  • Dynamic contract registration via contractRegister for runtime-generated contracts.
  • Async registration workflows to discover and register new contracts on-the-fly.
  • Same-block event coverage to ensure events from newly created contracts are indexed in the originating block.
  • Works across multiple chains by configuring factory and pair contracts with dynamic addresses.

Quick Start

Register dynamic contracts with contractRegister to start indexing factory-created contracts in real time.

Frequently Asked Questions about indexing-factory

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

FAQPage Schema
How do I index events from dynamic contracts created by factory deployments at runtime?▼

To index dynamic contracts generated by factory deployments, you can use contractRegister for automatic runtime registration. This enables on-the-fly tracking and same-block event coverage for newly created contracts without requiring fixed addresses.

What is same-block event coverage and why is it needed for factory-created contracts?▼

Same-block event coverage ensures that events emitted by newly created contracts are indexed in the originating block where the factory deployment occurred. This prevents missing early on-chain events during asynchronous contract registration flows.

How to register runtime-generated contracts across multiple chains with no fixed addresses?▼

You can register runtime-generated contracts across multiple chains by configuring factory and pair contracts with dynamic addresses using contractRegister. This supports no-address contract configurations and asynchronous registration workflows.

Can I use asynchronous registration workflows to discover and index newly deployed contracts on-the-fly?▼

Yes, asynchronous registration workflows allow you to discover and register new contracts on-the-fly. The skill applies contractRegister to dynamically track and index these runtime contracts as they are generated.

Does this approach require predefined contract addresses to start indexing on-chain events?▼

No predefined contract addresses are required to start indexing on-chain events. The skill supports no-address contract configurations, allowing you to dynamically index contracts created at runtime by factory deployments.

What are the limitations of using contractRegister for dynamic contract indexing?▼

The skill is specifically designed for contracts created at runtime by factory deployments. It requires configuring factory and pair contracts properly to enable dynamic registration and same-block event coverage across supported chains.