indexing-transactions

Name: indexing-transactions
Availability: InStock
Author: Jonjon

Acknowledge:

2|3|Updated Mar 4, 2026

Search Tags:#indexing #transaction #hyperindex #event-handlers #field_selection #transaction_fields

Ready to run

npx skills add https://github.com/moose-code/polymarket-indexer --skill indexing-transactions-moose-code

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: indexing-transactions
Source: https://github.com/moose-code/polymarket-indexer/tree/main/.claude/skills/indexing-transactions
Command: npx skills add https://github.com/moose-code/polymarket-indexer --skill indexing-transactions-moose-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

HyperIndex users often need access to transaction-level data, but there is no native onTransaction handler. This skill provides a mechanism to access transaction fields through event handlers.

Core Features & Use Cases

Expose transaction fields (hash, from, to, gasUsed, input, value, etc.) via event.transaction for any indexed contract.
Enable precise auditing, tracing, and correlation of events across multiple subgraphs and contracts.
Use case: link a Transfer event to its corresponding transaction to compute gas usage per transfer.

Quick Start

Configure a handler to read event.transaction fields (for example hash and from) to correlate events with their transactions.

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 without a native onTransaction handler?▼

Access transaction data in HyperIndex by reading fields through event handlers. You can retrieve properties like hash, from, to, gasUsed, input, and value via the event.transaction object within your existing event handlers.

How do I configure field_selection to expose transaction fields for indexed contracts?▼

Configure transaction fields in HyperIndex using the field_selection configuration. This setup enforces that specific transaction data is exposed and accessible as event.transaction within your handlers for any indexed contract.

Can I link a Transfer event to its corresponding transaction to compute gas usage per transfer?▼

Yes, you can link events to their corresponding transactions to compute gas usage. By accessing event.transaction.gasUsed within your event handlers, you can correlate the Transfer event with its exact transaction gas cost.

What transaction fields are available through event handlers in HyperIndex?▼

Available transaction fields include hash, from, to, gasUsed, input, and value. These fields are exposed through the event.transaction object, enabling precise auditing and tracing of events across multiple subgraphs and contracts.

Does HyperIndex support correlating events across multiple subgraphs using transaction data?▼

Yes, HyperIndex supports correlating events across multiple subgraphs and contracts. By exposing transaction fields via event handlers, you can trace and audit event relationships using shared transaction properties like hash and from.

Why are my transaction fields not showing up in the event handler?▼

Transaction fields do not appear if they are not explicitly configured. You must define the required transaction fields in the field_selection settings to ensure they are exposed and accessible as event.transaction within your handlers.