Overview
Hedera test networks provide developers access to a free testing environment for Hedera network services. Testnets simulate the exact development environment as you would expect for mainnet. This includes transaction fees, throttles, available services, etc. To create a Hedera Testnet or Previewnet account, you can visit the Hedera Developer Portal. Once your application has been built and tested in this test environment, you can expect to migrate your decentralized application (dApp) to mainnet without any changes.| Test Networks | Description |
|---|---|
| Testnet | Testnet runs the same code as the Hedera Mainnet, designed to provide a pre-production environment for developers about to move to mainnet. You can find compatible SDKs here. |
| Previewnet | Code that is under development by the Hedera team and likely to be used in an upcoming release designed to give developers early exposure to features coming down the pipe. Updates to the network are made frequently. There is no guarantee an SDK will readily support the up-and-coming features. Note: Updates to this network are triggered by a new release and are frequent. These updates will not be reflected on the status page. |
| Network Service | Availability |
|---|---|
| Cryptocurrency | Limited |
| Consensus Service | Limited |
| File Service | Limited |
| Smart Contract Service | Limited |
| Token Service | Limited |
Test Network Resets
The mirror node and consensus node test network are scheduled to be reset periodically. Scheduled resets are communicated to the ecosystem with anticipation so developers can plan ahead. During a reset:What Gets Reset
- All account balances and transaction history
- Smart contract state and deployed contracts
- Consensus node ledger state
- Topic and token configurations
What Remains
- Your account’s public/private key pairs
- Access to the Hedera Developer Portal
- SDK configurations and application code
Scheduled Reset Process
Resets follow a structured communication and execution process:Pre-Reset (2-4 weeks before)
- Subscribe to notifications on the Hedera Status Page
- Community notification through official channels
- Developer preparation period begins
During Reset
- Network temporarily unavailable
- Consensus nodes cleared and reinitialized
- Mirror node data archived
Post-Reset (within 24 hours)
- Network restored with fresh state
- New account IDs available via Developer Portal
- Mirror node historical data accessible for 2 weeks
Preparing for Resets
To minimize disruption during scheduled resets:- Export any test data you need to preserve before the reset
- Schedule development activities around announced reset dates
- Obtain new testnet account IDs from the Hedera Developer Portal after each reset
- Mirror Node operators can reference the instructions here to set up your mirror node
- GCP GCS and AWS S3 buckets:
hedera-testnet-streams-2023-01
- GCP GCS and AWS S3 buckets:
Reset History
| Date | Status |
|---|---|
| February 1, 2024 | Completed |
| April 25, 2024 | Skipped |
| July 25, 2024 | Skipped |
| Oct 31, 2024 | Skipped |
Test Network Throttles
| Network Request Type | Throttle (tps) |
|---|---|
| Cryptocurrency Transactions |
|
| Consensus Transactions |
|
| Token Transactions |
|
| Schedule Transactions | ScheduleSignTransaction: 100 tpsScheduleCreateTransaction: 100 tps |
| File Transactions | 10 tps |
| Smart Contract Transactions | ContractExecuteTransaction: 350 tpsContractCreateTransaction: 350 tps |
| Queries (per node) |
|
| Receipts | unlimited (no throttle) |