| Table of Contents |
|---|
...
Epic – FIO staking
Stories
Produce design spec, and revise FIP-21. (1 week Complete)
review internal, and community.
FIO Staking Development (3 weeks In progress 15% complete)
implement the solution as per FIP-21 and detailed development spec.
Started work March 29
constants implemented
staking global state implemented
account staking implementation implemented
port existing work to new contract fio.staking, completed
make shell of the new contract and integrate into the build.
integrate all table implementations for staking into fio.staking contract.
integrate stake and unstake shell into fio.staking contract.
Develop new logic to permit new contracts and system accounts to be added to the FIO protocol without mandatory core upgrades (completed, in QA for Bahamas)
implement and test actions to update global state for staking. In progress (20% completed)
implement stakefio (completed)
implement unstakefio (75% completed)
implement modified locking mechanism to support unstakefio (in work)
impelement and test incgrewards
implement and test
clrgdailyrewimplement and test
incgstkmint
adapt usable balance logic
adapt voting power logic
mature implementation of unstake
no existing general locks
update existing general locks
transfer
transfer using pub key
bpclaim
bpclaim
resetclaim
updbpclaim
Dev test
dev test cases
no pre-existing locks
pre existing main net locks
pre existing general locks
use existing main net locked account to create general lock
pre existing main net AND general locks
develop tests matching test plan in design spec.
internal code review
internal testing review.
perform QA and resolve all issues (comprehensive QA analysis)
Acceptance testing review by product owner.
FIO staking – Security/Performance testing (dev net) (1 week)
develop tests to load system and drive volume of requests (we desire a max stakes test, and also a volume of staking unstaking requests once loaded maximally) performance test plan is still TBD.
Rollout testing (dev net) (2 days)
load previous version of contracts, perform contract MSIGs, repeat load testing.
Test net testing – (1 week)
roll out msigs, perform subset of functional tests on test net (tests to be performed are TBD)
Main net rollout (2 days)
roll out MSIGs, perform minimal success testing to verify deployment (tests to be performed are TBD).
security of the new locking actions will require relatively complete QA testing (a test plan will be published).
...
3/30 Made strategic decision to place staking into its own distinct contract and account fio.staking.
during implementation it became obvious that the implementation of staking by adding actions and tables into the fio.system contract would considerably contribute to the contract bloat of that contract.
it was also deemed somewhat more organized to place all of the structures and actions pertaining to the staking within a central contract named for this purpose, this helps to clarify the location of the key structures and actions involved in staking going forward, and also provides a clean compartmentalization of the staking data and functionality.
it will add a day or two to the project, but the gains we get by way of comprehensibility, and maintainability will be significant, and so this is seen as an easy decision.
4/1 The team met to discuss the necessity for core upgrades that are presently required to deliver new contracts and system accounts within the Fio Protocol. It was proposed that we can use the actions table to make a list of distinct system accounts and use this, and so in the future we can avoid any mandatary upgrades being required whenever new contracts and system accounts are added to the Fio Protocol.
This underwent a quick feasibility prototype which proved the concept should work acceptably.
NOTE – testing must be performed before we go forward in delivering this approach.
full playback testing
test with 400 actions in the actions table
test with 400 actions in the actions table and also perform set code on system contract.
test with 400 actions in the actions table and also perform set code on system contract after bloating the system contract to increase its size.
test that a new contract can be added using operational msig and set contracts.
After submitting the PR for these changes, work will resume on the staking project. These changes may deliver with Bahamas and so should position the protocol well for staking, marketplace, and wrapping.
4/8/2021 implementation completed and functional testing completed on changes to permit adding contracts without core changes.
4/15/2021 release testing discovered an issue with playback, a fix was strategized and implemented. This Took a few days.
4/22/2021 dev net testing uncovered some issues with support for the dev net environment a fix was implemented, this took a few days.
4/25/2021 rollout to test net with Bahamas, and work re-focuses on the staking contract development.
4/28/2021 4 system calls implemented and dev tested.
4/292021 system calls refactored into in line logic in stakefio and unstakefio (stakefio is completed and dev tested, unstakefio is 75%, need to focus next on the lock modifications to support the rest of the unstakefio implementation).