<aside> 💡

This document explains how the protocol state is mutated, transferred—or remains unchanged—with Graph Horizon. It aims to clarify the actions required from each protocol participant following the upgrade assuming they wanted to continue to operate indexing subgraphs and serving queries through the SubgraphService data service.

</aside>

• Stake will be initially be considered idle, i.e not assigned to a data service. | Idle stake needs to be assigned to the SubgraphService by calling HorizonStaking.provision(). | | | Stake that was thawing before the upgrade | - Stake will continue to thaw
• Once thawed it can be removed with withdraw() | - | | | Delegation parameters | - Delegation parameters set before horizon will NOT be automatically migrated. | Service provider needs to set the delegation cuts with HorizonStaking.setDelegationFeeCut() for each payment type (indexing rewards and query fees). | | | Operator access | - Operators authorized before horizon will be automatically authorized to operate on the SubgraphService provision
• Note that in Horizon operators allowed on a provision can manage it’s stake, parameters and delegation cuts. In the SubgraphService they can register the service provider, manage allocation lifecycle and collect fees. | - | | | Subgraph indexing registration and configuration | - Indexers’ registration will NOT be automatically migrated.
• Indexers’ rewards destination address will NOT be automatically migrated. | Indexers need to re-register via SubgraphService.register() and re-configure their rewards destination address with SubgraphService.setRewardsDestination() (though the register call allows specifying a rewards destination address). | | | Existing (legacy) allocations | - They are NOT migrated to the SubgraphService however the staking contract will allow collecting and closing them during the transition period. | - | | Delegator | Existing delegation in the protocol | - Delegation assigned to a specific indexer
• Automatically assigned to (serviceProvider, SubgraphService) where the service provider is the indexer. | - | | | Delegation that was thawing before the upgrade | - Stake will continue to thaw
• One thawed it can be removed with withdrawDelegated(). Note that the function signature is what differentiates the new withdraw flow from the legacy one. | - |

Recommended “migration guide” for a service provider after the Horizon upgrade:

• Close their subgraphs operation in HorizonStaking
  • [indexer stack] Close all existing allocations in the staking contract: HorizonStaking.closeAllocation()
  • [indexer stack] Collect any pending query fees: HorizonStaking.collect()
• Start subgraphs operation in SubgraphService
  • [indexer stack] Create SubgraphService provision automatically: HorizonStaking.provision()
  • [indexer stack] Register in the subgraph service: SubgraphService.register()
  • [explorer] Set delegation parameters: HorizonStaking.setDelegationFeeCut() for indexing rewards and query fees (two calls)

Additional recommendations for service providers during the transition period:

• Do not unstake() if the time remaining on the transition period is less than the thawing period. Once the transition period ends the unstaking is immediate.