The Graph Core Dev Call #24

:information_source: The 24th Core Dev call is happening this Thursday 2023-09-07T15:00:00Z.

Join us!

:point_right: Launch Meeting - Zoom

This is a recurring call where team contributors gather to discuss major updates from different working groups and brainstorm around active R&D tracks.

:calendar: Please subscribe to The Graph Foundation’s Ecosystem Calendar, so you don’t miss any of the upcoming calls!

:notebook: Tentative agenda:

  • CIP (Chain Integration Process) [Foundation]
  • Updates on GIP-0051 & GIP-0052 [Edge & Node]
  • Graph Node support for Arweave (new File Data Source) [Edge & Node]
  • Spyglass [Spyglass Pirate Collective]

:tv: The recording will be uploaded here.

Got something interesting to present and discuss? Feel free to propose any new topic by replying to this thread.

:rocket: The Graph Core R&D Workspace

As The Graph is being built in public and in a decentralized way, we’ve put together a new publicly accessible The Graph Core R&D Workspace . You can use this page to follow along with each working group’s progress on significant workstreams and access meeting notes and recordings.

:crystal_ball: Monthly Core Dev updates

Core development teams are now posting monthly updates in this forum section Core Team Updates - The Graph.
Soon you’ll also find regular updates from all Working Groups and Task Forces on all major components of The Graph stack. Stay tuned!

See you Thursday! :astronaut:



In Core Devs Call #24, several updates were discussed:

  • Chain Integration Process
  • GIP-0051 & GIP-0052 Updates (Bonding Curves and L2 Migration)
  • Graph Node Support for Arweave
  • Spyglass Demo

As always, the community was encouraged to ask questions and participate actively in discussions.

Chain Integration Process (03:50)

The Graph Foundation has introduced the Chain Integration Process (CIP) for community-driven addition of new chains to the network. Building on the success of the Migration Infrastructure Providers (MIPs) program, CIP allows anyone to propose and fast-track chain integration. It aims to broaden the network’s scope and align with web3 principles.

The process involves these three steps:

  1. Submit a proposal in The Graph Forum for community feedback.
  2. Test and validate the integration, working closely with core developers.
  3. Apply for Mainnet Integration based on community feedback and demand.

The initiative empowers community members, Indexers and developers to voice what chains the The Graph’s decentralized network should support next!

Visit this link for more information on getting a chain integrated!


Does Optimism need to go through this process since it never made it through the MIPS program?


The Graph Foundation will initiate the process for Optimism as a continuation of the MIPS program. A forum post will be created, followed by a test on the testnet. After successful testing, the proposal will be submitted to the council for approval.

GIP-0051 & GIP-0052 Updates (08:50)

The implementation of GIP-0051 and GIP-0052 aims to optimize The Graph’s network by addressing key challenges in query fee rebates and indexing rewards. GIP-0051 proposes to replace the current Cobb-Douglas rebate mechanism with an exponential one, eliminating the need for indexers to predict other indexers’ staking behavior. This change simplifies the protocol, removes the need for rebate pools, and reduces query fee burn from over 50% to less than 7%. GIP-0052 outlines a phased approach to shift 100% of indexing rewards to the Layer 2 (L2) Arbitrum network, enhancing scalability. At Core Devs Call #24 Tomas and Pablo shared updates on these GIPs and some of the current changes currently underway.

In regard to the implementation of GIP-0051, the process is divided into two steps. The first step, which was completed on September 5, involved a parameter change that adjusted the channel dispute epochs to just one epoch. This change was made to give Indexers more flexibility in closing their allocations and redeeming query fees. The second step, which is the actual contract upgrade, is scheduled for September 10.

Indexers are advised to ensure they are running v0.20.20 following this contract upgrade as it will be the minim Indexer version required.** Additionally, a specific warning was issued for Indexers about a "danger period" around the contract upgrade date. **If Indexers close allocations within one epoch before the contract upgrade, they risk losing their query fees.**

GIP-0052 focuses on adjusting the indexing rewards on different networks. Specifically, the rewards on the Arbitrum network will be increased, while those on the mainnet will be decreased. The first adjustment is set for September 10, where the rewards on Arbitrum will be increased to 25%. A second increase to 50% is planned for September 24, provided there are no major issues. The community has been using the newly launched Transfer Tools without significant problems, which is a positive indicator for the planned increases. Further adjustments are planned but come with additional requirements, such as a certain number of Indexers and subgraphs transitioning to Arbitrum.

Both GIPs are being combined into a single upgrade process to minimize the operational overhead involved in implementing these changes.

Graph Node Support for Arweave (File Data Sources) (18:59)

Marcus Rein, who works in developer relations and developer success for Edge & Node, presented an update on graph node’s support for Arweave as a file data source. The team is currently focused on a “file data sources push,” aiming to integrate Arweave and IPFS into subgraphs. Arweave serves as an off-chain data source, a significant new feature that allows for more extensive data integration into subgraphs.

In the call, Marcus showcased a demo subgraph that indexes a smart contract deployed on Polygon. The smart contract references both IPFS and Arweave data in its events, making it an ideal example to show off its capability of indexing content from both Arweave and IPFS. Marcus explained that the data from these sources is brought in as a string, allowing developers the flexibility to organize it as they see fit. The presentation was an exciting example of how builders will be able to implement Arweave as a file data source.

Check out the subgraph from the demo here!

Spyglass Demo (28:57)

Lastly, Jordan Rein presented an update on Spyglass, a Substreams registry and data visualization platform that makes Substreams accessible and viewable.

Spyglass features a registry of community uploaded Substreams, where users can upload Substreams and visualize data in real-time, offering a high level of customization and fine-tuning. Users can utilize an easy quick start interface where they can choose their endpoint, map modules and timeframe and subsequently visualize Substreams data. The team aims for Spyglass to become a decentralized registry of Substreams with community involvement, offering features like one-click deployment (at a later date) to The Graph and real-time notifications and plans to launch the platform soon.

Jordan emphasized the platform’s efficiency compared to traditional methods, stating that through the implementation of Substreams, it takes significantly less time to create meaningful dashboards on Spyglass.

Stay Tuned!

Kevin wanted to remind everyone that The Graph Builders Office Hours happens every Thursday! Stop in and say hi and share what your buiding! You can find it on the calendar below.

Join us next month for Core Devs Call #25!

Keep up to date by joining discussions in the forum, following The Graph on Twitter or joining the Discord server.