Skip to content

XLS-68.1 SponsoredAccountCreate - #666

Open
oleks-rip wants to merge 1 commit into
XRPLF:masterfrom
oleks-rip:sponsored_acc
Open

oleks-rip wants to merge 1 commit into
XRPLF:masterfrom
oleks-rip:sponsored_acc

Conversation

@oleks-rip

Copy link
Copy Markdown

High Level Overview of Change

Update XLS-68, add spec for SponsoredAccountCreate

Context of Change

Described new tx SponsoredAccountCreate which allow to create sponsored account with 0 balance. XRP never touch the account during creation. Additionally the tx can create sponsorship object for the dst account.

Type of Change

  • New XLS Draft
  • XLS Update (changes to an existing XLS)
  • XLS Status Change (e.g., Draft → Final, Draft → Stagnant)
  • Process/Meta (changes to CONTRIBUTING.md, XLS-1, templates, etc.)
  • Infrastructure (CI, workflows, scripts, website)
  • Documentation (README updates, typo fixes)

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.

🟡 Changes recommended

The security guidance understates future reserve exposure authorized by RemainingOwnerCount.

1 open finding
What changed in this PR

Extends XLS-68 with SponsoredAccountCreate, enabling zero-balance sponsored accounts without transferring XRP to them.

Changes:

  • Defines the transaction, optional sponsorship funding, failure conditions, and invariants.
  • Updates the parent specification with SponsorV1_1 gates and cross-references.
File Description
XLS-0068-sponsored-fees-and-reserves/​README.md Integrates the new amendment into account-creation rules.
XLS-0068-sponsored-fees-and-reserves/​68.1/​README.md Specifies sponsored account creation and optional sponsorship setup.

🧠 Review effort: Balanced


💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.


## 5. Security Considerations

The sponsor's exposure is bounded by the transaction: one base reserve for the new account, one object reserve for the `Sponsorship` object, and `FeeAmount`. `MaxFee` caps what a single sponsored transaction may draw from `FeeAmount`, and the reserve-checking failure in [§3.1.4.2](#3142-protocol-level-failures) ensures the sponsor stays above its own reserve after paying them.

This branch has not been deployed

No deployments
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