FTX plugin for Jesse
This is the initial release of the FTX driver for Jesse. At the moment, it is only meant for importing candles and running backtests.
Installation
Install by running:
pip install jesse-ftx
Register your driver
Now you need to tell Jesse where to find this driver. We do that by adding it as a driver for importing candles in plugins.py file that exists in the root of Jesse projects. Here is an example where I register a driver for the FTX exchange:
from jesse.modes.import_candles_mode.drivers.binance import Binance
from jesse.modes.import_candles_mode.drivers.binance_futures import BinanceFutures
from jesse.modes.import_candles_mode.drivers.binance_inverse_futures import BinanceInverseFutures
from jesse.modes.import_candles_mode.drivers.bitfinex import Bitfinex
from jesse.modes.import_candles_mode.drivers.coinbase import Coinbase
from jesse.modes.import_candles_mode.drivers.testnet_binance_futures import TestnetBinanceFutures
from jesse_ftx import FTX
import_candles_drivers = {
'Binance': Binance,
'Binance Futures': BinanceFutures,
'Binance Inverse Futures': BinanceInverseFutures,
'Testnet Binance Futures': TestnetBinanceFutures,
'Bitfinex': Bitfinex,
'Coinbase': Coinbase,
'FTX': FTX
}
Now I should be able to run import candles from FTX:
jesse import-candles 'FTX' 'BTC-USDT' '2012-06-04'
Add new config values for running backtests
Usually the reason for importing candles in the first place is to run backtests on them. So we need to tell Jesse where to find the config values for our newly added exchange in order for it run backtests on it.
We can do that by opening config.py and coping and pasting values from an existing exchange such as Binance Futures and changing the values according to our needs for out exchange:
# https://www.ftx.com
'FTX': {
'fee': 0.0004,
# backtest mode only: accepted are 'spot' and 'futures'
'type': 'futures',
# futures mode only
'settlement_currency': 'USDT',
# accepted values are: 'cross' and 'isolated'
'futures_leverage_mode': 'isolated',
# 1x, 2x, 10x, 50x, etc. Enter as integers
'futures_leverage': 3,
# used for spot exchange only
'assets': [
{'asset': 'USDT', 'balance': 10_000},
{'asset': 'BTC', 'balance': 0},
],
},
Metadata
Release files for jesse-ftx 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| jesse-ftx-0.1.0.tar.gz | 4.1 kB | Without provenance | Details for jesse-ftx-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| jesse_ftx-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for jesse_ftx-0.1.0-py3-none-any.whl |
Total release size: 8.1 kB
Release files / jesse-ftx-0.1.0.tar.gz
| Download URL | jesse-ftx-0.1.0.tar.gz |
|---|---|
| Size | 4.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4b441629ec6a43cbf741d93cf059ed4bf3c6b3e03b827b24a9f5063359b972dc
|
|
BLAKE2b-256 checksum How to use checksums |
8fafa79200a12d538f1cf15319ce555aa65246918a81704692c7da36415e7534
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.4.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.61.0 CPython/3.9.5
|
Release files / jesse_ftx-0.1.0-py3-none-any.whl
| Download URL | jesse_ftx-0.1.0-py3-none-any.whl |
|---|---|
| Size | 4.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0d8a27237e3b2970863ca39b8da5192de4ab083c3ec29fb3fd9103fc1eadda2c
|
|
BLAKE2b-256 checksum How to use checksums |
3f09ab09f1626daa5abbb8a5ce36c86b2397e5ea7fc7b7b1a4b0dc86267270cd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.4.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.61.0 CPython/3.9.5
|
Security for jesse-ftx 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.