Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SDK/Namadillo: Sometimes Tx broadcast times out #1416

Open
jurevans opened this issue Dec 17, 2024 · 1 comment
Open

SDK/Namadillo: Sometimes Tx broadcast times out #1416

jurevans opened this issue Dec 17, 2024 · 1 comment
Assignees
Labels
App: Namadillo bug Something isn't working Lib: SDK

Comments

@jurevans
Copy link
Collaborator

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).

@jurevans jurevans added bug Something isn't working App: Namadillo Lib: SDK labels Dec 17, 2024
@jurevans jurevans added this to the Namadillo Mainnet Readiness milestone Dec 17, 2024
@jurevans jurevans self-assigned this Dec 17, 2024
@Fraccaman
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
App: Namadillo bug Something isn't working Lib: SDK
Projects
None yet
Development

No branches or pull requests

2 participants