Dual staking

[jmoreira-valory]

Proposed changes

• Added dual staking support.
• Improved logic for refill requirement.
• ContractLogicError had to be replaced by a general Exception, because depending on the RPC provider it might raise other exception type.

Types of changes

What types of changes does your code introduce?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

[OjusWiZard]

it looks like we can avoid overwriting these requirement by just reading the on_chain_state also in the compute function, and having this logic there

[jmoreira-valory]

Yes and no.

The output of this method is the service asset requirements (native, tokens, dual tokens, etc) required to deploy a service from scratch.

On another method, we retrieve the bonded assets.

So, the requirements needed will be service_asset_requirements - bonded_assets

[jmoreira-valory]

I opted for this way to have separation between what's bonded and what's on the Safe. We can discuss.

[jmoreira-valory]

In other words, the following invariant must always be satisfied (*):

master_safe_balance + bonded_assets >= protocol_asset_requirements

=

master_safe_balance >= protocol_asset_requirements - bonded_assets

(*) Obviously, the value bonded_assets and master_safe_balance depend on the protocol state, but we have a methodology to compute these values.