Authorized Trust Lines Explained

Definition and scope

Authorized Trust Lines Explained addresses a distinct part of issued tokens and trust lines. Require issuer approval before a trust line can hold or transact an issued asset.

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

With RequireAuth enabled, an issuer must authorize each trust line before the holder can receive the asset. Authorization is represented in RippleState flags and managed with TrustSet transactions.

• RequireAuth: verify this field, object, or component against the cited protocol documentation.
• TrustSet: verify this field, object, or component against the cited protocol documentation.
• authorized line: verify this field, object, or component against the cited protocol documentation.
• RippleState: verify this field, object, or component against the cited protocol documentation.

Practical example and checks

A regulated issuer enables RequireAuth before issuing, verifies an applicant off-ledger, authorizes the exact account/currency line, and records evidence linking the decision to the validated transaction.

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.

Limits, risks, and common confusion

Ledger authorization only records the issuer's approval; it does not prove why approval was granted or guarantee ongoing eligibility. Enabling RequireAuth late can create operational complications.

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.