First two trust lines and reserve
New XRPL accounts historically received reserve relief for the first objects they own — often discussed as the “first two trust lines” exemption in community docs. Rules changed with fee voting; always read live base/incremental reserve and OwnerCount in server_state rather than old blog posts.
Key facts
- Concept: Early OwnerCount exemptions
- Live source: server_state reserve fields
- Typical increment: ~0.2 XRP per object (2024+)
- Tool: XRPline reserve strip
What people mean
Community guides say the first one or two trust lines on a freshly funded wallet do not add incremental reserve. That was a network parameter effect, not a wallet feature. After exemptions are consumed, each additional RippleState behaves like any other owned object.
How to verify your account
- Note OwnerCount before creating a line.
- Sign TrustSet for a test line with minimal limit.
- Compare reserve requirement after validation.
- Remove the test line if you do not need it.
Planning many lines
Account reserve on XRPL is locked XRP, not a fee. Total reserve ≈ base reserve + (OwnerCount × incremental owner reserve). After network fee voting in late 2024, many operators cite ~1 XRP base and ~0.2 XRP per owned object — always verify live values in your wallet or in XRPline’s network strip.
Each new trust line usually increases OwnerCount by one unless an exemption applies (see first two trust lines). Closing an empty line with a zero balance and a cleared limit can reduce OwnerCount and return incremental reserve once the ledger accepts the transaction.
Using XRPline safely
XRPline is a non-custodial TrustLine manager for the XRP Ledger. You connect a wallet or paste a classic address for read-only previews; when you create, change, or remove lines, your wallet signs the TrustSet payload. We never ask for seed phrases or private keys.
Reserve figures, freeze flags, and line tables come from public ledger reads and XRPSCAN API surfaces documented on Methodology. Confirm live base and incremental reserve via server_state before you budget XRP for new lines.
TrustSet, tecNO_LINE, and IOU receipts
This page (guides/first-two-trustlines/) sits in the XRPline trust line cluster for xrpline.org. On ledger, issued assets are never identified by ticker alone: every IOU payment path resolves to a currency code plus issuer classic address. When a receiver lacks that RippleState, validated payments commonly end with result code tecNO_LINE rather than crediting balance.
Creating or updating a line is always a TrustSet transaction. LimitAmount.value sets the maximum IOU balance you accept from that issuer. Setting value to zero after clearing balance removes the object and typically lowers OwnerCount. Wallets may hide the JSON, which is why XRPline exposes a Sign TrustSet preview before you approve.
Native XRP transfers do not use this mechanism. If you only hold XRP, reserve math still applies (base plus owned objects), but you will not see tecNO_LINE for missing IOU lines.
OwnerCount, incremental reserve (~0.2 XRP), and Cleaner
Account reserve on XRPL is locked XRP, not a fee. Total reserve ≈ base reserve + (OwnerCount × incremental owner reserve). After network fee voting in late 2024, many operators cite ~1 XRP base and ~0.2 XRP per owned object — always verify live values in your wallet or in XRPline’s network strip.
Each new trust line usually increases OwnerCount by one unless an exemption applies (see first two trust lines). Closing an empty line with a zero balance and a cleared limit can reduce OwnerCount and return incremental reserve once the ledger accepts the transaction.
Users feel “missing XRP” when spendable balance is low even though total balance looks fine. That gap is often reserve, not theft. Each trust line you open for an airdrop or exchange token usually adds one owned object until you remove it.
XRPline Cleaner sorts zero-balance lines so you can reclaim multiple increments of incremental reserve after campaigns. You still sign one TrustSet per removal — we do not batch-sign and we never hold keys.
Issuer verification before you sign
Scammers exploit ticker collisions: two unrelated projects can both display similar three-letter codes with different issuers. Before any TrustSet, copy the issuer r-address from official documentation and match it character-for-character in the signing payload.
Use issuer lookup, issuer discovery guide, and explorer account flags (freeze, authorized trust lines, clawback) documented in Glossary. Risk tab heuristics prioritize review; they are not purchasable rankings and not financial advice — see Methodology.
FAQ
Are the first two lines always free?
Not guaranteed — network amendments and account funding path matter. Verify live.