Horizon upgrade stages

For easier reference we split the upgrade timeline in three different stages:

• Stage 0: current protocol
  • Starts on protocol genesis
  • Ends when the Horizon upgrade is deployed
• Stage 1: transition period
  • Starts when the Horizon upgrade is deployed
  • Ends when governance signals intent via a contract call (expected to last ~2 months)
• Stage 2: Graph Horizon
  • Starts when the transition period ends
  • No end in sight 😀

Proposed strategy for upgrading the Graph Network subgraph

The main goal we want to achieve is to support the Horizon upgrade with the least amount of changes to the Network subgraph (see Stage 1):

• This means keeping the Subgraph service data within the Network subgraph.
• No breaking changes (if possible)
• This would allow other components for an easier integration (no subgraph endpoint changes, no huge entity redesigns, etc)
• This goal should be achieved by Stage 1 described below.

The end state however is to have each data service maintain it’s own subgraph, so we would have to eventually split the Network subgraph into at least two, one for Horizon core data and then one for each data service, starting with the Subgraph Service. This goal can be achieved after Stage 2.

Stage 0

The Graph Network subgraph indexes all protocol data, knows about everything for all participants, for example:

• Indexer details, including total stake, allocated stake
  • Allocation details, including tokens allocated, subgraph deployment data
• Delegator details
• Curator details