The Aptos testnet has processed more than 10 billion transactions, highlighting the rapid growth of activity on the blockchain’s testing infrastructure and raising questions about the long-term storage requirements associated with maintaining an increasingly large transaction history.
Aptos co-founder Avery Ching drew attention to the milestone while discussing the growth of testnet storage and a draft proposal known as AIP-147. The proposal is designed to establish a more predictable process for managing the testnet’s expanding data footprint without making changes to the Aptos mainnet.
AIP-147 proposes resetting the Aptos testnet no more than once every six months, with users and developers receiving one month of advance notice before a reset takes place.
The proposed approach is focused specifically on the test environment, where transaction activity can accumulate rapidly as developers test applications, smart contracts, and network functionality. Unlike the mainnet, the testnet is primarily intended for development and experimentation, making periodic resets a potential way to control storage demands while preserving an effective environment for testing.
Storage Growth Becomes a Key Testnet Challenge
The 10 billion-transaction milestone underscores the scale that Aptos testnet activity has reached. As transaction records continue to accumulate, the amount of storage required to maintain the testnet can increase significantly. This can create operational and infrastructure challenges for participants running nodes and other components of the testing network.
AIP-147 appears to address this issue by introducing a defined reset schedule rather than allowing testnet data to grow indefinitely. Under the proposal, a reset would occur no more frequently than once every six months. The six-month minimum interval is intended to provide developers with a sufficiently stable testing period while giving network operators a mechanism to manage storage growth.
The proposal also includes a one-month notice period. Such advance warning could allow developers and infrastructure providers to prepare for the removal of historical testnet data and adjust their testing processes accordingly.
Mainnet Remains Unaffected
A key aspect of the development is that the proposed reset mechanism would not apply to the Aptos mainnet. The distinction is important because mainnet transactions represent live network activity and have substantially different requirements for data retention, reliability and continuity.
Full AIP introduced by @AptosLabs' @sherryxiao: https://t.co/T38jTiNPXi
— Aptos (@Aptos) August 22, 2026
The proposal leaves the Aptos mainnet untouched, meaning the suggested resets are limited to the testnet and are aimed at managing development infrastructure rather than altering the live blockchain.
For developers, a predictable reset schedule could make testnet planning easier. Teams would have clearer expectations about how long test data can remain available and when they may need to recreate testing environments. The notice period could also reduce disruption by giving projects time to back up relevant information or adjust development workflows.
The proposed policy may also benefit node operators by placing a recurring limit on the accumulation of testnet data. Smaller data requirements could potentially make it easier to maintain testing infrastructure, although the precise operational impact would depend on how the proposal is implemented.
Proposal Highlights Growing Network Activity
The milestone also illustrates the level of activity generated on Aptos test infrastructure. Processing more than 10 billion transactions indicates substantial use of the environment for testing and development, while simultaneously demonstrating the infrastructure costs associated with maintaining an ever-growing historical record.
If adopted, AIP-147 would establish a structured mechanism for periodically clearing testnet data while maintaining advance communication with developers and infrastructure providers.
The proposal remains focused on testnet operations, and its significance is primarily related to scalability and resource management rather than changes to Aptos’ live network. As the testnet continues to support development activity, a defined reset policy could provide a balance between maintaining a useful testing environment and controlling the infrastructure burden created by accumulated transaction data.
