Transaction cannot be confirmed if fee emulation fails

[k0zibek]

I ran into an issue in Tonkeeper Pro where a transaction cannot be confirmed if the fee emulation step fails.
Even though the transaction itself is valid and would be executed successfully on-chain, the wallet UI blocks signing completely when emulation fails.

HTTP status: 500; {error: "to many iterations: 1100/1100"}

If fee emulation fails, it would be great if the user could still proceed:

• Allow signing and sending the transaction anyway
• Or show a warning that the fee could not be estimated
• Or use a fallback / approximate fee

[xHetso]

This is a really needed improvement. I run into this issue quite often — fee emulation fails, but the transaction itself is valid and would succeed on-chain.

Because of this, I constantly have to work around the UI and resolve things manually via the CLI/console, which is far from ideal.

[verificatorrus]

Thanks for the report — this is indeed a painful UX issue.

I’ve opened a PR that addresses this by introducing an optional Blind Sign flow, allowing users to proceed when fee estimation fails, with explicit warnings and confirmations to keep the default flow safe.

PR: #537