Releases: multiversx/mx-chain-go
Releases · multiversx/mx-chain-go
BoNwards wave 41
- Implemented miniblock whitelist mechanism
- Removed useless tx cache cleaner
- Fixed start of epoch edge cases
- Fixed antiflood bug that prevented dissemination of messages beyond 10000 packages
Note: This release should start with a new DB
BoNwards wave 40
- Fixed genesis metachain split due to not-deterministic parsing of the genesis file
- Fixed trie node removal that occurred during concurrent prune operation with commit operation
- Fixed epoch start block finalization after multiple rollbacks on the attesting metaheader
- Fixed the creation of bootstrap interceptors due to the lack of a valid data pool
Note: This release should start with a new DB
BoNwards wave 39
- Added bech32 support, the transactions are signed on the addresses fields containing bech32-format strings
- Added logs for SC execution
- Changed the ratings computing algorithm to take into account the network parameters
- Bugfixes in epoch start requests, miniblocks requests/resolve/intercept, block tracker areas
- General code cleanup, golang ci linter fixes
Note: This release should start with a new DB
BoNwards wave 38
- Added key-value storage inside the account (directly on the state trie)
- Added a supplemental condition to keep the shards in synced with the metachain
- Added usernames aliases for accounts
- Added shuffled out handler
- Added more guards on consensus received data
- Bugfix in elastic search indexer
- Bugfix on trie snapshot done with an empty trie
Note: This release should start with a new DB
BoNwards wave 37
- Added start in epoch components
- Arwen now runs in a separate process, monitored by the arwen driver inside the node
- Removed the second broadcast of the block body after the consensus has been achieved
- Changed the data field type in the transaction data structure
- Removed an exploit that could affect peer id - public key mapping on all peers
- Fixed termui metrics
- Removed a bug by implementing a white list mechanism. The bug appeared whenever a debit transaction was added in the same block with a credit transaction affecting the same address and the credit transaction could not have been executed without first executing the debit transaction.
BoNwards wave 36
- Added cleaning component for cross txs
- Removed the unused block tracker's cleaning mechanism
- Update validators pub key when epoch change and add rating information
- Bugfixed the rating computation so the shards will correctly follow up the metachain
test only
test only
BoNwards wave 35
- Rating v2 implemented:
- allow metachain rating steps to be different than the ones on shards
- added 2.5% minimumSignedBlocksThreshold
- add consecutiveBlocksPenalty for increased proposer penalty if consecutive proposed blocks are missed
- Weighted random sampling for consensus group selection
- Added cleaning mechanism for old/unused miniblocks
- Added a new route for epoch information
- Moved logger subsystem in a separate repo so that it can be easily reused
- Bugfixed a network stuck issue that happened when the network booted in an epoch > 0
- Bugfixed the trigger for shards on missed peer miniblocks
- Bugfixed the network sharding component that was not correctly wired to the epoch change handler
- Bugixed validators config between epochs
- Bugfixed dead lock in process block
- Termui fixes
test only
test only
BoNwards wave 34
- Bugfix on sending transactions without data field to system SCs
- Complete refactor of the accounts DB. This should lead to a performance increase because of the complete rethinking of the journalizing system
- Improvements in logger subsystem, log lines offers now more info