BoNwards wave 23

• Bugfixed the error "mismatch in reward transactions" that appeared when the leader gathered fees equal to the reward value
• Bugfixed the multiple sending of the same reward transactions
• Added debugging prints

Note: This release should start with a new DB

BoNwards wave 22 - patch 1

• Improved the BLS consensus even further: added a special message that will trigger block commit instead of waiting the full singed block header to be propagated. Added the possibility to broadcast 2 in 1 the block header along with the block body
• Improved Arwen VM engine
• Removed unnecessary transactions requests

BoNwards wave 22

• Added a cache for computed consensus group based on the shard ID, randomness and round. This will greatly reduce the computational power needed after skipping thousands of rounds.

Note: This release should start with a new DB

BoNwards wave 21

• Temporary revert the libp2p libs to an older version
• General code clean-up, running go vet and gosec will raise no issues
• Headers protection on interceptors when receiving older than final header blocks or ahead of time blocks
• Improved project's code coverage
• Added milliseconds when displaying timestamp on logger line
• Finished improving the new consensus mechanism, added new metrics for consensus

Note: This release should start with a new DB

BoNwards wave 18

Note: This release should start with a new DB

BoNwards wave 17

• Major optimization in consensus state machine: all peers process speculatively the proposed block, waiting for the signed header to be intercepted. When it is received, it will cause an immediately commitment of the state trie. This will cause the proposed block being processed in the same round was produced, yielding performance boost since all shard nodes will start the new round synced.
• Added a time.sleep each time a new pubsub publish is done. This is a temporary fix until the new pubsub publish feedback is ready to be used.

Note: This release should start with a new DB

BoNwards wave 16

• Fixed a p2p related bug that appeared when publishing new messages on a p2p topic
• Optimized code related to data pools (now we have only one implementation of data pools independent of the node's shard ID)
• Account's trie now splits the nodes in an inverse manner (as to align with next elrond's features)
• Requests are now done by also specifying the epoch number
• Fixed tests that sometimes failed

Note: This release should start with a new DB

BoNwards wave 15

Note: This release should start with a new DB

BoNwards wave 14

• Fixed a bug related to 2 mutex usages

Note: This release should start with a new DB

BoNwards wave 13

• Block tracker print fixes and requests
• Permanent fix for invalid transactions processed but not received through interceptors
• Fixed kad-dht parameters to allow faster network recovery and faster peer bootstrapping process