القائمة
Use when needing call trace data from transactions. HyperSync supports trace queries at the data layer. No handler-level trace API currently — access traces via HyperSync client directly.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | indexer-traces |
| description | Use when needing call trace data from transactions. HyperSync supports trace queries at the data layer. No handler-level trace API currently — access traces via HyperSync client directly. |
| metadata | {"managed-by":"envio"} |
HyperSync supports full trace queries at the data layer, but the Envio Indexer does not yet expose a handler-level trace API (like onTrace).
HyperSync can query traces with filtering by:
from / to — sender/recipient addressesaddress — contract addresscallType — call, delegatecall, staticcalltype — call, create, suicide, rewardsighash — function signaturesAvailable trace fields: From, To, CallType, Gas, Input, Value, GasUsed, Output, Subtraces, TraceAddress, TransactionHash, BlockNumber, Error, and more.
For trace-dependent indexing, use the Effect API to fetch trace data from an RPC endpoint:
import { createEffect, S } from "envio";
const getTraces = createEffect(
{
name: "getTraces",
input: S.schema({ blockNumber: S.number }),
output: S.unknown,
cache: true,
},
async ({ input }) => {
const res = await fetch(RPC_URL, {
method: "POST",
body: JSON.stringify({
jsonrpc: "2.0",
method: "trace_block",
params: [`0x${input.blockNumber.toString(16)}`],
id: 1,
}),
});
return (await res.json()).result;
}
);
Full reference: https://docs.envio.dev/docs/HyperIndex-LLM/hyperindex-complete
Use when processing every block (or every Nth block) for time-series data, periodic snapshots, or block-level aggregations. indexer.onBlock API, where filter with block-number range and stride, and block handler context.
Use when writing or editing config.yaml. Chain/contract structure, addresses, start_block, event selection, field_selection, custom event names, env vars, address_format, schema/output paths, YAML validation, and deprecated options.
Use when making RPC calls, fetch requests, or any external I/O from handlers. Effect API with createEffect, S schema validation, context.effect(), preload optimization (handlers run twice), cache and rateLimit options.
Use when indexing contracts deployed by factory contracts at runtime. contractRegister API, dynamic contract config (no address), async registration, and same-block event coverage.
Use when filtering events by indexed parameters to reduce processing volume. The `where` option supports static filters, dynamic per-chain functions, contract address filtering, and conditional enable/disable.
Use when writing or editing event handlers. Handler registration, context API (entity CRUD, getWhere queries, chain, log), spread updates, indexer runtime API, and common pitfalls.