# This month in curation #19 | November 22 **URL:** \ **Category:** Ecosystem Updates\ **Tags:** curator, curator-newsletter\ **Created:** [November 28, 2022, 7:14pm UTC](https://forum.thegraph.com/t/this-month-in-curation-19-november-22/3751 "2022-11-28T19:14:19Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![Slimchance](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.thegraph.com/slimchance/32/409_2.png) [@Slimchance](https://forum.thegraph.com/u/Slimchance)\ **Post date:** [November 28, 2022, 7:14pm UTC](https://forum.thegraph.com/t/this-month-in-curation-19-november-22/3751/1 "2022-11-28T19:14:19Z")
This Month: - The Graph Network is turning 2 years in December! - The Graph now supports Solana powered by Substreams! - Graph Improvement proposals detailing an `Arbitrum layer 2 deployment`, `Curation 1.x` and the `Epoch Block Oracle` ![Birthday](https://us1.discourse-cdn.com/flex020/uploads/thegraph1/original/2X/b/bc7ec26b50d7a64bfa8d08df351c33aea972fbaf.png) **The Graph Network is turning 2 years!** - On december 17th 2020, The Graph Network [launched on mainnet](https://thegraph.cmail19.com/t/j-l-vkiljkl-iyhiuldkkr-y/). Since then, over 200 Indexers, 10,000 Delegators and 2,500 Curators have joined the journey. Come celebrate The Graph’s birthday at one of six community-led birthday events worldwide, or tune in to the special birthday twitter spaces on december 15th. - Join members of The Graph community for an evening of celebration filled with tasty food, refreshing beverages, and a special birthday POAP. In addition to celebrating this milestone and the decentralized future, this event is also a great opportunity to learn more about the latest with The Graph and meet participants in The Graph ecosystem that live in your area! Space is limited - RSVPs are required. Looking forward to an interstellar evening with you! - Can’t make it to one of the in-person events? Be sure to join the community on [The Graph Twitter](https://thegraph.cmail19.com/t/j-l-vkiljkl-iyhiuldkkr-o/) for a special birthday Twitter Spaces on **Thursday, December 15th at 9:00 am PST.** During this special online event, you will hear from core developers and other leaders in the ecosystem! [Set a reminder](https://thegraph.cmail19.com/t/j-l-vkiljkl-iyhiuldkkr-b/) for the Space on Twitter. ![Solana](https://us1.discourse-cdn.com/flex020/uploads/thegraph1/original/2X/5/5c4b434603654a0a11cb126384036fbbe00b2e05.jpeg) **The Graph Now Supports Solana with Substreams** The Graph Foundation is excited to announce support for Solana with substreams - Read the full announcement [here](https://thegraph.com/blog/indexing-solana-substreams/). - The Solana developer community can now begin using The Graph to build lightning-fast dapps. - Substreams are developed by [StreamingFast](https://thegraph.com/blog/core-dev-grant/) , a core developer in The Graph ecosystem. ![rome](https://us1.discourse-cdn.com/flex020/uploads/thegraph1/original/2X/b/beec160da9f3d1ca5d47339e03cc22f6fa285596.jpeg) **Graph Improvement Proposals** GIP-0037: **The Graph Arbitrum deployment with linear rewards minted in L2** | [Forum](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551) | [Radicle](https://app.radicle.network/seeds/pine.radicle.garden/rad:git:hnrkrhnth6afcc6mnmtokbp4h9575fgrhzbay/remotes/hybhtwejbt1845jumra1n9jixreu7dmf8dybj3gwg3q1sr6uobikeq/tree/arbitrum-deployment-linear/gips/0037-arbitrum-linear-rewards.md) | [HackMD](https://hackmd.io/@N6uqeJqKRhS_geEwjyATnQ/r1PsHBIei) - Like GIP-0034, this proposal introduces a new deployment of The Graph’s smart contracts to the Arbitrum One Layer 2 blockchain - The Layer 2 implementation on Arbitrum was discussed during The Graph Core Devs Call #16 from [28:08](https://youtu.be/3Wom4uX1m3Y?t=1688). This call covered GIP-0037, as well as GIP-0034 and GIP-0031. - This GIP is presented as an alternative to _GIP-0034: The Graph Arbitrum deployment with a new rewards issuance and distribution mechanism_ - The main differences between GIP-0037 and GIP-0034 are as following GIP-0038: Epoch Block Oracle | [Forum](https://forum.thegraph.com/t/gip-0038-epoch-block-oracle/3323) - When indexers are indexing a subgraph, they allocate some of their stake towards that subgraph. Indexers may serve queries on subgraphs with open allocations, and they will accrue Indexing rewards. To collect these Indexing rewards, allocations must be closed with a valid proof of indexing (POI) for the first block of the current epoch. - If the network is to support indexing rewards for subgraphs indexing networks other than Ethereum mainnet, Indexers need to know which block POI to submit when closing an allocation. - This proposal introduce an “Epoch Block Oracle” to specify the `currentEpochBlock` on other chains. - An Epoch Block Oracle subgraph will index a simple on-chain [Data Edge](https://forum.thegraph.com/t/gip-0025-dataedge/3161), which will track the “Epoch Block” for all networks supported for indexing rewards. Indexers will use block hashes specified by the subgraph to close their allocations for subgraphs indexing a given network. GIP-0039: **Curation v1.x** | [Forum](https://forum.thegraph.com/t/gip-0039-curation-v1-x/3613) - This proposal aims to improve the experience of subgraph- and dapp developers. - Curators signal to the network that a particular subgraph contains valuable data by depositing GRT into a bonding curve, minting curation shares. They may also burn their curation shares to withdraw GRT. Today, the bonding curve is not flat. The GRT valuation of curation shares will increase or decrease when curators mint or burn curation shares respectively. - GIP-0039 propose to flatten the bonding curves for subgraphs deployed on Arbitrum. - Curation v1.x and the roadmap to Curation 2.0 was discussed during The Graph Core Devs Call#16 from [41:32](https://youtu.be/3Wom4uX1m3Y?t=2492). GIP-0040: **L2 Bridge and Protocol Deployment** | [Forum](https://forum.thegraph.com/t/gip-0040-l2-bridge-and-protocol-deployment/3695) - This proposal outlines a gradual move to Abitrum Layer 2. Most of the contracts will be deployed with no functional changes, so staking and curation can be done in the same way as in L1. Users can move GRT to L2 using the bridge proposed in GIP-0031. \*\*The L2 deployment is proposed to happen over 3 stages: - `Stage 1`: Deploy a mirror of the L1 contracts to L2 Arbitrum with Indexing rewards _disabled_. This stage includes an L1-L2 bridge as proposed in GIP-0031. Curation will be deployed with flattened bonding curves as proposed in GIP-0039. - `Stage 2`: Upgrade the protocol to support indexing rewards on L2. - `Stage 3`: Add migration helpers to facilitate users moving stake, delegations and subgraphs from L1 to L2. - GIP-0040 is for the deployment of `Stage 1`. In the future, separate GIPs will be written for `stage 2` and `stage 3`.