Exchange Ranking
Top Exchanges
24h Volume Ranking
Popularity Ranking
Exchange BTC Balance
Proof of Reserves
Decentralized Exchanges
Funding Rate
Funding Heatmap
Liquidation Data
Max Pain
Long/Short Ratio
Whale L/S Ratio
Binance/Okex/Huobi L/S
Bitfinex Margin L/S
ETF Tracker
Solana ETF
XRP ETF
Hong Kong ETF
Bitcoin Treasuries
Crypto Reversal
Ethereum Reserves
HyperLiquid Wallet Analysis
Hyperliquid Whale Watch
Large Transactions
On-chain Movement
Bitcoin ROI
Stablecoin Market Cap
Options Analysis
News
Articles
Economic Calendar
Features
Wallet
Contract Calculator
Security
Collections
Watchlist
Following
APT Aptos testnet will undergo its first state reset on October 7
Aptos, a Layer 1 blockchain designed for high-throughput and low-latency transactions, announced on Wednesday that its testnet will be reset on October 7. This is the first time in the history of the network that a status reset has been carried out. This reset will return the test network to a new state of creation. All deployed smart contracts, test accounts, balances, and transaction history will be cleared and need to be redeployed or created.
The main network (i.e., the network where real transactions and assets are located) is not affected. Devnet, a stand-alone environment used for early testing, also continues to operate according to the established reset plan. Testnet is a separate copy of blockchain that developers use to test new code and applications without taking real risks. Since the testnet token has no actual value, this reset has no direct economic risk to users.
Why Aptos needs to be reset
According to statistics, the test network has processed more than 10 billion transactions, and the number even exceeds the main network's approximately 6 billion transactions. As the accumulated status data becomes larger and larger, maintenance costs become more and more expensive. According to the proposal behind the policy, AIP-147, the amount of data in the archive node is close to 30 TB, and the indexer database exceeds 70 TB, with no natural upper limit.
AIP-147 was proposed by Sherry Xiao of Aptos Labs on August 19. The proposal argues that the cost of retaining historical data from older versions of TestNet now exceeds the benefits. Without regular resets, spending on storage and related cloud services will grow endlessly, consuming budgets that could otherwise be used for higher-impact infrastructure work.
Aptos considered other alternatives and rejected them. Fixed quarterly reset frequencies can lead to unnecessary frequent redeployments; selective state pruning can increase operational complexity without completely limiting the size of archives and indexers.
Under the new policy, resets will occur on an as-needed basis rather than following a fixed calendar cycle: up to once every six months, with at least one month's public notice. If the state growth is not enough to support a reset, a reset may not occur for a long time.
What happens on October 7
This reset is a coordinated operating process, not a code change. The testnet verifier will stop running the existing chain and restart it from the new creation block.
Faucet, which provides free test tokens to developer accounts to fund development, will also be reset for the new creation state. The full node, archive node, and indexer databases will be resynchronized from the beginning, and storage associated with the previous state will be deactivated and reclaimed.
This leaves developers with a to-do list: smart contracts must be redeployed, funds must be recreated and obtained from taps to replenish test accounts, and any indexer, browser, or analytical pipeline that relies on the history of the testnet before resetting must plan to respond to the loss of historical data. Node operators need to resynchronize from the new creation block and reclaim their own storage space.
There is still one detail that has not yet been determined. Aptos has not yet stated whether a reset will preserve the test net's chain IDs and endpoints; the proposal is designed to keep well-known endpoints stable where technically feasible, but those clients with a fixed Genesis hash will need to be re-synchronized anyway.
How developers can continue to use tools
In response to the problem of losing long-standing historical data on testnets, Aptos Labs launched Forklift. This is an open source TypeScript framework for developing, testing and writing Move contract scripts. Its network fork model extracts the real chain state (including accounts, resources, and deployed contracts) from the main network, test network, or Devnet, allowing developers to simulate it locally without having to spend Gas fees or touch the real-time network.
Project teams that previously relied on cumulative testnet status can now directly fork current mainnet data. Aptos recommends that developers use mainnet forks to verify critical test suites by October 7 to ensure that no workflow depends on the state of the testnet before reset.
