🧵 2.7M+ post-quantum transactions are only part of @Algorand’s story. Native PQ accounts. Wallet upgrades without moving assets. AI-agent payments. User-controlled authorization. Here’s what is live—and what comes next. 👇 @Algorand reports 2.7M+ PQ transactions on mainnet, ahead of QRL’s 2.5M in its published comparison. First by that reported transaction count. Behind the milestone is a progression from State Proofs to native account signing. 2022: Falcon-secured State Proofs brought PQ cryptography to blockchain-state attestations. 2025: Falcon verification in the AVM enabled PQ transactions through LogicSig accounts. August 2026: Native Falcon-1024 accounts and related tooling went live. Native PQ accounts can hold ALGO and other assets, send transactions and interact with applications. Existing accounts can adopt PQ signing through rekeying: → Same public address → Same assets → Same transaction history The signing authority changes. That migration path matters. Users can upgrade authorization while retaining the address connected to their apps, contacts and payment workflows. Algorand 5.0 also introduces a flexible signature framework designed to accommodate additional cryptographic schemes. Developers received more room to build. Algorand 5.0 doubles maximum application code size from 8 KB to 16 KB. Updatable applications can expand code capacity and global state, helping existing products grow without starting over. Now add agentic commerce. Algorand supports x402 payments for APIs, data and services. @GoPlausible provides SDKs, examples, a facilitator and integration tooling—including an AP2–x402 extension for A2A. Payment authorization meets execution. AC2 adds user-controlled authorization. The @AlgoFoundation‘s Agentic Communication and Control Protocol lets agents request signatures while private keys remain under user control. Request → Approve → Execute. AC2’s documented use cases extend beyond payments: → Code deployments → API access → Client communications → x402 payments The open specification, reference wallet and plugin are available. The protocol is blockchain-agnostic. These layers address different security needs: AC2 → authorization and key separation. PQ signatures → resistance to quantum attacks. Together, they illustrate why agent infrastructure needs both controlled permissions and strong signing mechanisms. Practical payment pilots add another dimension. The Foundation reported a German Federal Foreign Office and @PoliSync pilot using @HesabPay_ on Algorand for aid payments to Syria. Reported results: up to 73% lower fees and settlement in under two hours. Next on the published PQ roadmap: → Native Falcon-512 → PQ multisig → Hybrid signing approaches Falcon-512 and PQ multisig are targeted for the end of 2026, expanding options for accounts, institutional operations and treasury approvals. Hardware is being explored, too. Algorand demonstrated Falcon-1024 key generation and signing on a Trezor Safe 5 proof of concept. Reported signing time: approximately 0.7 seconds. Bringing this into supported products requires manufacturer collaboration. The remaining work reaches into consensus. Research covers a PQ-resistant VRF for committee selection and PQ signatures for consensus messages. A hybrid Ed25519 + Falcon approach is under consideration. Broad quantum resilience remains the target for end-2027. AC2’s next planned step is bounded delegation. Its launch design requests approval for each signature. The planned evolution lets users define limits once, with agents acting inside those bounds and returning for approval beyond them. That’s the bigger picture: PQ technology already deployed. Existing accounts able to migrate. More capable applications. Agent-payment tooling. User-controlled authorization. Further consensus and hardware work ahead. @Algorand is building across the layers that make these systems usable.