Edge & Node's Dec 2025 / Jan 2026 Update

:woman_astronaut: Executive Summary

Although many of us at Edge & Node took a break for the holiday season, it seems that we packed an unusual level of productivity into a short timespan. December marked a major milestone with the successful production deployment of Graph Horizon, migrating over 95% of query volume and indexer stake while completing additional in-flight upgrades. The team stabilized the broader stack with Horizon-related compatibility across Gateway, Explorer, Studio, and graph-node, including support for TAPv2 receipts and dual dispute managers. Parallel efforts advanced the next generation data stack, with meaningful improvements to Amp’s data quality, query metadata, and internal architecture. We also expanded ampersend’s accessibility with practical examples, enhanced observability, and new tooling that showcases agent-based access to The Graph in real-world workflows involving payments.

:tada: Notable December Accomplishments

Protocol

  • Deployed Graph Horizon upgrade to production!

    • Over 95% of query volume and indexer stake was migrated to Horizon

    • Upgraded Horizon in the process of migrating (17k allocations)

  • Discussed initial plans for Amp on the Network (which will use Horizon) during Indexer Office Hours

  • Finished the Rewards Eligibility Oracle (REO) audit - ready for testnet

Gateway, Explorer, Studio, graph-node

  • Resolved Horizon-related bugs and handling the deprecated Analytics Subgraph fields in Explorer

  • Migrated to authenticated call for SafeKit API use in Studio

  • Added support for Horizon allocations using TAPv2 receipts

  • Now supporting dual dispute managers for attestation verification (legacy and Horizon)

Amp

  • Added new useful UDFS for encoding/decoding hex data and parsing floats

  • Executed EVM-RPC extractor data quality improvements

  • Made a series of improvements to Rust crate structure, improving separation of concerns

  • Added metadata to batch queries to inform the client of the block range executed over

ampersend

:telescope: What’s Next:

  • Full-fledged preparation for EthDenver

  • Add Solana extractor to Amp :fire:

  • In addition to ampersend’s existing support of MCP and A2A agentic interaction, add HTTP