Provision management proposal for the explorer

Trigger	Condition	Calls
STAKE	provision exists	`HorizonStaking.stakeToProvision()`
STAKE	provision does not exist	`HorizonStaking.stake()`
`HorizonStaking.provision()` / `HorizonStaking.provisionLocked()`
UNSTAKE	during transition period and `amount < idle stake`	`HorizonStaking.unstake()`
UNSTAKE	during transition period and `amount > idle stake`	Do not allow.
UNSTAKE	after transition period and `amount < idle stake`	`HorizonStaking.unstake()`
UNSTAKE	after transition period and `amount > idle stake`	`HorizonStaking.thaw()`
WITHDRAW	funds fully thawed from a legacy unstake	`HorizonStaking.withdraw()`
WITHDRAW	after transition period and funds fully thawed from provision	`HorizonStaking.deprovision()`
`HorizonStaking.unstake()`

When an indexer stakes in the explorer:

If the indexer has an existing provision for SubgraphService
- Call stakeToProvision() shortcut to directly stake and add funds to the provision
If the indexer does not have a provision for SubgraphService
- Call stake() to get funds into the protocol
- Call provision() to create the provision
  - this needs to be provisionLocked() if the caller is a vesting contract

When an indexer unstakes in the explorer:

Stage 2: transition period
- If the amount to unstake is less than the idle stake:
  - Call unstake() to start thawing the funds
- If the amount to unstake is greater than the idle stake - this is the tricky one
  - Call thaw() to start removing the funds from the provision, funds being the difference between idle stake and amount to unstake
    - Once thawed we would need to call unstake() and get trough a thawing period AGAIN.
  - Unless time remaining in transition period…..
Stage 3: Horizon
- If the amount to unstake is less than the idle stake:
  - Call unstake() for immediate withdrawal
- If the amount to unstake is greater than the idle stake:
  - Call thaw() to start thawing the funds from the provision

When an indexer withdraws in the explorer:

Stage 2: transition period
- Condition: funds need to be fully thawed from a previous call to unstake()
  - Call withdraw() to get the funds out of the protocol
Stage 3: Horizon
- Condition: funds need to be fully thawed from a previous call to unstake()
  - Call withdraw() to get the funds out of the protocol
  - Note that on stage 3 further calls to unstake() will automatically withdraw funds, so no new calls to withdraw() would be needed. However we need to keep it in case someone initiated an unstake() before. Eventually the withdraw() code will be removed.
- Condition: funds need to be fully thawed from the SubgraphService provision
  - Call deprovision() to get the funds out of the provision and into idle stake
  - Call unstake() to get the funds out of the protocol - unstaking is immediate

Ideas to simplify explorer

During the transition period
- Don’t allow calling thaw() - this means that if an indexer provisions stake to the SubgraphService the explorer will not expose UI elements to allow thawing those funds.
- We can provide instructions to perform a thaw() call via Etherscan if someone needs it for some reason.