Since Curation went online in July, The Graph Forum has been bustling with community input on Graph Explorer, Subgraph Studio, and Curation.
The procedure has already benefited from precise, practical ideas from the community. On the permissionless network, for example, users have complained about the difficulties posed by subgraph upgrade charges. This comment has influenced a new proposal to cut the curation cost for subgraph developers. Those who want to upgrade their subgraph on the network from 2.5 percent to 1%. The existence of a tax is critical. That’s because each time a subgraph on the network updates, the Indexers must perform computationally difficult labor to re-sync that subgraph.
Issues Raised by Community
Another issue raised by the community was front-running bots. Members of the community have proposed numerous approaches for preserving the benefit of curation. At the same time guarding against this type of exploitative behavior. At The Graph’s Core Devs meeting, viable solutions are still being debated in order to acquire a better understanding of their viability, potential fruition, and community support.
Users have also taken to Telegram and Discord channels to give criticism in addition to The Graph Forum. The Graph Foundation has also sponsored monthly Community Talk and Core Devs meetings. In order to keep the community informed about protocol progress. In The Graph ecosystem, these calls are a vital source of transparency.
Over 22,000 subgraphs have produced and delivered to The Graph’s Hosted Service by 23,000 developers. Over 180 subgraphs have transferred to The Graph Network using the Subgraph Studio since migration began in spring 2021. Audius, PoolTogether, and Reflexer are among the apps that have moved their subgraphs to The Graph Network. There are still additional dapps moving every day.
By employing a query market powered by Indexers, Delegators, and Curators, developers can rely on a fully decentralized stack. Developers no longer have to run expensive and time-consuming centralized infrastructure or servers in-house. A query market also implies that builders are building on infrastructure that can last indefinitely. Even if the company that produced it goes out of business.
The Graph Network: No Downtime
Since its introduction, the Graph Network has seen no downtime, marking a significant step toward a genuinely decentralized Web3 stack. The Graph’s core developers aim to improve the way developers publish subgraphs in order to help dapps migrate to the network. Indexers participate at an increasing rate, with over 16,000 allocations completed to date. This allows for the indexing of trustworthy subgraphs while also rewarding Indexers for their efforts.
Curators have also been offering early feedback to core developers. In order to guarantee priority to all critical Studio and developer features. The Graph Explorer contains all subgraphs, curation statistics, and query fees data. To enable subgraph migration and inform new Curators into The Graph ecosystem, initiatives like Curation Station and dashboards like Graphscan have established in the community.
Currently, 35 Indexers (or 22 percent of all Indexers) index some of the most popular signaled subgraphs, such as Livepeer, with each subgraph served by an average of 4.4 Indexers and 33.1 Curators. To date, more over 3 million GRT have signaled, with each subgraph averaging 20K GRT.
The Three Core Developing Teams
Throughout this process, The Graph Foundation worked hard to decentralize the protocol’s basic development in order to maintain its long-term viability. StreamingFast and Figment are two new core development teams that have joined The Graph in the last six months to help scale the protocol. It also improves indexing performance, and multi-blockchain activities like StreamingFast’s Firehose stack.
These three core developer teams are working together on a protocol roadmap. Simultaneously sharing their progress at the Core Devs Meetings on a monthly basis.
For bringing protocol changes to the community and The Graph Council, The Graph has used a Graph Improvement Proposal (GIP) Process. The Graph Forum is where GIPs are offered and discussed getting feedback from subgraph developers, Indexers, Curators, and Delegators. Before being implemented, the GIPs are put up for a Snapshot vote to measure the community reaction, then by a vote by The Graph Council. Council sessions holds every two weeks, and meeting minutes are kept according to Chatham House Rules.
The Graph Network’s Improving Performance
The Graph Network’s performance is improving with the aid of the key developer teams! StreamingFast recently announced upgrades that might speed up indexing by 300 times. The Graph continues to place a premium on indexing efficiency in order to boost subgraph developer productivity.
Developers attracts to The Graph because of the low pricing. Developers pay query fees only for the data they consume through a Gateway, unlike existing blockchain data service providers. Furthermore, the Graph Network’s dependability allows development teams to concentrate their attention on their dapp rather than back-end infrastructure or servers, lowering infrastructure and operations costs.
The Graph is improving on a number of fronts in order to become the all-in-one indexing solution for a decentralized future.
Role in Protocol Evolution
The Graph community continues to play an important role in shaping the protocol’s evolution. Instead of being on the receiving end of centralized decision-makers, Web3 intends to empower consumers by providing them complete control over their data. This is done through a permissionless approach. The quality of a protocol’s user base determines its success. The Graph’s early triumphs and momentum would not have been possible without its enthusiastic community.
The Graph prepares a series of subgraph migrations to the decentralized network, a vital component of the Web3 vision, while the core developer teams work on a targeted set of enhancements that will make a huge impact in the experience of using the network. Its Workshops and The Arbitration Charter, respectively, make it easier to educate participants and settle conflicts.
The Graph positioned itself to be the catalyst for Web3 adoption through all of these efforts.
