Go to website
The plugin for live-trading and paper-trading.
Why do I have to pay for live? I thought it's open source?
The main framework which supports importing candles, backtesting, optimization, the most indicators out there, extensive metrics, research and many more features worth thousands of hours invested from the free time of the main developers and many contributors, while being easy to use, is and will stay open source. See https://jesse.trade/blog/opinion/the-story-behind-jesses-development and [https://jesse.trade/blog/news/the-
Why don't you use ccxt?
ccxt offers WebSocket connection only in its PRO version. We additionally preferred custom solutions. Jesse will implement as many exchanges as possible.
How do I activate my Jesse license?
See the documentation here.
I got the error code ... from the exchange. What does it mean?
In the live mode, you might face certain error codes you don't understand and that aren't documented in Jesse's docs. Luckily, Binance has a list with an explanation for all error codes that might get returned during live trading: https://binance-docs.github.io/apidocs/spot/en/#error-codes If you still aren't sure what it means, head to our Discord and ask there.
My exchange isn't supported. Can I code it myself?
importing candles and backtesting For candle imports and backtesting you can code your own: See here. live mode The exchange code for live trading is inside the live plugin and therefore closed-source. So the answer for live trading currently is no. Make sure to send us a suggestion though. If it's a famous one, it will be surely supported soon.
If I terminate and start again a live session, would the restarted live session know the previous open positions?
No, it'll close them and start again. However, session consistency is a feature under development as it was added to our Trello page.
I changed the config / strategy file, but the live instance didn't change.
Jesse currently doesn't watch for config or strategy changes. You have to restart the instance for changes to have an effect.
It's open source and therefore you have to make the live code open source too!
Jesse uses the MIT license. While ensuring open-source rights to the main framework's code, commercial use isn't prohibited: See here.
Will you support DEFI?
Yes, it's on the todo-list.
What would happen to Jesse if the Saleh stops working on it? Is that even a possibility?
At the moment I have no intention of stopping at any time and so many ideas to implement in the coming months. The first reason of course being that I appreciate supporters of the project, and I continue to do so. But here are more reasons for why I do things from a business aspect of things: Every work that I do is related to trading somehow and Jesse is the main tool I developed and use for all of it. Which is the first reason reason why I built it in the first place, and keep it updated and
How can I contact you?
You can write an email to: email@example.com or join us on Discord.
What would happen to the open positions if a live session is terminated?
At the moment Jesse only understands orders that it submitted by itself, and positions that it caused them to open. Hence, it tries to clean the state on both session start and termination time. So all your open positions get closed, and open orders get canceled.
How can I fix the "Order would immediately trigger" error in Binance?
Sometimes when trading small-cap altcoins on Binance Futures, you might have faced the Order would immediately trigger error. According to my research, this error occurs when the order price that your strategy submits (for example in the case of a long trade) is above the current price which would cause a STOP order, but the moment that order reaches Binance the price has changed and that order would get executed (or triggered as Binance's error mentions) but unfortunately, Binance's API dec
How do I get updates?
You have to manually log in and download the latest version matching your system. Then follow the installation instructions again except this time you need to run it with pip install -U to update instead of install.
I can't validate another instance.
You probably exceeded the allowed number of instances. Login in to your account and go to API Tokens. There you have to remove the old instances.
I recieved ExchangeInMaintenance. What's wrong?
From time to time exchanges have maintenance periods or breakdowns due to high usage. This is when you get the error and you can't do anything about it. Jesse will try to reconnect itself. Most of the time only the position endpoint is affected, which isn't very important. You can visit the exchange's website/status page to confirm the outage or ask in our Discord channel. Normally those outages are temporary. To be on the safe side, when those breakdowns happen, a good practice is to always hav