indexing-traces

Name: indexing-traces
Availability: InStock
Author: Jonjon

Index transaction call traces via HyperSync data-layer queries and the Effect API.

2|3|Updated Mar 4, 2026

Search Tags:#debugging #analytics #trace #transactions #data-layer #hyperSync #trace-queries

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Access to detailed call trace data from transactions is limited by the absence of a handler-level trace API; this skill enables querying and indexing trace information through HyperSync's data layer.

Core Features & Use Cases

HyperSync data-layer trace queries for transactions, blocks, and addresses.
Workaround access via the Effect API to fetch trace data from an RPC endpoint for index-time indexing and analysis.
Use cases include debugging complex transaction flows, auditing contract interactions, and building trace-based analytics dashboards.

Quick Start

Query trace data for a target block using the HyperSync data layer and the Effect API to index results for analytics.

Frequently Asked Questions about indexing-traces

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

FAQPage Schema

How do I index transaction call traces when a handler-level trace API is unavailable?▼

You can index transaction call traces by using the Effect API to fetch trace data directly from an RPC endpoint. This bypasses the missing handler-level trace API by leveraging HyperSync's data-layer trace queries for your indexing workflow.

What call trace filters can I use with HyperSync data-layer queries?▼

HyperSync data-layer trace queries support filtering by from, to, address, callType, type, and sighash. These filters allow you to precisely target specific contract interactions and transaction-level traces across blocks and addresses.

Can I query transaction traces for specific blocks and addresses using HyperSync?▼

Yes, HyperSync data-layer trace queries support fetching transaction trace data across specific blocks, addresses, and contracts. You apply the available filters to retrieve detailed call trace data needed for auditing or debugging complex flows.

What is the best way to debug complex transaction flows using call trace data?▼

The best way to debug complex transaction flows is to index call trace data using HyperSync trace queries. By capturing detailed transaction-level traces via the Effect API, you can analyze contract interactions and build trace-based analytics dashboards.

Do I need the Effect API to fetch trace data for index-time analytics?▼

Yes, you need the Effect API to fetch trace data from an RPC endpoint when the handler-level trace API is unavailable. This approach is required to retrieve and index call trace information for index-time analysis and analytics dashboards.

When should I use HyperSync data-layer trace queries instead of standard RPC calls?▼

You should use HyperSync data-layer trace queries when you need to index detailed transaction-level call traces across blocks and addresses, especially when a handler-level trace API is unavailable and you rely on the Effect API to fetch RPC data.