Skip to article
XRPAuthority
Tokens · Verified concept guide

XRPL Trust Lines Explained

See how two accounts record limits, balances, and settings for an issued asset relationship.

Published 2026-08-23Reviewed 2026-08-237 minute readBy Matt Barlow
SIMPLE EXPLANATION

Definition and scope

XRPL Trust Lines Explained addresses a distinct part of issued tokens and trust lines. See how two accounts record limits, balances, and settings for an issued asset relationship.

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.

TECHNICAL DEPTH

How it works

A RippleState entry represents a bilateral relationship for one issued currency, including balance, limits, qualities, and flags from each side's perspective. TrustSet creates or changes the holder's settings.

  • RippleState: verify this field, object, or component against the cited protocol documentation.
  • TrustSet: verify this field, object, or component against the cited protocol documentation.
  • LimitAmount: verify this field, object, or component against the cited protocol documentation.
  • account_lines: verify this field, object, or component against the cited protocol documentation.
PRACTICAL EXAMPLE

Practical example and checks

A holder specifies the issuer and currency in LimitAmount, chooses a deliberate limit and No Ripple setting, submits TrustSet, then confirms the resulting line with account_lines.

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 trust line is not an endorsement and does not force an issuer to redeem. Removing it generally requires a zero balance and compatible settings.

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.