rippled fixes paging in account_lines for newer ledger object types

Serguey Asael Shinder02 October 2026, 17:421 min read

The maintainers of rippled, the reference server for the XRP Ledger, merged a fix on 2 October for pagination in three account-level API methods: account_lines, account_offers and account_channels. The pull request, number 8274, does not yet appear in a release.

All three methods page through the objects in an account's owner directory, the ledger structure listing everything an account owns, and hand back a marker so the client can request the next page. When a request comes in with a marker, the server checks that the marker points at an entry that belongs to the account. According to the pull request, that check used a hard-coded list of related object types in a function called rpc::isRelatedToAccount, and the list was written before many of the object types the ledger has gained since: Credential, Oracle, PermissionedDomain, MPTokenIssuance, MPToken, Vault, LoanBroker, Loan, Sponsorship, Delegate and DID among them.

When a page boundary fell on one of those newer entries, the marker could fail validation and pagination broke for that account. The fix makes the marker check generic, verifying membership of the owner directory directly instead of matching a list of types, so it stays correct as new ledger entry types are added. The pull request marks no public API change.

Why it matters

The XRP Ledger has added a long run of new object types through amendments, and every list that names types by hand is a place where the newest ones get forgotten. Wallets and explorers that page through accounts holding vaults, loans or multi-purpose tokens are the ones that would have hit this; the generic check removes the class of bug rather than adding names to the list.