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
Sometimes users are encountering a "tx failed" error due to a timeout, even when the transactions are successful.
We need to investigate the exact cause of this, and perhaps figure out a better way to verify that a Tx either succeeded or failed. Currently we are throwing an error when our SDK integration broadcastTx() (which in turn calls process_tx() in Namada SDK) throws an error of any kind, which in turn notifies user that the Tx failed (which is obviously not accurate every time).
The text was updated successfully, but these errors were encountered:
The namada sdk can either "send a tx and forget" or "send and wait". The first method, just send a transaction and doesn't check if it was actually included in a block (it just wait until it passes mempool validation). The second instead, waits for the transaction to be included in a block. The timeout you are experiencing is probably due not being able to tell if a tx was included in a block or not during the timeout window
Sometimes users are encountering a "tx failed" error due to a timeout, even when the transactions are successful.
We need to investigate the exact cause of this, and perhaps figure out a better way to verify that a Tx either succeeded or failed. Currently we are throwing an error when our SDK integration
broadcastTx()
(which in turn callsprocess_tx()
in Namada SDK) throws an error of any kind, which in turn notifies user that the Tx failed (which is obviously not accurate every time).The text was updated successfully, but these errors were encountered: