v1.5.12.0 - Altair patch 1

Release v1.5.12.0 is out 🚀

This release updates the new libp2p libraries to the newest versions. Starting from this version, the node should be compiled with a go compiler no older than v1.20.5, or the code might not compile due to the constraints found in the libp2p libraries used.
The node can now connect on the p2p level with another 3 transports besides the already used TCP: QUIC, WebSocket, and WebTransport.

There is 1 flag that will be enabled on epoch 1126 which is scheduled to happen on August 30th, 2023 ~15:45 UTC

• DeterministicSortOnValidatorsInfoEnableEpoch - will activate a deterministic sort on the assembled validators info in the miniblocks. This will prevent the validators from having different versions of miniblocks that contain the exact same information in the improbable situation when we might have 2 validator info structures for the same BLS public key.

The full binary release notes are published here: https://github.com/multiversx/mx-chain-go/releases/tag/v1.5.12

v1.5.11.0

What's Changed

Release v1.5.11.0 is out 🚀

Full Changelog: v1.5.8.0...v1.5.11.0

v1.5.8.0 - Altair

Release v1.5.8.0 is out 🚀

There is 1 flag that will be enabled on epoch 1075 which is scheduled to happen on July 10th, 2023 ~15:45 UTC.

• SetGuardianEnableEpoch - will activate the Guardians feature that allows any user account to be guarded by another account. The operations from the guarded account will be permitted only through transactions that are both signed by the account's private key and the guardian's private key. This feature will add extra security for user accounts if the account's private key was leaked.

The full binary release notes are published here: https://github.com/multiversx/mx-chain-go/releases/tag/v1.5.8

v1.4.18.0 - Polaris patch 5

Release v1.4.18.0 is out 🚀

There are no flags for this version. However, the binary referenced here addresses a small issue found when indexing data in the Elasticsearch database.

The full binary release notes are published here: https://github.com/multiversx/mx-chain-go/releases/tag/v1.4.18

v1.4.17.0 - Polaris patch 4

Release v1.4.17.0 is out 🚀

There is one new flag for this version. It is called RelayedNonceFixEnableEpoch and will be active on epoch 1043 which normally should happen on June 8th, 2023, ~15:47 UTC. The flag is required to activate a fix for some failed relayed transactions that need to be treated differently.

The full binary release notes are published here: https://github.com/multiversx/mx-chain-go/releases/tag/v1.4.17

v1.4.16.0 - Polaris patch 3

Release v1.4.16.0 is out 🚀

There are no flags for this version. However, the new binary referenced here 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.

The full binary release notes are published here: https://github.com/multiversx/mx-chain-go/releases/tag/v1.4.16

v1.4.15.0 - Polaris patch 2

Release v1.4.15.0 is out 🚀

There are no flags for this version. However, the new binary referenced here fixes an edge-case situation that ended up making the node lose some trie nodes when they were stored in the DB. The bug happened only on a small batch of nodes (~10 units approximatively) and those nodes stopped syncing the chain. The nodes recovered after they did a proper sync from the network.
It is very important to state that this bug did not affect the processing of the transaction or the outcome of that processing as it only affected the trie node storage after the consensus was reached on the outcome.

A detailed description of the bug:

• 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 disk after the block was processed;
• affected nodes stopped syncing the chain as they were missing some trie data nodes.

The full binary release notes are published here: https://github.com/multiversx/mx-chain-go/releases/tag/v1.4.15

v1.4.14.0 - Polaris patch 1

Release v1.4.14.0 is out 🚀

There is only one flag that will be enabled on epoch 970 which is scheduled to happen on Monday 27th, 2023 ~15:35 UTC.

• RuntimeCodeSizeFixEnableEpoch fixes a wrong smart contract code size computation bug that, in certain conditions, could have prevented the correct operation of the nodes that just joined in the network at a certain epoch.
• 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 erd1alice... 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.

The full binary release notes are published here: https://github.com/multiversx/mx-chain-go/releases/tag/v1.4.14

v1.4.8.1 - Polaris

Release v1.4.8.1 is out 🚀

There are 8 flags that will be enabled on epoch 938 which is scheduled to happen on February 23rd, 2023 ~15:30 UTC.

• RuntimeMemStoreLimitEnableEpoch - a maximum hardcap limit for the mem store instruction (invariant);
• SetSenderInEeiOutputTransferEnableEpoch - a flag that will make the EEI subsystem return & store the sender's address for easier traceability & easier debugging experience;
• RefactorPeersMiniBlocksEnableEpoch - the epoch that the refactoring of the peer's miniblocks is activated: the miniblocks won't contain the marshalled form of the peer change info but a hash of that change. This is now done in the exact manner as the transactions are referenced, transferred & processed. The peer change info remained unchanged and it's processing results will be identical with the initial implementation. So, this change affects only the transmission and the reference of each peer change info;
• MaxBlockchainHookCountersEnableEpoch - will limit the number of blockchain-API calls a SmartContract can perform;
• WipeSingleNFTLiquidityDecreaseEnableEpoch - the SystemAccounts will automatically decrease the value (and do an automatically clean) whenever an NFT is wiped. Without this fix, the SystemAccount would accumulate garbage after the processing of an NFT-wipe operation;
• AlwaysSaveTokenMetaDataEnableEpoch - will trigger the automatic update of an old-type NFT info in order to preserve the consistency of the held information accross shards;
• BLSMultiSignerEnableEpoch.KOSK - will improve the performance of the aggregated signature verification by 2-3x. The security of the BLS signatures is not affected by this change.
• gasScheduleV7.toml - this is a new gas schedule change that will address a bug when computing the developer rewards when executing a multi-esdt-nft-transfer. The cost won't change but the developer fees will be transferred correctly as in any other esdt operation or SC call.

The full binary release notes are published here: https://github.com/ElrondNetwork/elrond-go/releases/tag/v1.4.8

v1.3.50.4

What's Changed

• Update image name and readme by @miiu96 in #158

Full Changelog: v1.3.50.3...v1.3.50.4