Algorand released 3.9 code for State Proofs and higher capacity

Algorand announced the 3.9 protocol software release on September 7, 2022, placing State Proofs, higher theoretical transaction capacity and new smart-contract functions into a network-upgrade process. The dated technical record supports the release of version 3.9.2 and its code. It does not support treating every feature as already active across MainNet at the moment of the announcement.

That distinction is important because Algorand’s own event-day materials were not perfectly aligned. A company-distributed release described the upgrade as live on MainNet. A technical post published under Algorand’s official publication on September 7 said the features would become available only after the network completed its upgrade, expected during the week beginning September 12, 2022. The September 6 node release notice likewise told operators that version 3.9.2 required a consensus protocol upgrade.

What version 3.9 proposed

The release packaged three main changes. State Proofs were designed as compact, portable cryptographic attestations of Algorand state. The intended use was to let software outside Algorand verify information about the chain without relying entirely on a conventional bridge operator or a separate validator committee. Algorand also described the proofs as post-quantum secure; that was a protocol-design claim, not evidence on September 7 that a production cross-chain application had eliminated bridge risk.

The performance configuration raised the stated maximum block size from 1 MB to 5 MiB, with the release notes estimating roughly 25,000 transactions per block and a maximum throughput of 6,000 transactions per second. It also targeted average round times near 3.9 seconds. These figures were engineering capacity targets supplied by Algorand, not a measurement of sustained MainNet demand or an independent benchmark. Actual throughput depends on transaction composition, node behavior and network conditions.

Algorand Virtual Machine version 7 added tools for applications, including block and verification opcodes intended to support randomness beacons or oracles. It also allowed an account without a funded balance to issue a transaction when another transaction in the same group covered the fee. Those were developer-facing capabilities; release notes alone could not establish adoption.

Why the release mattered

In September 2022, smart-contract networks were competing on more than token prices. Developers and users were testing whether layer-one chains could offer capacity, predictable finality and safer communication across otherwise separate ecosystems. Algorand’s release addressed all three themes in one package.

State Proofs were the most strategically important part. Cross-chain systems commonly introduced an additional trust layer between two blockchains. A proof that another chain or light client could verify offered a route to reduce that dependency. The careful interpretation is “reduce trust in an intermediary,” not “make bridges safe.” Relayers, verifier implementations, destination-chain code, key management and application logic could still fail.

The capacity changes also mattered even if the network was not using the advertised ceiling. Raising a limit before demand reaches it can give applications room to grow, but a theoretical maximum does not show that users need the capacity, that all nodes can sustain it under stress, or that latency will remain stable at the limit.

The event-day record

The verifiable September 7 development was therefore a software release and upgrade announcement, with node operators directed to version 3.9.2 and network activation still dependent on completion of the protocol-upgrade process. Coinburn does not resolve the conflict in Algorand’s event-day wording by backdating a later activation.

As of September 7, the open questions were operational: when the network would complete the upgrade, whether the new parameters would perform as specified under live load, and which applications would use State Proofs or AVM 7. Those questions required later on-chain and implementation evidence; they were not answered by the release itself.