Release: mx-chain-mainnet-config - v1.3.50.1

AccountsStatePruningEnabled = false

Please note that all nodes will observe a slight increase in their disk state with this release, with an additional ~100MB/shard to ~500MB/shard each epoch. While this may be slightly higher than expected, it is still within the specified specifications and should not cause any issues. The normal epoch-pruning process will eventually delete this extra state for the normal validators. The nodes that will run as observers with the official configuration settings will still remove the enlarged state trie DB during the epoch-pruning event. However, the observers running with the altered AccountsTrieCleanOldEpochsData or AccountsTrieSkipRemovalCustomPattern flags will make their DB size increase with the aforementioned values each epoch.

We have made every effort to ensure that this release is fully backward compatible with v1.3.50.0, so you should experience no issues when upgrading. There are no activation flags or binary updates required for this release.

We highly recommend that all users upgrade to this release, as it brings significant performance improvements and a more stable experience. If you have any questions or encounter any issues when upgrading, please don’t hesitate to reach out through our Github Discussions tab and share your thoughts so that the entire MultiversX community can hear you.

Configuration Release Notes: v1.3.50.1.

Full Changelog: v1.3.50.0…v1.3.50.1.

We hope that this new release helps to make your experience even better in the new year. Thank you for your continued support and we wish you all the best for a successful and productive year ahead.