You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There was this random bug that we couldn't reproduce, where we were randomly getting safeTxHash sometimes when fetching the txResult, which led to store an invalid txHash instead of the real Optimism txHash.
Few weeks ago this started happening all the time, and the cause is the Safe sponsored transactions. If we use this free transaction feature from Safe, we are receiving the safeTxHash all the time, but I've tried paying gas, and it's getting the good Optimism txHash.
Maybe it's a Safe bug, but tried to log the result just in case we can do something:
"rawResult": {
"hash": "0x5f9c0a0d7b1472242acb8197b5817070433ed50541b98112802f0e92ec84ea08"
},
useTransactor.tsx:96 ⚡️ ~ file: useTransactor.ts ~ error TransactionNotFoundError: Transaction with hash "0x5f9c0a0d7b1472242acb8197b5817070433ed50541b98112802f0e92ec84ea08" could not be found.
Version: [email protected]
at getTransaction (getTransaction.js:58:15)
at async delay.count.count (waitForTransactionReceipt.js:102:48)
at async attemptRetry (withRetry.js:17:30)
Here I think they mention some solutions for this, not sure if they apply for us, or are too hacky.
The text was updated successfully, but these errors were encountered:
There was this random bug that we couldn't reproduce, where we were randomly getting
safeTxHash
sometimes when fetching thetxResult
, which led to store an invalid txHash instead of the real Optimism txHash.Few weeks ago this started happening all the time, and the cause is the Safe sponsored transactions. If we use this free transaction feature from Safe, we are receiving the
safeTxHash
all the time, but I've tried paying gas, and it's getting the good Optimism txHash.Maybe it's a Safe bug, but tried to log the result just in case we can do something:
Here I think they mention some solutions for this, not sure if they apply for us, or are too hacky.
The text was updated successfully, but these errors were encountered: