This month in curation #16 | June 22

This month:

  • Graph Day & Graph Hack was held in San Francisco, 2-5 june

  • Substreams will massively improve indexing performance

  • The roadmap for sunsetting the Hosted Service has been announced

  • Cosmos Hub beta integration is live

  • GIP-0030 to GIP-0033





Graph Day & Graph Hack | Blogpost

  • On June 2nd, the world’s brightest dreamers & doers gathered for Graph Day at The historic Palace Of Fine Arts, San Francisco.

    • Graph Day was livestreamed, and the recording can be found here.
  • Following Graph Day, developers, innovators and creatives put their minds together during Graph Hack.

    • Hackers competed to win nearly $500k in prizes. The submissions can be found here.





Substreams | Blogpost

  • One year ago StreamingFast joined as a Graph Core Developer team to work full-time on The Graph ecosystem.

  • StreamingFast brought Firehose, a high-performance method of ingesting data from blockchains and started integrating it into to The Graph. At that time, an extremely complex subgraph could take weeks to sync, creating friction for developers building on The Graph. StreamingFast created a prototype called Sparkle, which helped decrease sync time on that subgraph from weeks to around six hours.

  • Now, StreamingFast has evolved Sparkle’s capabilities and created Substreams that can scale across all subgraphs on all chains.

  • How Substreams work:

    • RPC-based Subgraphs have a linear indexing model for processing blockchain data (i.e. they process events one at a time, in order). They do so via polling API calls to Ethereum clients.

    • Firehose technology replaces those polling API calls with a stream of data utilizing a push model and sending data to the indexing node faster. This helps increase the speed of syncing and indexing.

    • Substreams take things even further by enabling massively parallelized streaming data. Substreams can be combined and aggregated in powerful new ways to feed data into subgraphs or end-user applications in a fraction of the time. With substream parallelization, some subgraphs could sync more than 100x faster.





The Road to Sunsetting the Hosted Service | Blogpost

  • After nearly 4 years of supporting subgraphs for web3 dapps, the hosted service will be sunsetting in Q1 2023 with dapps migrating to the decentralized network.

  • To help developers migrate their subgraphs, Migration Grants are available to help bootstrap curation signal and initial query fees. If your dapp is migrating a subgraph, apply here

  • Core developers and support engineers are available to walk teams through the entire migration process, from understanding the technical steps, to KYCing for the grant, to co-marketing opportunities, as well as anything else migrants need to get comfortable with the process.

  • The sunsetting of the Hosted Service is a three-phase process unfurling between now and Q1 2023:

    • Q3 2022: Cease new subgraph deployments to the Hosted Service

      • During this phase, developers will still be able to upgrade existing subgraphs on the Hosted Service but all new subgraphs will need to be deployed via Subgraph Studio to the The Graph Network.
    • Q4 2022: Stop all upgrades from Hosted Service accounts

      • In this phase, all upgrades to subgraphs must be made through Subgraph Studio and subsequently published to the decentralized network.
    • End of Q1 2023: Fully phase out Hosted Service Subgraphs

      • At the end of Q1 2023, subgraphs will no longer be supported for any chain that is integrated with the decentralized network.





Cosmos Hub Integration | Blogpost | Docs

  • The Graph’s Hosted Service has completed a beta integration of Cosmos Hub

    • This implementation, spearheaded by core dev Figment , marks The Graph’s expansion into the Cosmos ecosystem and paves the way for many more to come.

    • The Cosmos Hub beta integration started in 2021 and now enables The Graph’s hosted service to index Cosmos Hub data.





Graph Improvement Proposals

GIP-0030: Minimum Curation Amount for Indexing Rewards Eligibility | Forum

  • This proposal aims to mitigate economic security risks to the protocol.

  • The proposal will introduce a new protocol parameter: minimum_signal.

    • minimum_signal will initially be set to 500 GRT.
    • Subgraphs with less signal will not be eligible for receiving indexing rewards.

GIP-0031: Arbitrum GRT bridge | Forum | Github

  • This proposal presents the specification for a set of contracts that will act as an Arbitrum bridge for GRT, i.e. allowing users (or contracts) to transfer GRT to the Arbitrum One Layer 2.

    • The bridge is based on the standard Arbitrum implementation and following Livepeer’s example.
    • The bridge gives the Graph Council the ability to pause, upgrade and generally control the bridge to recover from potential issues.
  • This would be the first step towards a “devnet” deployment of The Graph protocol to Arbitrum One, that would allow the community to evaluate it as a potential L2 scaling solution.


GIP-0032: Make GNS signal transferrable | Forum

  • This proposal would allow curators to transfer their GNS shares.

  • The proposal outlined a few usecases:

    • A developer that curated the initial signal and then wants to move it to a different address like a multisig.
    • A concierge application that setups a subgraph and mints some signal, which eventually needs to delegate the ownership to a different beneficiary.
    • A curator that needs to reorganize wallets.

GIP-0033: Osmosis indexing for Graph node | Forum

  • This proposal describes the Osmosis integration into Graph Node.

    • Osmosis is a decentralized, cross-chain automated market maker (AMM) protocol build on top of the Cosmos SDK.
    • The Osmosis blockchain is made up of free, public, and open-source software.
  • Integrating Osmosis will set a foothold on the Cosmos ecosystem integration and will keep expanding The Graph’s market and make its multi-chain vision a reality.

4 Likes