indexing-traces

Index transaction trace data via the HyperSync data layer with filters.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

HyperIndex currently lacks a handler-level trace API, so you need to access trace data through the HyperSync data layer.

Core Features & Use Cases

  • Full trace queries at the data layer with filters for From/To, address, CallType, type, and sighash.
  • Available trace fields include From, To, CallType, Gas, Input, Value, GasUsed, Output, Subtraces, TraceAddress, TransactionHash, BlockNumber, Error, and more.
  • Use cases include tracing and debugging complex transactions, attribution of on-chain activity, and indexing for auditing.

Quick Start

Invoke the HyperSync client to fetch traces for a block or transaction using the available filters.

Frequently Asked Questions about indexing-traces

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

FAQPage Schema
How do I index and query call traces for blockchain transactions?

To index and query call traces for blockchain transactions, invoke the HyperSync client to fetch trace data using filters for From/To, address, CallType, type, and sighash. This bypasses the lack of a handler-level trace API in HyperIndex.

What blockchain trace fields are available when fetching data with HyperSync?

Available blockchain trace fields include From, To, CallType, Gas, Input, Value, GasUsed, Output, Subtraces, TraceAddress, TransactionHash, BlockNumber, and Error for auditing and debugging.

Can I use HyperIndex handlers to directly access transaction trace data?

No, HyperIndex currently lacks a handler-level trace API. Access transaction trace data through the HyperSync data layer to query and index traces for debugging and analytics.

What is the best way to debug complex blockchain traces?

The best way to debug complex blockchain traces is querying the HyperSync data layer to filter by addresses, CallType, or sighash. This exposes detailed execution data like GasUsed, Input, and Error for analysis.

How do I filter transaction traces by sighash or CallType?

Filter transaction traces by sighash or CallType by invoking the HyperSync client with specific query parameters. This isolates exact internal call types and function signatures for debugging on-chain activity.