graph-tally-primary-sources-2026-05-11

Graph Tally primary sources

Reviewed: 2026-05-11 UTC

Core protocol framing

• https://thegraph.com/docs/en/indexing/tap/
  • Official GraphTally docs page. Best single source for the live operational framing: sender/gateway role, indexer role, RAV lifecycle, verifier and escrow contract addresses, and the concrete indexer-service / tap-agent / indexer-agent stack.
• https://thegraph.com/blog/graph-tally-indexer-micropayments/
  • Best narrative explanation of why the protocol exists: one-way payment channels for high-volume decentralized query serving, stateless senders, receiver-side accumulation, and threshold-based RAV requests.

Spec and implementation lineage

• https://raw.githubusercontent.com/graphprotocol/graph-tally/main/README.md
  • Official repository README confirming the current branding transition from TAP to Graph Tally and the core receipt → aggregation → RAV → escrow-redemption flow.
• https://raw.githubusercontent.com/graphprotocol/graph-improvement-proposals/main/gips/0054-timeline-aggregation-protocol.md
  • Canonical accepted protocol specification for TAP. Most useful source for the exact protocol objects: receipts, RAVs, allocations, uniqueness guarantees, aggregation requests, and EIP-712 signing.
• https://raw.githubusercontent.com/graphprotocol/graph-improvement-proposals/main/gips/0066-graph-horizon.md
  • Canonical source for why TAP/Graph Tally matters beyond subgraphs. Shows how Graph Horizon generalizes staking and payments into a reusable data-services protocol for future query, oracle, and other service markets.

Main takeaways from this pass

• Graph Tally is most usefully classified as query-micropayment and settlement infrastructure rather than generic payments or generic The Graph infra.
• Its durable primitive is the receipt-to-RAV compression step: per-request signed debt is accumulated offchain, then periodically rolled into one redeemable voucher against escrow.
• The sender/gateway and aggregator roles are the key control surfaces. Even when settlement is cryptographically verifiable, routing, signer management, aggregation responsiveness, and escrow operations still shape who can practically transact.
• Graph Tally is a strong comparison class for L402, x402, generic payment channels, and paid API systems because it separates request authorization, service delivery, aggregation authority, and final settlement more cleanly than most paid-API narratives do.