Temporarily increase the staking increase limit

[areshand]

Description

Type of Change

• New feature
• Bug fix
• Breaking change
• Performance improvement
• Refactoring
• Dependency update
• Documentation update
• Tests

Which Components or Systems Does This Change Impact?

• Validator Node
• Full Node (API, Indexer, etc.)
• Move/Aptos Virtual Machine
• Aptos Framework
• Aptos CLI/SDK
• Developer Infrastructure
• Other (specify)

How Has This Been Tested?

Key Areas to Review

Checklist

• I have read and followed the CONTRIBUTING doc
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I identified and added all stakeholders and component owners affected by this change as reviewers
• I tested both happy and unhappy path of the functionality
• I have made corresponding changes to the documentation

[musitdev]

stake increase limit is temporary and should not be activated when network become public. By merging in l1-migration we make it public. We should do like the epoch change, use a temporary framework to update the stake. I think we can even use the epoch change one because staking reward update has been merged in movement-migration branch as I remember.
I add the staking test and pass all unit test.

[0xmovses]

@musitdev That's a way yes, we could also just merge it then merge another PR that undoes this change prior to production migration next week. I think it's less overhead to do it in like that.

[musitdev]

Yes, but we need to apply both framework (the one with the staking increase deactivated and the final one) during the migration so if you have updated one it's harder to upgrade the first. What I say is that we can use the epoch activation one to load the initial staking and avoid to load/unload a specific framework to add the initial staking.

[0xmovses]

@apenzk can we update the MIP to reflect this. Or have discussion on this formula.

[apenzk]

0.2176 bps is equivalent to APY = 10%. The value for 10% APR would be 0.2283.

Since APY is more familiar to the public the above code looks good and i agree its better to state 10% APY

I will update the MIP

cc @musitdev

[apenzk]

i misunderstood the discussion in the call - i thought you wanted to frequently or continuously update this configured number.

[apenzk]

movement-network/MIP#124 is updated. And i added some section about the APR to APY conversion.

[areshand]

Yes, but we need to apply both framework (the one with the staking increase deactivated and the final one) during the migration so if you have updated one it's harder to upgrade the first. What I say is that we can use the epoch activation one to load the initial staking and avoid to load/unload a specific framework to add the initial staking.

how to load the initial staking? we can also run a script to lower the threshold back to 50% without updating the framework.