Skip to content

Sponsored fees reserves - #1335

Open
cybele-ripple wants to merge 7 commits into
mainfrom
sponsored-fees-reserves
Open

Sponsored fees reserves#1335
cybele-ripple wants to merge 7 commits into
mainfrom
sponsored-fees-reserves

Conversation

@cybele-ripple

@cybele-ripple cybele-ripple commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

High Level Overview of Change

Adds a "Sponsored fees & reserves" section to the account detail page

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Refactor (non-breaking change that only restructures code)
  • Tests (You added tests for code that already exists, or your new feature included in this PR)
  • Documentation Updates
  • Translation Updates
  • Release

Codebase Modernization

  • Updated files to React Hooks
  • Updated files to TypeScript

Preview

Note: this preview includes mock data which is not included in this PR.
Screenshot 2026-08-20 at 10 27 14 AM
Screenshot 2026-08-20 at 10 27 47 AM
Screenshot 2026-08-20 at 10 27 57 AM
Screenshot 2026-08-20 at 10 28 12 AM
Screenshot 2026-08-20 at 10 33 51 AM

Test Plan

Included tests in src/rippled/lib/test/rippled.test.ts

Surfaces XLS-68 sponsorship data on the account detail page: whether
another account is sponsoring this account's base reserve
(AccountRoot.Sponsor) and/or its transaction fees (Sponsorship ledger
object), matching the Figma spec for this feature.
Build table rows from an array instead of duplicated JSX, use the
existing AccountState type instead of any, and move the
show-if-sponsored guard out to the call site to match how
SignersCard/nftMinter/paychannels are conditionally rendered elsewhere
on the account page.
# Conflicts:
#	src/containers/Accounts/index.tsx
@kuan121
kuan121 self-requested a review August 2, 2026 14:20
@@ -729,6 +729,12 @@
"account_page_payment_channels": "Payment Channels",

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.

@cybele-ripple I have a couple of questions about the scope of this PR:

  1. Do we plan to add support for the two new transaction types, SponsorshipSet and SponsorshipTransfer?
  2. This amendment also affects many existing ledger entries and transaction types, and adds common fields to both. Do we need to cover those changes in this PR as well?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

This PR now has Sponsor/SponsorFlags/SponsorSignature fields, so any co-sponsored transaction of any type now shows who's sponsoring its fee and/or reserve. There are now updated screenshots to reflect this

<table className="sponsored-fees-reserves-table">
<thead>
<tr>
<th>{t('account_page_sponsored_scope')}</th>

@kuan121 kuan121 Aug 4, 2026

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.

It's not clear to me what we want to achieve here. An account can have multiple sponsors. Which ones do we show?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I have updated the preview screenshot to show what multiple sponsors look like

An account can have more than one active Sponsorship object; getAccountSponsorship() previously used .find() and silently dropped all but the first, so the account page only ever showed one fee sponsor.
The Sponsored fees & reserves table truncated sponsor addresses via
shortenAccount, but full addresses are more useful for verifying who
is sponsoring an account.
…Sponsor field display

Adds transaction detail rendering (Description/Simple/TableDetail) for the
SponsorshipSet and SponsorshipTransfer transaction types, following the
existing per-transaction-type component pattern, plus generic support for
the transaction-common Sponsor/SponsorFlags/SponsorSignature fields so any
co-sponsored transaction shows who is sponsoring its fee and/or reserve.
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