Transaction erroneously retries when "insufficient funds for fee" with WAGMI+Viem+Wallet Connect+Fireblocks

[alexwalchli]

Describe the bug
When connected with Fireblocks to an app that uses WAGMI/Viem, attempting to make a contract call when not having sufficient ETH for the network fee results in 3 retry attempts. If the transaction is cancelled in Fireblocks the retries will stop with a standard user rejected error.

Either the error thrown by Wallet Connect is wrong, or Viem should interpret the error better and not attempt to retry. Given Wallet Connect interprets the error from Fireblocks as an "UnknownRpcError" when it is in fact known (insufficient fees), I figured I'd start here.

Package versions
"viem": "2.21.41",
"wagmi": "2.12.26",
"@dynamic-labs/ethereum": "^3.5.1",
"@dynamic-labs/sdk-react-core": "^3.5.1",
"@dynamic-labs/wagmi-connector": "^3.5.1",

Looks like dynamic is currently using @WalletConnect[email protected]

To Reproduce

1. Connect to an app with the above combination (Wallet Connect through to Fireblocks).
2. Attempt any transaction that will require more ETH than the wallet contains.
3. Watch the transaction appear in Fireblocks, result in an insufficient funds for fee error.
4. You will then note that the transaction appears again in Fireblocks, until after the 3rd retry or if you cancel.
   

Expected behavior
I would not expect the transaction to retry at all.

Screenshots
Error throw by Wallet Connect and being handled by Viem in buildRequest.js. Note that is is "UnknownRpcError", "Session settlement failed.".

[linear]

CR-567 Transaction erroneously retries when "insufficient funds for fee" with WAGMI+Viem+Wallet Connect+Fireblocks