BetaNet Update: Version 2.1.1

BetaNet
1

We are planning to upgrade BetaNet to version 2.1.1 on Friday, Aug 7th 2020 11:30AM EDT.

If you have your node set to automatic updates, you don’t need to do anything. It will automatically update to the newer version whenever that becomes available.

If this is not the case, you can update the binary, but aren’t required to do so.

Summary of Contained Changes in Upgrade:

Highlights

  • Fix for memory leak in merkle trie prioritization cache

Changes

  1. General
    • Bug Fix - merketrie prioritization cache
  2. Agreement
    • Bug Fix - prevent warning message for block assembly when catching up
  3. REST API
    • Enhancement - add messagepack to produces list for endpoints which can produce messagepack
  4. Tools
    • New Feature - create a utility to generate the consensus.json file
  5. Tests
    • Enhancements
      • add new rekeying tests
      • add unit test TestConsensusUpgradeWindow
      • enable creatables in ledger tests
      • add a fuzzer to the merkletrie cache testing
      • add assets and apps to ledger txn validate tests
      • e2e test for rekeying before and after upgrade
      • unit test for accountsNewRound creatables parameter
  6. Other
    • Bug Fix - fix package script go version failure

Protocol Upgrade

This release does not contain a consensus protocol upgrade.

Additional Resources

To update your current version of BetaNet to 2.1.1, run the following goal command:

./update.sh -c beta -i -d <betanet-data-directory> -n

If you haven’t already done so, we also advise setting up a CRON job to automatically update your algorand networks. If you haven’t done this for BetaNet, you can follow the instructions here:

https://developer.algorand.org/docs/run-a-node/setup/install/#updating-node

2

Does this patch require BetaNet 2.1.0 to be applied first?

3

This patch includes all the changes from BetaNet 2.1.0. You do not need to apply 2.1.0 first, but the changes from 2.1.0 will then apply as well.

1 Like