feat(tangle-cloud): wire dispute-bond claim flow (v0.15.0)#3206
Merged
Conversation
Closes the TODO carried since v0.14.0 — `cancelSlash` stopped auto-refunding the disputer's bond, so disputers now need a pull-pattern claim flow. Adds: - `usePendingDisputeBondRefund(account)` — reads `pendingDisputeBondRefund(address)` on TANGLE and surfaces the outstanding refund balance for the connected disputer. - `useClaimDisputeBondTx()` — wraps `claimDisputeBond()` via the shared `useContractWrite` plumbing; invalidates the refund balance query on success so the UI updates without a page refresh. - Operator-manage page: emerald refund-available card that appears when there's a non-zero pending refund (or after a failed claim attempt). Surfaces the amount, a Claim refund button, and a Dismiss affordance when an error needs to be cleared. Wires through `libs/tangle-shared-ui/src/data/graphql/index.ts` re-exports so downstream consumers can use the hooks directly.
✅ Deploy Preview for tangle-cloud ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for tangle-dapp ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for tangle-leaderboard ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
drewstone
added a commit
that referenced
this pull request
May 14, 2026
… to master Promotes: - #3204 fix(vite): merge @radix-ui into react chunk to break load-order cycle - #3206 feat(tangle-cloud): wire dispute-bond claim flow (v0.15.0) - #3208 chore: retire `staging` branch, document develop → master flow This is the first non-cascade release after retiring the staging branch. From this point forward, every `[RELEASE]`-tagged commit on develop auto-promotes to master via auto-sync-master-with-develop.yml.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes the TODO carried since v0.14.0 in `useSlashing.ts` — `cancelSlash` stopped auto-refunding the disputer's bond, so disputers now need a pull-pattern claim flow.
Changes
`libs/tangle-shared-ui/src/data/graphql/useSlashing.ts`
`apps/tangle-cloud/src/pages/operators/manage/page.tsx`
`libs/tangle-shared-ui/src/data/graphql/index.ts`
Verification