Add support to Staking contract to separate operational from financial capabilities about flow-core-contracts HOT 4 OPEN

Made a small edit to your proposal to the second capability. This makes sense.

One question: I assume that most node operators and delegators are using the staking collection, so I am think that we just make these three new interfaces for the staking collection contract, or do you think we need to add the interfaces to both the core staking contract and the staking collection?

from flow-core-contracts.

I don't have a strong opinion on that. I think as long as there's a way for operators to delegate permission for each of those capabilities (particularly 1 & 2), either should be fine. Is it simple to switch to using the collection if you're currently using the core staking contract?

from flow-core-contracts.

yes, this transaction updates any account to use the staking collection, even if they are already using a different setup:
https://github.com/onflow/flow-core-contracts/blob/master/transactions/stakingCollection/setup_staking_collection.cdc

from flow-core-contracts.

I think the stable cadence upgrade would be a perfect place to introduce this feature since it is a great use case for entitlements. I'll try to get it added to the feature branch relatively soon

from flow-core-contracts.