Definition and scope
What Are Drops? The Smallest Unit of XRP addresses a distinct part of xrp and ledger fundamentals. Learn how XRP amounts are represented in drops and why APIs often use integer values.
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
XRPL represents native XRP in integer drops: 1 XRP equals 1,000,000 drops. JSON transaction fields such as Fee and XRP Amount values use quoted drop strings so software can avoid floating-point rounding.
- drops: verify this field, object, or component against the cited protocol documentation.
- Amount: verify this field, object, or component against the cited protocol documentation.
- Fee: verify this field, object, or component against the cited protocol documentation.
- integer serialization: verify this field, object, or component against the cited protocol documentation.
Practical example and checks
A Payment Amount of "2500000" represents 2.5 XRP, while a Fee of "12" represents 0.000012 XRP. Applications should convert only for display and preserve the integer value for signing.
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
A drop is a denomination, not a token issued separately from XRP. Issued currencies and MPT amounts use different JSON structures and decimal rules, so a universal amount parser is unsafe.
Names and identifiers describe protocol state; they do not establish ownership, identity, market value, or an affiliation with Ripple.
Current network status
Enabled on XRPL Mainnet. The underlying protocol capability is available on XRPL Mainnet. Individual services can still impose additional rules, limits, or trust assumptions.
Status reviewed 2026-08-23. Amendment-dependent behavior must be rechecked against the network's live feature state before operational use.