Skip to content

feat(react): burn confirmation, supply update and transaction history (#1220 #1221 #1222 #1223) - #1285

Open
dslegacy wants to merge 1 commit into
BCPathway:mainfrom
dslegacy:feature/1220-1221-1222-1223-burn-flow-and-history
Open

dslegacy wants to merge 1 commit into
BCPathway:mainfrom
dslegacy:feature/1220-1221-1222-1223-burn-flow-and-history

Conversation

@dslegacy

Copy link
Copy Markdown

Summary

  • Burn now opens a ConfirmationDialog; the Burn button stays disabled until "I understand this action permanently destroys tokens" is checked.
  • BurnScreen uses useBurn (SDK simulates before wallet signing); rejections, reverts and network errors show an alert via parseWalletError.
  • Success alert shows the destroyed token count with an optional explorer link; a total supply card decrements immediately and balance and supply are refetched.
  • New TransactionHistory table (operation badge, counterparty, amount, status, time, explorer link) and sessionStorage-backed useSessionTransactions; burns are recorded.

Testing

  • npm run build --workspace @bc-forge/sdk
  • npm test --workspace @bc-forge/react (284 passed)
  • npm run build --workspace @bc-forge/react

Closes #1220
Closes #1221
Closes #1222
Closes #1223

…history

- Gate burn behind a checkbox confirmation dialog (BCPathway#1220)
- Wire BurnScreen to useBurn with parsed wallet errors and explorer receipt (BCPathway#1221)
- Show destroyed amount, decrement total supply immediately and refetch balance/supply (BCPathway#1222)
- Add TransactionHistory table and sessionStorage-backed useSessionTransactions (BCPathway#1223)
@drips-wave

drips-wave Bot commented Oct 18, 2026

Copy link
Copy Markdown

@dslegacy Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

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

1 participant