-
Notifications
You must be signed in to change notification settings - Fork 55
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
Transaction sent, but transaction does not exist #30
Comments
i have seen the same. curious if you figured it out? |
I'm having the same issue, especially when swapping newly released tokens. This seems to be due to limited liquidity or uninitialized token accounts. It would be very helpful if Jupiter's API could include a feature to automatically check for liquidity pools on other DEXs and route swaps there when needed, similar to how the website handles unsupported tokens more effectively. |
hi is anyone can fix the problem? i come with the same issue / |
This
This implies the transaction was sent out to the network but unfortunately didn't make it into a block and expired. It only take about 90 seconds for a transaction to expire on Solana. There're several reasons why your transaction might not be picked of which the most important remains the incentive for the miner to do so. You'd have to match up the priority fee of the most recent successful transactions. Unfortunately, Jupiter doesn't automatically this for you, However, they expose options to help you with it. perhaps you can post some code snippet for further pointer |
Hello, I've noticed that even though I get the output like below, the transaction si not executed 9 out of 10 times. Is that normal?
Example:
Transaction sent: https://explorer.solana.com/tx/2YiaTwoaMa9fY53KpjAGcknHicrew5RBmCtLSSRyoVSyMuFaTmHsZ7QcDwDRGwRuSHHYEboGCvsMjXoEcSFWwdUX
This did not do the transaction, how can I be sure transaction is executed?. The only problem is that the output is ok, the transaction is not executed most of the time.
The text was updated successfully, but these errors were encountered: