Enable Blind Sign flow when fee estimation fails#537
Open
verificatorrus wants to merge 3 commits intotonkeeper:mainfrom
Open
Enable Blind Sign flow when fee estimation fails#537verificatorrus wants to merge 3 commits intotonkeeper:mainfrom
verificatorrus wants to merge 3 commits intotonkeeper:mainfrom
Conversation
- Add blind sign confirmation to TonTransactionNotification - Fix useGlobalPreferencesQuery usage in ConfirmView with optional chaining - When estimation fails and Blind Sign is enabled, show "Send Anyway" button
feat: add Blind Sign support for TonConnect transactions
scutuatua-crypto
approved these changes
Feb 1, 2026
|
هل ان تساعدني انا لا اعرف |
scutuatua-crypto
approved these changes
Feb 11, 2026
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
3 participants
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.
Context
In some cases (e.g. HTTP 500:
too many iterations), fee emulation fails even though the transaction itself is valid and would be successfully executed on-chain.Currently, when fee estimation fails, the UI completely blocks signing and sending the transaction, leaving the user with no way to proceed.
This PR addresses issue #536:
#536
What’s changed
UX & Safety
Why this matters
Fee estimation failures should not fully block valid transactions.
This change improves reliability in edge cases while preserving user safety and control.
Fixes #536