Skip to main content

GRT $0.01972 1.06% Market cap $217.6M

GIP-0038: Subgraph Availability Manager

Council vote #45 on The Graph

Overview

Updated

Approved

Voting ended
Apr 27, 2024
Opened Apr 18, 2024
Submitted
Apr 18, 2024
Apr 18, 08:53 UTC
Members voted
6
One vote each, on Snapshot

Put to the Council by 0xb731a7…fd0a

Votes

  • Yes 6 votes
  • No 0 votes

How BitBasic reads the result

  • Approved when more Council members chose Yes than No.
  • Each member has one vote, and Snapshot keeps a member's last.

Description

GIP: 0065 Title: Subgraph Availability Manager Authors: Miguel de Elias miguel@edgeandnode.com [Link to full GIP] (https://github.com/graphprotocol/graph-improvement-proposals/blob/cf998623a4c8e90db7fc1c024c6179f812570c22/gips/0065-subgraph-availability-manager.md)

GIP Summary

GIP-0065 proposes the SubgraphAvailabilityManager to decentralize The Graph’s protocol. It replaces a single SAO with five oracle operators, requiring a consensus of three for actions on subgraph data. Deployed on Arbitrum One, it mediates between oracles and the RewardsManager, featuring a vote system with expiration limits. Governed by the council, the contract is non-upgradeable but replaceable.

Technical Advisory Board (TAB) review & vote

Reviewed by 6 members (all); Approved by 5 Rejected by 1 More on TAB's vote here.

Next steps

Once this GGP is approved:

  • This PR will be merged
  • The new SubgraphAvailabilityManager contract will be deployed with a RewardsManager address defined and set of Operators.
  • SAO Operators will start coordinating the deployment of new SAO instances.

See the vote on Snapshot Its discussion on the forum

How the Council voted

In the order they voted. Snapshot knows members by address only, so BitBasic doesn't name them.

Member Vote When
0x17118d…2c21 Yes Apr 23, 10:20 UTC
0x68afab…2b57 Yes Apr 24, 11:48 UTC
0x7eabe4…7fee Yes Apr 24, 19:40 UTC
0x38fa68…4da8 Yes Apr 25, 14:31 UTC
0xd201c9…22aa Yes Apr 26, 14:10 UTC
0x325256…ad8e Yes Apr 26, 16:55 UTC