[FEATURE] Paranets

[br41nl3t]

No description provided.

[botnumberseven]

@u-hubar

It appears addStake function will be removed from Staking and StakingV2 ABIs. Not sure what would be used as a replacement for regular staking process. Anyway, that change will make these ABIs incompatible with current chain data, as addStake is used at the moment. Would be nice to keep it there.

When AccumulatedOperatorFeeRestaked is emitted in Profile, i assume regular staking events like stake_increased and shares_minted are also emitted. Correct?

Would it be possible to make AccumulatedOperatorFeeWithdrawalStarted event in Profile similar to StakeWithdrawalStarted and show old_accumulated_operator_fee and new_accumulated_operator_fee. It's a bit easier to track it that way, than only using amount value.

[br41nl3t]

@botnumberseven

The function I changed the name for was never used for manual staking, there is a separate function with the same name for that. Anyways, I will revert back the name change just to keep things less complicated.

Correct.

New will always be 0 as there is no choice of how much to withdraw/restake, it always takes full amount. I can add possibility to choose amount if needed, just didn't really see the reason for why it would be useful

[botnumberseven]

@u-hubar
Oh, I missed we have two functions with the same addStake name. False alarm then.

Restake/withdraw amount.
If there is no delay for op fee withdrawal/restaking, then i agree, there is no value to allow custom amount here.

If there is a delay, custom amount might make sense:

1. User wants to withdraw a portion of funds and restake a portion of funds. Without custom amount they would need to withdraw first, wait 28 days, then stake.
2. User wants to restake, but their node of choice does not have enough room to accept all of his stake. Again they would have to withdraw, wait 28 days, then stake.
3. User wants to split his accumulated op fee for 2+ nodes. They would need to withdraw, wait 28 days, then stake.