Skip to content

Use reclaim wording for Tron resource staking claims#6096

Closed
j0ntz wants to merge 2 commits into
developfrom
jon/trx-stake-language
Closed

Use reclaim wording for Tron resource staking claims#6096
j0ntz wants to merge 2 commits into
developfrom
jon/trx-stake-language

Conversation

@j0ntz

@j0ntz j0ntz commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Description

Edge's staking UI reused yield-staking wording for the Tron resource-freeze policies: "Claim Rewards", "Amount of Reward to Claim", "TRX Earned". Tron pays no APY and holds no third-party reward. Freezing TRX buys bandwidth and energy, and the action Edge calls "claim" is WithdrawExpireUnfreeze, which returns the user's own previously frozen TRX to their spendable balance after the network's post-unfreeze delay. The old copy read as if the user had earned that TRX.

A StakePolicy can now supply claimLanguage to replace the default claim wording, and the Tron resource policies set it. For currency:tron:BANDWIDTH_V2 and currency:tron:ENERGY_V2:

Surface Before After
Stake Overview claim button, claim scene title Claim Rewards Reclaim TRX
Claim amount tile Amount of Reward to Claim Amount of TRX to Reclaim
Claimable position row TRX Earned TRX Pending Reclaim
Post-send notification Claim transactions sent successfully Reclaim transaction sent successfully

Every other staking policy keeps the existing reward wording. This is display-only: the transaction built, the claim amount, and the claim availability rules are unchanged.

Wording follows the direction on the task: Michael McMurray proposed "Unstake" or "Reclaim Resources" and Alberto Mercado confirmed that satisfies the communication need. "Unstake" is already the unfreeze action on the same scene, so the claim action takes the "Reclaim" wording, naming TRX rather than resources because TRX is what the user gets back.

Asana: https://app.asana.com/0/1215088146871429/1211050361847785

CHANGELOG

Does this branch warrant an entry to the CHANGELOG?

  • Yes
  • No

Dependencies

none

Requirements

If you have made any visual changes to the GUI. Make sure you have:

  • Tested on iOS device
  • Tested on Android device
  • Tested on small-screen device (iPod Touch)
  • Tested on large-screen device (tablet)

Tested on the iOS simulator against edge-funds / My Tron 2, which held a real
41.289 TRX unfrozen balance past Tron's post-unfreeze delay. Drove
Earn → TRON Resources v2 → Reclaim TRX and executed the real
WithdrawExpireUnfreeze: the claim scene showed "Amount of TRX to Reclaim", the
transaction broadcast, the "Reclaim transaction sent successfully" flash
appeared, and the pending-reclaim row cleared with the button returning to
disabled. Screenshots attached below.


Note

Low Risk
UI copy and optional policy metadata only; no changes to claim transaction building or staking logic beyond string selection.

Overview
Tron resource-freeze policies no longer use yield-staking copy (“Claim Rewards”, earned rewards, etc.) for the claim flow. StakePolicy can now supply optional claimLanguage (actionLabel, amountLabel, positionLabel, successMessage), and Stake Overview / Stake Modify read those strings when present instead of the default claim/reward labels.

The Tron resource plugin sets claimLanguage to reclaim TRX wording (e.g. “Reclaim TRX”, “TRX Pending Reclaim”, reclaim success toast). New stake_reclaim_* strings were added; other stake policies keep existing reward wording. Display-only—claim transactions and eligibility are unchanged.

Reviewed by Cursor Bugbot for commit 932e69b. Bugbot is set up for automated code reviews on this repo. Configure here.

j0ntz added 2 commits July 23, 2026 19:32
Freezing TRX buys bandwidth and energy rather than yield, and the claim
action only returns the user's own unfrozen TRX to their spendable
balance. Let a stake policy replace the default reward wording so the
Tron policies read as reclaiming instead of earning.
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@j0ntz

j0ntz commented Jul 24, 2026

Copy link
Copy Markdown
Contributor Author

📸 Test evidence

stake overview reclaim button

stake overview reclaim button

reclaim claim scene quote

reclaim claim scene quote

reclaim success flash

reclaim success flash

post reclaim position cleared

post reclaim position cleared

Captured by the agent's in-app test run (build-and-test).

@j0ntz

j0ntz commented Jul 24, 2026

Copy link
Copy Markdown
Contributor Author

Superseded by #6105, which consolidates this and 11 other small GUI task branches into one PR/branch per the umbrella task's instructions.

@j0ntz j0ntz closed this Jul 24, 2026
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.

1 participant