Go-Algorand v3.22.0 deployed to MainNet and TestNet, changing how NetAddress determines archival status
The Algorand DevOps team deployed go-algorand v3.22.0 to MainNet and TestNet on February 5, 2024. The release focuses on networking optimizations and introduces a change to how the NetAddress field interacts with node configuration.
NetAddress no longer automatically marks a node as archival. Operators who rely on NetAddress for archival status must manually set Archival to true in their node configuration to prevent the node from deleting old blocks during the upgrade. The Foundation published this as an upcoming release note on January 31, ahead of the February 5 deployment.
Sources that covered it
More stories
Algorand updates MainNet and TestNet to Go-Algorand 3.21.0 with dynamic round times and new AVM opcodes
The network has updated to version 3.21.0, introducing dynamic round times to shorten average round durations and new opcodes for the Algorand Virtual Machine. This release includes a consensus protocol upgrade that also requires updates to the indexer and conduit.
Algorand Indexer v3.4.0 and Conduit v1.6.0 released for go-algorand 3.21 upgrade
The Algorand Indexer has been updated to version 3.4.0 and Conduit to version 1.6.0 to support the upcoming go-algorand 3.21 consensus upgrade. These updates are required for runners to maintain network connectivity once the upgrade is implemented.
Algorand updates MainNet and TestNet to Go-Algorand 3.20.1
The Algorand protocol has updated its MainNet and TestNet to version 3.20.1, which introduces a new endpoint for generating participation keys and various network optimizations. This update includes improvements to catchup behavior, the addition of an applications rate limiter, and a change to how crash and state proof databases are stored.