Definition and scope
Essential Settings for XRPL Token Issuers addresses a distinct part of issued tokens and trust lines. Review account flags and operating choices that affect holders, transfers, and trust.
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
Classic token issuers configure AccountSet flags such as RequireAuth, DefaultRipple, GlobalFreeze, NoFreeze, and AllowTrustLineClawback, plus transfer rates and domain identity where appropriate.
- RequireAuth: verify this field, object, or component against the cited protocol documentation.
- DefaultRipple: verify this field, object, or component against the cited protocol documentation.
- GlobalFreeze: verify this field, object, or component against the cited protocol documentation.
- AllowTrustLineClawback: verify this field, object, or component against the cited protocol documentation.
Practical example and checks
Before distribution, an issuer documents its control policy, sets irreversible choices deliberately, tests trust-line authorization and transfer behavior, and publishes consistent account information.
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
Issuer flags control that issuer's obligations, not native XRP. Technical controls do not by themselves establish compliance, reserve backing, redemption rights, or consumer protection.
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.