A testnet is a separate copy of a blockchain that developers use to test new code and applications without risking real money. Testnet tokens are valueless, so the reset carries no direct financial risk to users..
Why Aptos is resetting
The testnet has processed more than 10 billion transactions, more than mainnet’s roughly 6 billion, and the accumulated state has become increasingly expensive to maintain. Archival nodes are approaching 30 terabytes and the indexer database exceeds 70 terabytes, with no natural ceiling, according to AIP-147, the proposal behind the policy.
AIP-147, introduced by Aptos Labs’ Sherry Xiao on Aug. 19, argues the cost of carrying old testnet history now outweighs the benefit of keeping it. Without periodic resets, storage and the associated cloud spend would grow without bound, consuming budget that could fund higher-impact infrastructure work.
Aptos considered alternatives and rejected them. A fixed quarterly cadence would force more redeployment churn than necessary, and selective state pruning would add operational complexity without fully bounding the archival and indexer footprint.
Under the policy, resets happen as needed rather than on a fixed calendar: no more than once every six months, and always with at least one month of public notice. If state growth does not warrant one, a reset may not happen for far longer.
Trending on TheStreet Roundtable:
- McDonald’s deletes viral post over controversial intern claim
- XRP Healthcare says 3-year-old bug drained 4,011 crypto wallets
- Iran makes a major crypto move as U.S. pressure hits its economy
What happens on Oct. 7
The reset is a coordinated operational procedure, not a code change. Testnet validators will halt the existing chain and restart it from a new genesis block.
The testnet faucet, which funds developer accounts with free test tokens, will be reset against the new genesis. Full nodes, archival nodes and indexer databases will re-sync from scratch, and storage tied to the prior state will be decommissioned and reclaimed.
That leaves a checklist for builders. Contracts must be redeployed, test accounts recreated and re-funded from the faucet, and any indexer, explorer or analytics pipeline relying on pre-reset testnet history must plan around losing it. Node operators re-sync from the new genesis and reclaim storage of their own.
One detail is still unsettled. Aptos has not said whether the reset will preserve the testnet’s chain ID and endpoints; the proposal aims to keep well-known endpoints stable where technically feasible, but clients that pin a genesis hash will need to re-sync either way.
Developers keep their tools
Aptos Labs’ answer to losing long-lived testnet history is Forklift, an open-source TypeScript framework for developing, testing and scripting Move contracts. Its network-forking mode pulls real chain state, including accounts, resources and deployed contracts, from mainnet, testnet or devnet and lets developers simulate against it locally without spending gas or touching the live network.
Teams that previously relied on accumulated testnet state can instead fork current mainnet data directly. Aptos advises validating critical test suites against a mainnet fork before Oct. 7 so no workflow depends on pre-reset testnet state.
