Skip to content

Releases: multiversx/mx-chain-go

v1.5.15

14 Nov 17:06
1ef37e1
Compare
Choose a tag to compare

What's Changed

Bugfixes

  • Fixed return value in the MaxGasPriceSetGuardian method on the disabled fee handler by @iulianpascalau in #5703

Full Changelog: v1.5.14...v1.5.15

v1.5.14

31 Oct 11:17
0101225
Compare
Choose a tag to compare

What's Changed

Other Notable Changes

Full Changelog: v1.5.13...v1.5.14

v1.5.13

11 Aug 14:17
c4d6354
Compare
Choose a tag to compare

What's Changed

Improvements

Full Changelog: v1.5.12...v1.5.13

v1.5.12

20 Jul 08:33
f73e0b1
Compare
Choose a tag to compare

What's Changed

Improvements

We care about documentation

Other Notable Changes

Full Changelog: v1.5.8...v1.5.12

v1.5.8

15 Jun 08:14
f51099a
Compare
Choose a tag to compare

What's Changed

Bugfixes

New Features

Improvements

Other Notable Changes

Full Changelog: v1.4.18...v1.5.8

v1.4.18

02 Jun 12:17
a29cf3b
Compare
Choose a tag to compare

What's Changed

This release addresses one issue found when indexing the data in the Elasticsearch database. It is 100% backward compatible with the last release.

Full Changelog: v1.4.17...v1.4.18

v1.4.17

28 May 16:04
babdb14
Compare
Choose a tag to compare

What's Changed

This release addresses some edge cases when transactions executed in relayed mode could have produced results that were not consistent with other transactions' results. Since the binary is not backward compatible by default, we've added a new flag called RelayedNonceFixEnableEpoch.

Full Changelog: v1.4.16...v1.4.17

v1.4.16

19 Apr 16:32
9729547
Compare
Choose a tag to compare

What's Changed

The new binary version will return a user error message whenever a wrong username is invoked on a transaction. The behavior of the returning sent funds (because the transaction failed) was unaltered in this release.

Other Notable Changes

  • return a user error for the wrong username

Full Changelog: v1.4.15...v1.4.16

v1.4.15

27 Mar 14:09
cfaaaca
Compare
Choose a tag to compare

What's Changed

Bugfixes

  • added concurrency protection in the trie sub-component by @iulianpascalau in #5123
    This PR fixes a bug that happened on a handful of nodes that caused the trie nodes not to be saved in the DB after the block has been processed. Due to our last refactoring work in the Patricia-Merkle Trie implementation, we've wrongly removed mutex protection for a critical area. That area was used in the normal block processing and in the interceptors implementations (the components responsible for the pre-validation of the incoming data). Since there was more than 1 thread acting on the same area, due to some WAW hazards, the affected nodes ended up journalizing the wrong data to be written on the disk after the block was processed. Affected nodes stopped syncing the chain as they were missing some trie data nodes.

Other Notable Changes

Full Changelog: v1.4.14...v1.4.15

v1.4.14

13 Mar 16:24
7d39371
Compare
Choose a tag to compare

What's Changed

Breaking Changes

Node API Breaking changes

  • endpoints under the address group received an update that makes them always return empty or 0 values instead of errors when the requested account does not exist inside the trie.
    -> the list of the address group endpoints can be found on the Swagger Docs: https://gateway.multiversx.com/#/address
    -> example: (if the address erdalice... doesn't exist), then <node>/address/erd1alice.../key/0a0a0a would have returned an 'account not found' before, while now it will return an empty result

Bugfixes

Other Notable Changes

Full Changelog: v1.4.8...v1.4.14