chore(abi): sync tnt-core v0.11.3 + wire disputeSlash bond value#3172
Merged
Conversation
- ABI: adds getSlashConfig() view - useSlashConfig: new hook reads disputeBond from active SlashConfig - useDisputeSlashTx: forwards disputeBond as msg.value; zero-bond path unchanged (value: undefined), so existing behaviour is preserved Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
✅ Deploy Preview for tangle-cloud 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. |
✅ Deploy Preview for tangle-dapp ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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.
Summary
tangle.tsABI to tnt-core bindings v0.11.3 (addsgetSlashConfig()view)useSlashConfighook that reads activeSlashConfig(includingdisputeBond) from chainuseDisputeSlashTxnow forwardsdisputeBondasmsg.value— required when admin enables non-zero dispute bondsvalue: undefined), so no regression for current mainnet stateWhy this matters
disputeSlashispayableand requiresmsg.value == config.disputeBond. With the default bond of0this was transparent. If an admin callssetSlashConfig(... disputeBond: X ...), all operator-side dispute transactions would revert without this fix.Test plan
🤖 Generated with Claude Code