Arweave 2.9.7-alpha1 Targets Format 1 and Node Upgrades
Arweave has released version 2.9.7-alpha1, an alpha node update proposing soft fork 2.9.6 at block height 2,000,000, expected around 13 September 2026 at 12:00 UTC. The Arweave 2.9.7-alpha1 release ends the grace period for accepting legacy format: 1 transactions, which account for about 0.007% of Arweave base-layer interactions. Node operators are encouraged to upgrade before activation because blocks containing format: 1 transactions may be rejected by peers after the change.
The update completely rewrites Arweave node configuration. It adds hierarchical JSON and YAML files, new command-line and environment-variable options, dynamic configuration get/set commands, and a migration tool for legacy configurations. Storage modules can now use explicit byte ranges, while legacy bucket settings remain supported.
Arweave 2.9.7-alpha1 also introduces adaptive peer throttling, improved rate-limit headers, faster account-tree initialization and block processing, a cached metrics endpoint, stronger input validation, repack-in-place fixes, and sync-performance improvements. The release is marked alpha and may not be suitable for production use.
Neutral
The expected market impact is neutral. Arweave 2.9.7-alpha1 is mainly a technical and operational upgrade rather than a change to token economics, supply, staking, or network fees. Ending support for format: 1 transactions affects a very small share of activity—about 0.007%—so the direct impact on AR demand is likely limited.
In the short term, traders may monitor AR for volatility around the proposed activation height, particularly if node operators delay upgrades or report compatibility problems. Alpha software can also create temporary uncertainty because it is not yet recommended for production use. However, the release does not itself indicate a planned chain split, and legacy configuration support reduces migration risk.
Over the longer term, faster account-tree processing, improved synchronization, adaptive throttling, storage configuration flexibility, and stronger validation could improve node reliability and scalability. Similar infrastructure upgrades in blockchain networks typically have a more meaningful effect on developer confidence and operational efficiency than on immediate spot prices. A bullish reaction would require evidence of higher network usage, stronger demand for AR, or successful activation without disruption. Conversely, widespread upgrade failures or rejected blocks could create short-term bearish pressure. At present, the limited transaction exposure and absence of a direct economic change support a neutral classification.