Algorand activates native post-quantum accounts on mainnet, earning 32 mentions in Google's cryptography report
Covered by 2 sources
Algorand has activated native post-quantum accounts on mainnet as part of a protocol upgrade. Both Google and Coinbase highlighted the work in their respective coverage, with Algorand receiving 32 mentions in Google's report on post-quantum cryptography.
Custodial wallets on major centralized exchanges such as Coinbase and Binance operate through their own key-management processes. Whether those wallets have completed rekeying to the new post-quantum signature scheme is not stated in the official announcement.
Sources that covered it
More stories
AC2 introduced as a protocol feature for verifiable AI agent signing on Algorand
AC2 (Agentic Communication and Control Protocol) has been introduced as a protocol feature for Algorand. It provides verifiable proof of intent and credential isolation for AI-driven signing operations, returning control of those operations to the user. The protocol was demonstrated by Algorand software engineer Blair Mcilroy.
Covered by 4 sources
Falcon-1024 live on Algorand MainNet since v5.0.0, post-quantum VRF candidate under analysis with paper due early 2027
The Algorand Foundation published a technical thread covering the status of its post-quantum work. Native PQ accounts are already live on MainNet. The current VRF, which handles committee selection in Pure Proof-of-Stake consensus, relies on elliptic-curve cryptography and is the next target. A post-quantum VRF candidate construction is under security and efficiency analysis, with a research paper expected in early 2027. After that, consensus signatures remain as the final piece of the post-quantum roadmap.
Covered by 3 sources
FUNC v5 adds automatic Valar Daemon support for Algorand node runners
FUNC v5 now automatically runs Valar Daemon, allowing more node runners using the FUNC tool to advertise their nodes to stakers via Valar. Valar UI v0.4.2 was also deployed with updated node runner documentation and a fix for an xGov integration edge case involving representation status.
Covered by 3 sources