Releases: multiversx/mx-chain-go
Releases · multiversx/mx-chain-go
BoN phase ShadowShards wave 1 - patch 1
No changes on this release.
Note: This release should start with a new DB
BoN phase ShadowShards wave 1
- Metrics are now persisted as to eliminates issues regarding counters reset in termui between node restarts
- Fixed trie journalizing problem that appeared when running a large number of SC calls that altered the data trie(s). This issue became obvious after the introduction of genesis nodes inside system SC at node startup.
- Fixed a transaction fee computation problem that could cause transaction clutter and no new proposed blocks inside a shard
Note: This release should start with a new DB
BoN phase ShadowShards wave 1 - dry run
- Permanent fix for "unStake" problem that caused metachain to fail
- Permanent fix for probable highest nonce taken from consensus topic
- Fixed validator root hash mismatch error
- Fixed problem with method computeGenesisTimeFromHeader from base forkDetector
Note: This release should start with a new DB
BoN phase 2 wave 3 - patch 15
- Binary 100% compatible with 1.0.58
Note: This release should start with a new DB
BoN phase 2 wave 3 - patch 14
- Proposed blocks are no longer considered by the fork detector in probable highest nonce computation.
Note: This release should start with a new DB
BoN phase 2 wave 3 - patch 13
Binary 100% compatible with 1.0.55^
Note: This release should start with a new DB
BoN phase 2 wave 3 - patch 12
Binary 100% compatible with v1.0.55
No need to delete the DB
BoN phase 2 wave 3 - patch 11
Bugfixes and stabilization:
- Fixed an issue that happened when a rollback on block 1 occurred
- Added protection for blocks received from other chain (first variant)
- Crypto hook fixes
Note: This release should start with a new DB
BoN phase 2 wave 3 - patch 10
Fresh new testnet
Note: This release should start with a new DB
BoN phase 2 wave 3 - patch 9
Dirty patch to test if unstuck shard 1 is possible
No need to remove existing DB.