Skip to content

update: Changes to the XLS-68 PR before merge#564

Open
mvadari wants to merge 8 commits into
masterfrom
68-updates
Open

update: Changes to the XLS-68 PR before merge#564
mvadari wants to merge 8 commits into
masterfrom
68-updates

Conversation

@mvadari

@mvadari mvadari commented Jun 16, 2026

Copy link
Copy Markdown
Collaborator

High Level Overview of Change

Title says it all

Context of Change

XRPLF/rippled#7350

Type of Change

  • XLS Update (changes to an existing XLS)

Copilot AI review requested due to automatic review settings June 16, 2026 20:36

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates XLS-0068 (Sponsored Fees and Reserves) to align the specification with ongoing implementation work (notably rippled PR #7350), adding clarifications for pseudo-accounts, reserve carve-outs, Batch transaction behavior, and feature interactions.

Changes:

  • Adds/clarifies sponsorship constraints around pseudo-accounts and pseudo-account–owned objects, plus reserve carve-out behavior.
  • Specifies sponsorship rules and failure conditions related to Batch (XLS-56) and permissioned delegation interactions.
  • Renumbers/extends later sections (Feature Interactions, Invariants, etc.) and updates various references (with some remaining inconsistencies).

1. The sponsor does not have enough XRP to cover the reserve (`tecINSUFFICIENT_RESERVE`).
2. The transaction does not support reserve sponsorship (see section [8.3.4](#834-transactions-that-cannot-be-sponsored))
3. The transaction creates a ledger object whose owner is an account other than `tx.Account` (e.g. `AMMClawback` creating a trust line on behalf of the holder).
4. The transaction includes an `sfDelegate` field and `spfReserve` is enabled. Reserve sponsorship combined with permissioned delegation is disallowed.
Comment on lines +782 to +787
10. If transferring the sponsorship to a new sponsor:
11. The transaction is not submitted by the sponsee (`tecNO_PERMISSION`)
12. The `Sponsor` field or the `SponsorFlags` field is missing (`temMALFORMED`)
13. The `SponsorFlags` field does not include the `spfSponsorReserve` flag (`temINVALID_FLAG`)
14. The new sponsor account does not exist (`terNO_ACCOUNT`)
15. The new sponsor does not have enough XRP to cover the reserve for this object/account (`tecINSUFFICIENT_RESERVE`)
Comment thread XLS-0068-sponsored-fees-and-reserves/README.md Outdated
Comment thread XLS-0068-sponsored-fees-and-reserves/README.md Outdated
Comment thread XLS-0068-sponsored-fees-and-reserves/README.md Outdated
Comment thread XLS-0068-sponsored-fees-and-reserves/README.md Outdated
Comment thread XLS-0068-sponsored-fees-and-reserves/README.md Outdated
Comment thread XLS-0068-sponsored-fees-and-reserves/README.md Outdated
Comment thread XLS-0068-sponsored-fees-and-reserves/README.md Outdated
Comment thread XLS-0068-sponsored-fees-and-reserves/README.md Outdated
mvadari and others added 5 commits June 16, 2026 16:42
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants