So far, 6 epics of Lisk SDK 5.0.0 were closed. 5 of them were closed in June 2020. With that 8 epics remain to be implemented. 1. Updated address and ID system The entire address and ID system was updated. Account initializations will not be required and collisions will be nearly impossible. More details about the 8 issues of this epic can be found on GitHub. 2. PostgreSQL replaced by embedded database PostgreSQL was replaced by an embedded database in order to reduce the complexity for the Lisk SDK user, to optimize database storage size, and to improve the processing speed. The current most promising candidates are RocksDB and LevelDB. More details about the 12 issues of this epic can be found on GitHub. 3. Added delegate banning mechanism A banning mechanism was added in order to prevent unproductive delegates from forging. The motivation for including the fail safe mechanism can be found in the Delegate Productivity section of the LIP0023. This also completes the Lisk DPoS 2.0 consensus algorithm. More details about the 3 issues of this epic can be found on GitHub. 4. Implemented lisk-codec Lisk-codec, a generic serialization library to encode and decode data for communication and storage, was implemented. More details about the 42 issues of this epic can be found on GitHub. 5. Removed undo steps for transaction types Previously, when a new transaction type was implemented it always also needed to contain the logic to undo its actions, in case of a blockchain rollback. Due to our deterministic lisk-codec library and the switch to an embedded database, amongst others, this can now happen automatically. Now for any state change the difference is being calculated and stored, so that in case of a blockchain rollback it can be retrieved to come back to the previous state. More details about the 9 issues of this epic can be found on GitHub. |