Definition and scope
Rippling and the No Ripple Setting addresses a distinct part of issued tokens and trust lines. Learn how balances can shift across compatible trust lines and how users limit unwanted pathways.
Unlike native XRP, most fungible assets on XRPL represent obligations issued by an account. This category explains the trust relationships, flags, controls, and accounting conventions that make issued currencies and newer Multi-Purpose Tokens work. Issued assets depend on their issuer and must not be described as native XRP. Issuer controls apply only to eligible issued balances.
How it works
Rippling allows compatible issued-currency obligations to shift through an account during payment path execution. The No Ripple flag limits use of a trust line as an intermediary while still permitting ordinary holding and transfers.
- rippling: verify this field, object, or component against the cited protocol documentation.
- No Ripple: verify this field, object, or component against the cited protocol documentation.
- RippleState flags: verify this field, object, or component against the cited protocol documentation.
- payment path: verify this field, object, or component against the cited protocol documentation.
Practical example and checks
A normal user generally enables No Ripple on non-issuer lines, while an issuing or market-making account models which lines must participate in paths and tests the resulting configurations.
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
No Ripple is directional and trust-line flags are perspective-sensitive. It is not a freeze and does not prevent every incoming or outgoing token transfer.
Issued assets depend on their issuer and must not be described as native XRP. Issuer controls apply only to eligible issued balances.
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.