BetaNet Update 3.8.0

BetaNet is planned to be updated to version 3.8.0 on Thu June 23, 2022, 10:30 AM EST (2:30 PM UTC).


The goal command is now using the participation key REST API. A byproduct of this is that keys they are no longer copied into the data directory, instead they are installed directly into the internal participation key registry.

What’s New

  • Participation Key Interface cleanup
  • Adding support for m1 builds to pipeline
  • Other miscellaneous bug fixes and enhancements


New Features

  • CICD: Add m1 to build pipeline (#4079)


  • AVM: Make it easier to move experimental opcode groups (#4123)
  • AVM: Track Scratch Slot Types (#4064)
  • CICD: update build pipeline for darwin-amd64 (#4147)
  • CICD: Optimizing CircleCI cache usage (#4087)
  • Devops: Define recipe for FastNet. (#4066)
  • Ledger: fix typo in error.go (#4143)
  • Metrics: specify telemetry hostname and instance name as prometheus labels (#4089)
  • Misc: Add helper functions to genesis. (#4111)
  • Pingpong: improve transaction scheduling (#3478)
  • PKI: Enable full usage of REST API to install participation keys (#4002)


  • AVM: Version downgrade check ported to master (#4093) (in v3.7.2)
  • Bug Fix: Adds validity round check for failing tests (#4085)
  • Catchpointdump: fixes (#4130)
  • Ledger: fix flakiness in TestReproducibleCatchpointLabels (#4074)
  • Network: message-of-interest tiny bugfix (#4107) (in v3.7.2)
  • Tools: Fixing calls to pingpong with deprecated flag --REST (#4070)


Protocol Upgrade

This release does not contain a protocol upgrade.

vFuture changes are not yet available in MainNet or TestNet but can be used in private networks.

New Features

  • AVM: replace opcodes (#4129)


  • AVM: Set proper costs for json_ref (#4096)

Additional Resources

To update to the current version of BetaNet, you can run the following goal command:

./ -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: