The Graph Indexer Office Hours #133

Events By Nov 20, 2023 No Comments
TL;DR: The Graph protocol is moving to a permissionless system for RPC providers, and the next Agra hard fork will occur on November 28.

Opening remarks

Welcome to Index Office Hours 133!

This is a regular meeting where ecosystem participants come together to discuss the most important and relevant topics for The Graph community.

The latest GRTiQ episode features Tegan Kline, CEO and co-founder of Edge & Node.

Repo watch

  • Erigon version 2.54.0 is now available, including several important bug fixes and improvements. Polygon users must upgrade to this release before the Agra hard fork on November 28.
  • A new release of Geth fixes a potential data corruption issue in the path scheme.
  • Firehose Ethereum version 2.0.0-rc.1 is now available.
  • Nethermind version 1.22.0 is now available and includes several memory management improvements.
  • Teku new release 23.11.0 is now available.
  • There are no new releases for The Graph protocol or its subprojects.

Protocol watch

Project watch

  • Sepolia, the new testnet for The Graph, is almost fully deployed.
  • Several fixes to the contracts repository have been made.
  • The Edge & Node team is working on deployment to Sepolia.
  • The Explorer UI is now running on Sepolia.

Open discussion

  • Tim, product manager from Edge & Node, asked about updating documentation for indexers who are deploying to Sepolia.
  • Tim asked about the impact of deploying to Sepolia on the broader Graph community.
  • Juan said that the Arbitrum chain will not be supporting Sepolia.
  • Juan said a checklist of items needs to be completed before deploying to Sepolia.
  • Jim said that the Explorer UI can interact with contracts on Sepolia.
  • Tim asked about how to test the Explorer UI.
  • Vince said that the contract deployment should be set.
  • Vince said a few flags may need to be turned on before indexers can connect to Sepolia.
  • Derek said that many indexers are already running JSON RPC services.
  • Derek said he wants to learn more about the benefits of offering a JSON RPC service.
  • Juan said that there are a few pros and cons to indexers offering a JSON RPC service.
  • Juan said that The Graph protocol team is open to providing more support for JSON RPC services.
  • Tim asked about the potential for indexers to profit from running a JSON RPC service.
  • Derek said that DRPC is an example of a profitable JSON RPC service.
  • Jim said indexers are running JSON RPC services because they already have the infrastructure.
  • Brian said that The Graph protocol could offer JSON RPC services to get earlier in the developer journey.
  • Tim asked about the possibility of chains powering RPC endpoints.
  • Derek said DRPC is a good example of how indexers can provide RPC endpoints.
  • Juan said that chains are interested in getting aggregate views of RPC usage.
  • Derek said that DRPC is focused on providing insights into RPC usage.
  • Juan said the Graph protocol team uses Proxy D as a load balancer for indexer RPC requests.
  • Vince said the Graph protocol team plans to move to a permissionless system for RPC providers, with each data service defining its stake requirements and arbitration process.
  • Ford proposed a core protocol with staking and permissionless ability to add data services.
  • Jim said that The Graph protocol team still needs to be ready to provide a timeline for V2.

This week’s Index Office Hours 133 was a great success. We discussed various topics, including the potential for indexers to profit from running a JSON RPC service, the possibility of chains powering RPC endpoints, and the future of The Graph protocol. We also had some exciting announcements, including releasing the new Dash era PO and the upcoming roadmap discussion.

We look forward to seeing you all again next week!

Thank you for joining us for Index Office Hours 133!


A passionate, highly organized, innovative Open source Technical Documentation Engineer with 4+ years of experience crafting internal and user-facing support/learning documentation. Leverages a background in computer science to write for highly technical audiences and API docs and is the leader of the technical writing mentorship program.

No Comments

Leave a comment

Your email address will not be published. Required fields are marked *