-
Notifications
You must be signed in to change notification settings - Fork 25
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
TOKEN_NOT_TRADABLE #67
Comments
have you try increasing slippage? |
I just remembered I read a similar issue |
I haven't tried, but can this be about slippage? I am using 0 slippage, as I'm using this within a market cap calculation function. I'm doing 100 checks with 150ms delay between each, and after a few seconds it becomes "available". Sometimes it takes longer than that, though. I have also implemented a backup alternative, where in case of failure it uses the public Jupiter API as a backup, and it works there. |
not really, the only sensible reason was because it just can't find any pool for that pair yet, so it can't make a route. and since you need to restart the api service to pull new market, i think it's ipossible to make it works other than adding it yourself isn't it (https://station.jup.ag/docs/apis/self-hosted#adding-new-markets-without-restart)
|
This is not true anymore. If you're not providing the argument |
I think It'll be useful to send token examples and logs around when it got minted so the jupiter team can debug why it didn't get included in your jupiter node |
please check this token: Bim7QGxe9c82wbbGWmdbqorGEzRtRJvECY4s8YSK8oMq, it can be traded on raydium but it is not tradable on jupyter |
Sometimes new pairs (both Raydium and Pumpfun) get the TOKEN_NOT_TRADABLE error. The node we're using is in perfect sync (always 0 slot difference), and this situation doesn't seem to always happen. While trying to the Jupiter Public API, the tokens not tradable at time of checking are tradable on the public API.
The text was updated successfully, but these errors were encountered: