Definition and scope
XRP Mainnet vs. Testnet vs. Devnet addresses a distinct part of xrp and ledger fundamentals. Compare production and testing networks, their endpoints, data, and valueless test XRP.
This collection establishes the language needed to evaluate every other XRP Ledger topic. It separates the asset from the network, explains the identifiers visible in explorers, and shows how individual transactions fit into an ordered ledger history. Names and identifiers describe protocol state; they do not establish ownership, identity, market value, or an affiliation with Ripple.
How it works
Mainnet is the production network with real XRP and persistent economic history. Testnet usually resembles Mainnet for application testing, while Devnet previews newer server code and amendments; each network has separate ledgers, endpoints, and account state.
- Mainnet: verify this field, object, or component against the cited protocol documentation.
- Testnet: verify this field, object, or component against the cited protocol documentation.
- Devnet: verify this field, object, or component against the cited protocol documentation.
- network ID: verify this field, object, or component against the cited protocol documentation.
- faucet: verify this field, object, or component against the cited protocol documentation.
Comparison at a glance
Use these dimensions to choose between the concepts without treating their names as interchangeable.
| Dimension | Mainnet | Testnet | Devnet |
|---|---|---|---|
| Purpose | Production settlement | Application testing | Preview newer server features |
| Asset | Real XRP | No-value test XRP | No-value test XRP |
| State | Persistent production history | May reset | May reset or change quickly |
| Feature status | Only enabled Mainnet amendments | Can differ from Mainnet | Often includes experimental changes |
Practical example and checks
A developer should generate a test account from the appropriate faucet, connect the client to that network's documented endpoint, and verify the server-reported network ID before signing or funding anything.
For production use, preserve the exact signed or queried data, record the network and validated ledger reference, and compare the result with the current primary documentation before changing off-ledger state.
Open the related live demo or evidence lab →Limits, risks, and common confusion
Test XRP has no value and cannot be moved to Mainnet. Testnet and Devnet may reset, diverge in amendment state, or behave differently from production, so passing a test does not prove Mainnet availability.
Names and identifiers describe protocol state; they do not establish ownership, identity, market value, or an affiliation with Ripple.
Current network status
Mainnet, Testnet, and Devnet compared. This guide explains an operational or representational concept. Confirm live server values and service-specific behavior before relying on it in production.
Status reviewed 2026-08-23. Amendment-dependent behavior must be rechecked against the network's live feature state before operational use.