Summary
In this meeting, the Core Devs and the community have an open discussion around new GIPs from Figment and solutions to unintended behavior from some curators while participating in the network.
Meeting Participants explore:
- GIPs 13-15 from Figment introducing the Network Graph and Network Graph API
- How Figment’s Network Graph and StreamingFast’s Firehose solutions interact within the protocol
- The need for accessible core design constraints for developers
- Obstacles in the Curation Mechanism
- Solutions
Detailed notes regarding each topic with timestamps can be found below.
Figment GIPs (1:21)
Figment recently joined the graph as a core developer focusing on:
- Improving Indexing Performance
- Adding support for native network subgraphs
- Expanding multi-blockchain support
- They have posted the details for three GIPs on The Graph forum:
Figment’s GIP-13 would introduce the concept of Network Graphs to the protocol. A Network Graph is an ordered, structured and versioned set of data extracted from layer one blockchain networks. Every subgraph developed would be a derivative of a Network Graph. Self-hosted operations could utilize Network Graph API as a source, resulting in:
- Indexers being incentivized to create and support more Network Graphs
- Money spent on external blockchain data services would be redirected to The Graph encouraging GRT flow
- Self-hosted operations could directly query the Network Graph API
GIP-14: Subgraph GraphQL Processing
Figment’s GIP-14 would add a graphQL call function to the subgraph generation process this would allow subgraphs three types of calls:
- Calls for base layer network data (Using Network Graph and the Network Graph API detailed in GIP-13)
- Calls to other subgraphs
- Calls to self
GIP-15: Network Indexers (manager – worker model)
Figment’s GIP-15 is the implementation of GIP-13, where indexers would index each blockchain network independently of subgraphs, allowing subgraphs to access data through the Network Graph API.
Network Graph Feedback (Alexander Bourget & Joseph | 2:27)
A detailed technical discussion about the indexing process within the Network Graph approach between Alexandre Bourget of StreamingFast and Joseph of Figment ensued. A meeting will be scheduled to further explore these details.
Alternative to the Firehose? (Brandon Ramirez | 15:05)
Brandon Ramirez of Edge and Node raised the question of whether the Network Graph approach is an alternative to the Firehose or if they are complimentary. Figment is in communication with StreamingFast to see how the solutions would interact in the ecosystem.
Core Design Constraints (19:09)
There was consensus that a resource should be made available that will inform new and current developers of core design constraints within the protocol. This will assist future collaboration as the number of developers within The Graph ecosystem increases.
Curation (20:52)
The curation mechanism was intended to be a communication method between subgraph developers and indexers. The goal was for subgraph developers and non-developer curators to be rewarded for signaling on valuable and relevant subgraphs. Since launch, honest curators have faced unintended interference from frontrunning bots and sandwich attacks.
Profit Scalping ( Sam Green | 24:20)
In an analysis of 63 subgraphs by Semiotic AI, they discovered 626 events by 201 unique curators where the curator bought and sold shares within two minutes of a subgraph’s deployment. This is an unintended behavior, disincentivizing curators to analyze subgraphs properly.
Median Amount Curated (Joseph | 34:24)
Joseph of Figment requested the median amount curated from Sam Green of Semiotic AI to evaluate return ratio of profit scalpers.
Solutions
Dynamic Curation Tax 36:10
The proposal to reduce curation tax from 2.5% to 1% is a steady state curation tax. A dynamic curation tax would see curation tax decrease as time goes by. This would disincentivize bot frontrunning and give curators time to analyze subgraphs. Community feedback and ideas are encouraged in the forums.
Subgraph Showroom 43:42
The Subgraph Showroom solution would see subgraphs deployed to main net in 2 stages. In the first stage, a subgraph would be listed in the show room for curators to analyze and signal. Subgraphs would calculate total signal and curators would receive a common value of share proportional to their signal. Stage two would introduce the bonding curve and the curation mechanism would return to normal.
Subgraph Showroom Prototype 45:00
Brandon Ramirez of Edge & Node developed a prototype of the subgraph showroom detailing the two stages. The prototype introduces a initialization exit phase in addition to the initialization phase in which the bonding curve reserve changes linearly from a flat curve to its reserve ratio.
Next steps regarding discussion about the subgraph showroom prototype would be defining the parameters of the initialization phase and initialization exit phase.
Stay Tuned!
Join us next month for The Graph’s Core Devs Meeting #8!
Keep up to date by joining discussions in the forum, following The Graph on Twitter or joining the Discord server.
For further discussion on the topics covered in The Graph’s Core Devs meetings, attend Indexer Office hours in the Graph Stage voice channel every Tuesday.
Access a full transcript of Core Devs Meeting #7 here, or watch it on YouTube!