Table of Contents

...

chain

...

framework.

...

chain

1. fork height, the block writer loads the old block height to generate a dag genesis fork block. (done)

2. introduce block height as consensus info. (done)

3. introduce the final height/point. (todo done 11.10)

4. refactor the consensus connect. (doing ???done 11.7)

5. refactor the block header for compatibility (done)

...

1. new framework version and upgrade plan. (doing. 11.20)

   1. epoch consensus strategy.Add dag info and remove uncle info.

   2. v2 version of block/block metadata.

   3. block reward logic review. such as remove uncle.

...

1. compact sync old block before fork height. (done)

2. after fork height, sync dag block. (done)

3. Go across the line between the old chain and Flexidag chain when the height of the block reaches the predefined one.(done)

storage

1. Check and initialize the BlockDAG object if the height of the block reaches the predefined one.(done)

flexidag service

1. Define and create Flexidag service instance.(done)

2. Replace the code that uses the Dag object with the one that uses Flexidag service message calls.(doing 11.10)