메뉴
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;
}
);
If something is unclear, use the
envio-docsskill to search and read the latest documentation.
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 optimizing indexer speed or tuning sync performance. HyperSync, batch size, WebSocket realtime config, and preload optimization.
Use when the indexer fails to start, codegen errors, types are stale, Docker or database issues, or something is not working. Common error messages and fixes.
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 writing or editing event handlers. Handler registration, context API (entity CRUD, getWhere queries, chain, log), spread updates, indexer runtime API, and common pitfalls.
Use when deploying an indexer across multiple chains. Entity ID namespacing to avoid collisions, chain-specific configuration patterns, and the context.chain runtime API.