TL;DR: Matthew from Pinax presented on scaling Substreams, explaining how to set up and monitor tier 1 and tier 2 nodes for processing blockchain data. The architecture involves tier 1 nodes that are chain-specific and tier 2 nodes that are blockchain-agnostic. The setup requires monitoring through Prometheus and Grafana, with proper hardware sizing depending on specific Substreams workloads and complexity….
indexers
TL;DR: Rem from Edge & Node continues presenting GIP-0070, which proposes changes to The Graph’s protocol economics. The proposal aims to address three main goals: maintaining network balance, enhancing incentive alignment, and sustaining continuous improvement. Key changes include introducing network payments and network rewards to replace indexing rewards, implementing dynamic query fee cuts, and establishing a new curation mechanism that…
TL;DR: The Graph Networks Registry is a repository that consolidates and standardizes network information for blockchains supported by The Graph. Before its implementation, core dev teams and others faced challenges with fragmented data and manual updates, leading to inefficiencies and inconsistencies. The registry now serves as a single source of truth that enables developers, indexers, and delegators to access reliable…
TL;DR: Key points introduced during the open discussion about GIP-0081: Indexing Payments:- The motivation for this proposal is to design a developer-friendly way to get subgraphs indexed.- Indexing agreements will stipulate the subgraph to be indexed and the price per unit of “work done” indexing.- The proposal includes two clauses to protect the gateway: a maximum amount for initial syncing…
TL;DR: Yaniv introduced GRC-20, a new standard for knowledge graphs that can be used across applications. Christophe shared the current implementation, including three major components: a sink that uses Substreams to read on-chain events, Neo4j for storing entities, and a GraphQL API server for exposing data to consumer apps. Indexers will be able to choose which spaces they want to…
TL;DR: Ricky shared his progress on indexer operations automation tools, including an Indexer Management Interface and a Curation Signal Allocation Optimizer. He showed several demo videos, including deleting subgraphs, quality of service metrics, and real-time ISA score. The session outlined a seven-step roadmap, with the ultimate goal being the integration of knowledge/note taking, AI agents, and a coding environment, all…
TL;DR: Rem from Edge & Node discussed the proposal for evolving The Graph protocol economics. The proposal aims to better meet participant needs, with this discussion focusing on consumers and providers (indexers), particularly aligning incentives with value delivery and transitioning to a demand-driven network. A key change involves having gateways play a larger role in matching indexers to consumer demands…
TL;DR: Major indexers, including Pinax and Upgrade Indexer, have completed their TAP migration. Multiple indexers reported issues with Graph Node v0.36.0, including PostgreSQL performance problems and migration difficulties. It was noted that v0.36.0 is not yet ratified for production use. Upcoming sessions will feature Yaniv Tal discussing GRC-20: Knowledge Graph, Ricky on indexer analytics, and Vince covering Kubernetes and Launchpad….
TL;DR: During IOH #185’s open discussion, the focus was on the Timeline Aggregation Protocol (TAP) migration status, which has reached approximately 82% of queries with two major indexers still pending. A key highlight was the discussion of a zero-downtime upgrade strategy using reverse proxy routing for the Upgrade Indexer, which is critical as it serves as a single point of…
TL;DR: The Graph’s TAP (Timeline Aggregation Protocol) migration deadline is December 3, 2024, with about 34% of indexers already upgraded, representing 81.6% of query volume. The Q&A discussion focused on configuration settings for TAP, particularly around RAV (Receipt Aggregate Voucher) requests and managing unaggregated fees, with experts recommending starting with default values and adjusting based on query volume. Opening remarks…