Page Comparison

...

• 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)

          • https://fioprotocol.atlassian.net/browse/BD-2448

        • implement and test actions to update global state for staking. In progress (20% 50% completed)

          • implement stakefio (completed)

          • implement unstakefio (75% completed)

          • implement modified locking mechanism to support unstakefio (in workcompleted)

          • impelement and test incgrewards

          • implement and test clrgdailyrew

          • implement 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

        • Allow trnsloctoks to lock tokens to an existing account.

        • Allow trnsloctoks to lock tokens to an existing account with general locks in place.

      • 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).

...