Objective:
- Improve the robustness of the chain: avoid the chain blocked by the unavailability of nodes, network disconnected, inadequate node power.
- Adapts well with the variety of the number of validators
- Strengthen the security: trustless to shard committee
Estimate End Date: June 2021
July 2020
- Beacon sync, insert and store all shard blocks
- Beacon node must sync and insert shard from beginning
- Refactor Committee State in Blockchain package for later implementation
- Technical Specification for New Staking Flow
August 2020
-
Implement new staking flow
- Staking to become candidate
- Candidate Life cycle (not included monitoring and report)
- Unstake flow
- Refine Stop auto re-staking flow
-
Implement new swap rule
- Not included increasing/decrease (case 3,4) shard
-
Technical Specification of Slashing Misbehaved Validator
September 2020
- Integrate new Staking flow and swapping rule with with Smart Contract
- Implement Slashing Misbehaved Validator
October 2020
- New Staking flow and swapping rule are ready for local test (TestNet in happy case)
- Implement, Integrate and testing Slashing Misbehaved Validator with Smart Contract and other Feature
November 2020
- Ship New Staking flow and swapping rule at the end of Nov or early Dec
- Ship Slashing Misbehaved Validator at the end of Nov or early Dec
March 2021
- Reduce committee size dynamically
June 2021
- Dynamic grow/shrink number of Shards
Key results:
- Committee size is dynamically changed with the number of validators
- Dynamic sharding
- Beacon is able to verify the correctness of every single shard. As a result, a shard could verify cross-shard transactions through the beacon chain.
Note:
- Linked to Github
- Linked to Gantt Chart Timeline
- Ref Dynamic Committee Size design