indexing-transactions

Configure field_selection to expose transaction fields via event.transaction in HyperIndex handlers.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Access to transaction-level data within event handlers when using HyperIndex, addressing the lack of a native onTransaction handler by surfacing data through event.transaction.

Core Features & Use Cases

  • Configure field_selection to expose transaction fields on events.
  • Read transaction data via event.transaction in your handler logic for auditing, debugging, and analytics.
  • Use in scenarios like tracing trades, validating builder codes, and diagnosing failures in on-chain workflows.

Quick Start

Configure field_selection in your config.yaml to include transaction fields and access them via event.transaction in your handlers.

Frequently Asked Questions about indexing-transactions

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

FAQPage Schema
How do I access transaction data in HyperIndex event handlers?

Access transaction data in HyperIndex event handlers by configuring field_selection in config.yaml to expose transaction fields, then reading them via event.transaction in your handler logic.

What is the best way to debug on-chain transaction failures using HyperIndex?

Debug on-chain transaction failures using HyperIndex by surfacing granular transaction metadata through event.transaction, allowing you to trace trades, validate builder codes, and diagnose workflow errors directly in event handlers.

Can I use a native onTransaction handler with HyperIndex event-driven workflows?

No, HyperIndex lacks a native onTransaction handler, but you can achieve transaction-level data access by configuring field_selection to surface necessary fields through event.transaction within your existing event-driven handlers.

How do I configure field_selection to expose transaction fields in HyperIndex?

Configure field_selection in your config.yaml file to specify which transaction fields to expose, then access those fields directly from event.transaction within your event handlers to process on-chain data.

Does accessing transaction-level data in event handlers require special dependencies?

No, accessing transaction-level data requires no special dependencies, only configuring field_selection in your config.yaml to expose transaction fields and reading the surfaced data from event.transaction in your handlers.