Randomness beacon down for 23 minutes due to configuration change
The Algorand Foundation's randomness beacon was unavailable for 23 minutes on 13 February 2025. A configuration change caused a backend service error that temporarily halted the submission of Verifiable Random Function proofs. The service was restarted and proofs caught up within 11 minutes of the restoration.
The Foundation said it plans to implement code-level guards during the bootstrap process to prevent the same edge case from recurring.
Sources that covered it
More stories
Algorand Foundation opens the 2025 Relay Program for peer-to-peer gossip protocol transition
The Algorand Foundation is seeking participants for the 2025 Relay Program, which will provide non-archival relays and archival non-relay nodes to support the transition to a peer-to-peer gossip protocol. The program runs from April 1, 2025, to March 31, 2026, and prioritizes cost efficiency, geographical distribution, and the use of independent hosting providers.
Go-Algorand 4.0.1 ships native consensus participation incentives and MiMC opcodes to MainNet and TestNet
The Algorand protocol has been updated to version 4.0.1, introducing native consensus participation incentives and automatic heartbeat functionality for eligible nodes. The release also adds MiMC opcodes to support zero-knowledge proof applications and includes a network fix for peer handling.
Algorand deploys version 4.0 on January 15, 2025
Algorand is scheduled to deploy version 4.0 of its protocol on Wednesday, January 15, 2025. The upgrade process is expected to take approximately one week, with staking rewards becoming active after the consensus upgrade completes and 90% of the stake has voted.