<h1 align="center">Multi-Exchange Infinity Grid Trading Algorithm</h1>
<div align="center">
[](https://github.com/btschwertfeger/infinity-grid)
[](https://shields.io/)
[](https://pepy.tech/project/infinity-grid)
[](https://github.com/astral-sh/ruff)
[](https://mypy-lang.org/)
[](https://github.com/btschwertfeger/infinity-grid/actions/workflows/cicd.yaml)
[](https://app.codecov.io/gh/btschwertfeger/infinity-grid)
[](https://securityscorecards.dev/viewer/?uri=github.com/btschwertfeger/infinity-grid)
[](https://www.bestpractices.dev/projects/9956)
[](https://github.com/btschwertfeger/infinity-grid/releases)
[](https://pypi.org/project/infinity-grid/)
[](https://infinity-grid.readthedocs.io/en/stable)
[](https://t.me/mx_infinity_grid)
[](https://t.me/mx_infinity_grid/3)
<!-- [](https://doi.org/10.5281/zenodo.14735203) -->
</div>
> ⚠️ **Disclaimer**: This software was initially designed for private use only.
> Please note that this project is independent and not endorsed by any of the
> supported exchanges including Kraken or Payward Ltd. Users should be aware
> that they are using third-party software, and the authors of this project are
> not responsible for any issues, losses, or risks associated with its usage.
> **The supported exchanges and their parent companies are in no way associated
> with the authors of this package and documentation.**
>
> _There is no guarantee that this software will work flawlessly at this or later
> times. Of course, no responsibility is taken for possible profits or losses.
> This software probably has some errors in it, so use it at your own risk. Also
> no one should be motivated or tempted to invest assets in speculative forms of
> investment. By using this software you release the author(s) from any
> liability regarding the use of this software._
The infinity-grid is a trading algorithm that uses grid trading strategies that
places buy and sell orders in a grid-like manner, while following the principle
of buying low and selling high. It is designed for trading cryptocurrencies,
stocks, and derivatives on various exchanges, initially only supporting
[Kraken](https://pro.kraken.com) Spot exchange with plans to expand to other
major exchanges, is written in Python and currently uses the
[python-kraken-sdk](https://github.com/btschwertfeger/python-kraken-sdk) library
to interact with the Kraken API, with additional exchange adapters planned.
The algorithm requires a PostgreSQL or SQLite database and is designed to be run
in a container. The algorithm can be configured to use different
trading strategies, such as GridHODL, GridSell, SWING, and cDCA. While the
verbosity levels of logging provide useful insights into the algorithms's
behavior, the custom notification channels such as Telegram can be used to
receive updates on the algorithms's activity.
Note: This project is the successor of the
[kraken-infinity-grid](https://github.com/btschwertfeger/kraken-infinity-grid).
**Documentation:**
- https://infinity-grid.readthedocs.io/en/latest/
- https://infinity-grid.readthedocs.io/en/stable/
**PnL Calculator (for tax purposes):**
- Kraken: https://github.com/btschwertfeger/kraken-pnl-calculator
**Product Support Matrix:**
| Exchange | Status |
| ---------------------------------------- | ------- |
| [Coinbase](https://binance.com) | Planned |
| [Binance](https://binance.com) | Planned |
| [Kraken](https://pro.kraken.com) | ✅ |
| Other ideas? Issues and PRs are welcome! | 💡 |
## 📚 Fundamental concepts
`infinity-grid` is a sophisticated trading algorithm designed for
automated cryptocurrency trading using a grid strategy. This approach is
particularly effective in volatile markets, where frequent price fluctuations
allow for consistent profit opportunities through structured buying and selling
patterns.
### 📈 The core idea: Grid trading
At its essence, grid trading aims to capitalize on market volatility by setting
a series of buy and sell orders at predefined intervals. The algorithm operates
within a "grid" of prices, purchasing assets when prices dip and selling them as
prices rise. This systematic approach helps in capturing small gains repeatedly,
leveraging the natural oscillations in market prices.
<div align="center">
<figure>
<img
src="doc/_static/images/blsh.png?raw=true"
alt="Buying low and selling high in high-volatile markets"
style="background-color: white; border-radius: 7px">
<figcaption>Figure 1: Buying low and selling high in high-volatile markets</figcaption>
</figure>
</div>
_All currency pairs mentioned here are for illustrative purposes only._
### 📊 Key Elements of Grid Trading
1. **Intervals**: Unlike fully static systems, `infinity-grid` uses fixed
intervals that shift up or down based on price movements, ensuring continuous
trading and avoids manual interactions. This flexibility is crucial for
maintaining profitability in diverse market environments.
2. **Volatility Advantage**: High volatility is a friend to grid traders. The
more the price oscillates, the more opportunities arise to buy low and sell
high. The algorithm thrives in such conditions, with each price movement
potentially triggering a profitable trade.
3. **Consistent Position Sizing**: Each trade involves a consistent volume in
terms of the quote currency (e.g., $100 per trade). This uniformity
simplifies the management of trades and helps in maintaining a balanced
portfolio.
### 📉 Risk Management and Reinvestment
1. **Risk Mitigation**: The algorithm inherently incorporates risk management by
spreading investments across multiple price levels and maintaining almost
consistent trade sizes. This diversification reduces the impact of adverse
market movements on the overall portfolio.
2. **Reinvestment Mechanism**: Accumulated profits can be reinvested, enhancing
the trading capital and potential returns. The algorithm automatically
adjusts buy and and places sell orders to reflect the increased capital, thus
compounding growth over time.
## 📊 Available strategies
Each of the following strategies is designed to leverage different aspects of
market behavior, providing flexibility and adaptability to traders depending on
their risk tolerance, market outlook, and investment goals.
### `GridHODL`
The _GridHODL_ strategy operates on a predefined grid system where buy and sell
orders are placed at fixed intervals below and above the current market price,
respectively. This strategy is designed to capitalize on market fluctuations by
buying low and selling high, ensuring gradual accumulation of the base currency
over time.
Technical Breakdown:
- **Order Placement**: The algorithm dynamically adjusts $n$ buy orders below
the current market price. For example, with a 4% interval, if the current BTC
price is $50,000, the first buy order is set at $48,000, the second at
$46,080, and so on.
- **Execution**: Upon execution of a buy order, a corresponding sell order is
immediately placed at 4% above the purchase price respecting a fixed quote
volume. This creates a cycle of continuous buying and selling, with each cycle
aiming to yield a small portion in the base currency.
- **Accumulation**: Unlike traditional trading strategies, GridHODL is designed
to accumulate the base currency gradually. Each buy order slightly increases
the holdings, while the fixed order size in terms of quote currency (e.g.,
$100) ensures consistent exposure.
This strategy is particularly effective in sideways, slightly, and high volatile
markets, where frequent price oscillations allow for regular execution of the
grid orders. Accumulating the base currency over time can lead to significant
gains, especially when prices rise after a long accumulation phase.
### `GridSell`
The _GridSell_ is a complementary approach to `GridHODL`, focusing on
liquidating the purchased base currency in each trade cycle to realize immediate
profits. The key distinction is that each sell order matches the total quantity
bought in the preceding buy order.
Technical Breakdown:
- **Order Logic**: For every buy order executed (e.g., purchasing $100 worth of
BTC at $48,000), a sell order is placed for the entire amount of BTC acquired
at a 4% higher price. This ensures that each trade cycle results in a complete
turnover of the base currency.
- **Profit Realization**: The strategy ensures that profits are locked in at
each cycle, reducing the need for long-term accumulation or holding. It is
particularly suitable for traders who prioritize short-term gains over base
currency accumulation.
- **Risk Mitigation**: By liquidating the entire bought amount, the GridSell
strategy minimizes exposure to prolonged market downturns, ensuring that the
trader consistently realizes profits without holding onto assets for extended
periods.
### `SWING`
The _SWING_ strategy builds upon `GridHODL` but introduces a mechanism to
capitalize on significant upward price movements by selling accumulated base
currency at higher levels.
Technical Breakdown:
- **Market Adaptation**: This strategy tracks the highest buy price within a
defined range (e.g., $40,000 to $80,000). If the market price exceeds this
range (e.g., rises to $83,200), the algorithm initiates sell orders at
predefined intervals (e.g., 4% above the highest buy price).
- **Sell Execution**: Unlike `GridHODL`, which focuses on buying and selling in
cycles, SWING starts selling accumulated base currency once the price
surpasses the highest recorded buy price. This ensures that profits are
captured during bullish market trends.
- **Continuous Accumulation**: Even as it initiates sell orders above the
highest buy price, the algorithm continues to place buy orders below it,
ensuring that base currency accumulation continues during market dips.
- **Profit Maximization**: This dual approach allows traders to benefit from
both upward trends (through sell orders) and downward corrections (through
continued accumulation).
> ⚠️ It also starts selling the already existing base currency above the current
> price. This should be kept in mind when choosing this strategy.
### `cDCA`
The _cDCA_ (Custom Dollar-Cost Averaging) strategy diverges from traditional DCA
by incorporating dynamic interval adjustments to optimize long-term accumulation
of the base currency.
Technical Breakdown:
- **Fixed Interval Purchases**: Unlike time-based DCA, cDCA places buy orders at
fixed percentage intervals (e.g., every 4% price movement) rather than at
regular time intervals. This ensures that purchases are made in response to
market movements rather than arbitrary time frames.
- **No Sell Orders**: cDCA focuses purely on accumulation. It consistently buys
the base currency (e.g., $100 worth of BTC) at each interval without placing
corresponding sell orders, banking on long-term price appreciation.
- **Adaptive Buy Orders**: The algorithm adapts to rising prices by shifting buy
orders upward rather than letting them fall out of scope. For instance, if the
price exceeds $60,000, new buy orders are placed at 4% intervals below this
new level, maintaining relevance in the current market context.
- **Long-Term Growth**: This strategy is ideal for traders with a long-term
investment horizon, aiming to build a significant position in the base
currency over time, with the expectation of future price increases.
<a name="setup"></a>
## 🚀 Setup
<a name="preparation"></a>
### Preparation
Before installing and running the `infinity-grid` algorithm, you need to make
sure to fully understand the available trading strategies and their
configuration. Avoid running the algorithm with real money before you are
confident in the algorithm's behavior and performance!
Depending on the used exchange, different preparatory steps might be needed. In
the following, the steps for use with the Kraken Crypto Asset Exchange is shown:
1. In order to trade at the [Kraken Crypto Asset
Exchange](https://pro.kraken.com), you need to generate API keys for the
Kraken exchange (see [How to create an API
key](https://support.kraken.com/hc/en-us/articles/360000919966-How-to-create-an-API-key)).
Make sure to generate keys with the required permissions for trading and
querying orders:
<div align="center">
<figure>
<img
src="doc/_static/images/kraken_api_key_permissions.png?raw=true"
alt="Required API key permissions"
style="background-color: white; border-radius: 7px">
<figcaption>Figure 2: Required API key permissions</figcaption>
</figure>
</div>
2. [optional] The algorithm leverages Telegram Bots to send notifications about
the current state of the algorithm. We need two, one for the notifications
about the algorithm's state and trades and one for notifications about
errors.
- Create two bots, name as you wish via: https://telegram.me/BotFather.
- Start the chat with both new Telegram bots and write any message to ensure
that the chat ID is available in the next step.
- Get the bot token from the BotFather and access
`https://api.telegram.org/bot<your bot token here>/getUpdates` to receive
your chat ID.
- Save the chat IDs as well as the bot tokens for both of them, we'll need
them later.
### Running the algorithm
The repository of the
[`infinity-grid`](https://github.com/btschwertfeger/infinity-grid)
contains a `docker-compose.yaml` file that can be used to run the algorithm
using Docker Compose. This file also provides a default configuration for the
PostgreSQL database. To run the algorithm, ensure the required environment
variables are set and start the containers using:
```console
docker compose up -d
```
## 🛠 Configuration
| Variable | Type | Description |
| -------------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `INFINITY_GRID_API_PUBLIC_KEY` | `str` | The API public key provided by the exchange. |
| `INFINITY_GRID_API_SECRET_KEY` | `str` | The API secret key provided by the exchange. |
| `INFINITY_GRID_RUN_EXCHANGE` | `str` | The exchange to trade on. |
| `INFINITY_GRID_RUN_NAME` | `str` | The name of the instance. Can be any name that is used to differentiate between instances of the infinity-grid. |
| `INFINITY_GRID_RUN_USERREF` | `int` | A reference number to identify the algorithms's orders. This can be a timestamp or any integer number. **Use different userref's for different algorithms!** |
| `INFINITY_GRID_BOT_VERBOSE` | `int`/(`-v`,`-vv`) | Enable verbose logging. |
| `INFINITY_GRID_RUN_BASE_CURRENCY` | `str` | The base currency e.g., `BTC` or `AVAX`. |
| `INFINITY_GRID_RUN_QUOTE_CURRENCY` | `str` | The quote currency e.g., `USD` or `EUR`. |
| `INFINITY_GRID_RUN_AMOUNT_PER_GRID` | `float` | The amount to use per grid interval e.g., `100` (USD). |
| `INFINITY_GRID_RUN_INTERVAL` | `float` | The interval between orders e.g., `0.04` to have 4 % intervals. |
| `INFINITY_GRID_RUN_N_OPEN_BUY_ORDERS` | `int` | The number of concurrent open buy orders e.g., `5`. The number of always open buy positions specifies how many buy positions should be open at the same time. If the interval is defined to 2%, a number of 5 open buy positions ensures that a rapid price drop of almost 10% that can be caught immediately. |
| `INFINITY_GRID_RUN_MAX_INVESTMENT` | `str` | The maximum investment amount, e.g. `1000` USD. |
| `INFINITY_GRID_RUN_FEE` | `float` | A custom fee percentage, e.g. `0.0026` for 0.26 % fee. |
| `INFINITY_GRID_RUN_STRATEGY` | `str` | The trading strategy (e.g., `GridHODL`, `GridSell`, `SWING`, or `cDCA`). |
| `INFINITY_GRID_DRY_RUN` | `bool` | Enable dry-run mode (no actual trades). |
| `INFINITY_GRID_RUN_SKIP_PRICE_TIMEOUT` | `bool` | Skip checking if there was a price update in the last 10 minutes. By default, the bot will exit if no recent price data is available. This might be useful for assets that aren't traded that often. |
| `INFINITY_GRID_RUN_TELEGRAM_TOKEN` | `str` | The Telegram bot token for notifications. |
| `INFINITY_GRID_RUN_TELEGRAM_CHAT_ID` | `str` | The Telegram chat ID for notifications. |
| `INFINITY_GRID_RUN_TELEGRAM_THREAD_ID` | `str` | The Telegram thread ID for notifications. |
| `INFINITY_GRID_RUN_DB_USER` | `str` | The PostgreSQL database user. |
| `INFINITY_GRID_RUN_DB_NAME` | `str` | The PostgreSQL database name. |
| `INFINITY_GRID_RUN_DB_PASSWORD` | `str` | The PostgreSQL database password. |
| `INFINITY_GRID_RUN_DB_HOST` | `str` | The PostgreSQL database host. |
| `INFINITY_GRID_RUN_DB_PORT` | `int` | The PostgreSQL database port. |
| `INFINITY_GRID_RUN_SQLITE_FILE` | `str` | The path to a local SQLite database file, e.g., `/path/to/sqlite.db`, will be created if it does not exist. If a SQLite database is used, the PostgreSQL database configuration is ignored. |
<a name="monitoring"></a>
## 📡 Monitoring
Trades as well as open positions can be monitored at the exchanges', where they
can also be managed. Keep in mind that canceling via UI is possible, but placing
orders that the algorithm will manage is not possible, as it only manages orders
that it has placed, e.g. for the Kraken Crypto Asset exchange at
https://pro.kraken.com.
<div align="center">
<figure>
<img
src="doc/_static/images/kraken_dashboard.png?raw=true"
alt="Required API key permissions"
style="background-color: white; border-radius: 7px">
<figcaption>Figure 3: Monitoring orders via Kraken's web UI</figcaption>
</figure>
</div>
Additionally, the algorithm can be configured to send notifications regarding
the current state of the algorithm via Telegram Bots (see
[Preparation](#preparation)).
<div align="center">
<figure>
<img
src="doc/_static/images/telegram_update.png?raw=true"
alt="Required API key permissions"
style="background-color: white; border-radius: 7px; height: 500px">
<figcaption>Figure 4: Monitoring orders and trades via Telegram</figcaption>
</figure>
</div>
## 🚨 Troubleshooting
- Only use release versions of the `infinity-grid` algorithm. The `master` and
other branches might contain unstable code! Also pin the the dependencies used
in order to avoid unexpected behavior.
- Check the **permissions of your API keys** and the required permissions on the
respective endpoints of your chosen exchange.
- If you get some Cloudflare or **rate limit errors**, please check your tier
level on your exchange and maybe apply for a higher rank if required.
- **Use different API keys for different algorithms**, because the nonce
calculation is based on timestamps and a sent nonce must always be the highest
nonce ever sent of that API key. Having multiple algorithms using the same
keys will result in invalid nonce errors.
- Exchanges often have **maintenance windows**. Please check the status page of
your exchange for more information.
- When encountering errors like "Could not find order '...'. Retry 3/3 ...",
this might be due to the **exchange API being slow**. The algorithm will retry
the request up to three times before raising an exception. If the order is
still not available, just restart the algorithm - or let this be handled by
Docker compose to restart the container automatically. Then the order will
most probably be found.
- Always use unique user reference keys/numbers for each trading bot instance.
The algorithm will know what orders to handle based on passed user reference
numbers and selected trading pair.
## 📈 Backtesting
There are currently no backtesting mechanisms implemented. This will be added
soon.
<a name="notes"></a>
## 📝 Notes
This project follows the principles of [semantic
versioning](https://semver.org/) (`v<Major>.<Minor>.<Patch>`). Here's what each
part signifies:
- **Major**: This denotes significant changes that may introduce new features or
modify existing ones. It's possible for these changes to be breaking, meaning
backward compatibility is not guaranteed. To avoid unexpected behavior, it's
advisable to specify at least the major version when pinning dependencies.
- **Minor**: This level indicates additions of new features or extensions to
existing ones. Typically, these changes do not break existing implementations.
- **Patch**: Here, you'll find bug fixes, documentation updates, and changes
related to continuous integration (CI). These updates are intended to enhance
stability and reliability without altering existing functionality.
Raw data
{
"_id": null,
"home_page": null,
"name": "infinity-grid",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.11",
"maintainer_email": null,
"keywords": "crypto, trading, trading bot, grid trading, exchange",
"author": null,
"author_email": "Benjamin Thomas Schwertfeger <contact@b-schwertfeger.de>",
"download_url": "https://files.pythonhosted.org/packages/21/9f/d39882e7554d720e23ff0e5d2c211703a64d8c9f20a2f9038df858048ae6/infinity_grid-1.0.0.tar.gz",
"platform": null,
"description": "<h1 align=\"center\">Multi-Exchange Infinity Grid Trading Algorithm</h1>\n\n<div align=\"center\">\n\n[](https://github.com/btschwertfeger/infinity-grid)\n[](https://shields.io/)\n[](https://pepy.tech/project/infinity-grid)\n\n[](https://github.com/astral-sh/ruff)\n[](https://mypy-lang.org/)\n[](https://github.com/btschwertfeger/infinity-grid/actions/workflows/cicd.yaml)\n[](https://app.codecov.io/gh/btschwertfeger/infinity-grid)\n\n[](https://securityscorecards.dev/viewer/?uri=github.com/btschwertfeger/infinity-grid)\n[](https://www.bestpractices.dev/projects/9956)\n\n[](https://github.com/btschwertfeger/infinity-grid/releases)\n[](https://pypi.org/project/infinity-grid/)\n[](https://infinity-grid.readthedocs.io/en/stable)\n\n[](https://t.me/mx_infinity_grid)\n[](https://t.me/mx_infinity_grid/3)\n\n<!-- [](https://doi.org/10.5281/zenodo.14735203) -->\n\n</div>\n\n> \u26a0\ufe0f **Disclaimer**: This software was initially designed for private use only.\n> Please note that this project is independent and not endorsed by any of the\n> supported exchanges including Kraken or Payward Ltd. Users should be aware\n> that they are using third-party software, and the authors of this project are\n> not responsible for any issues, losses, or risks associated with its usage.\n> **The supported exchanges and their parent companies are in no way associated\n> with the authors of this package and documentation.**\n>\n> _There is no guarantee that this software will work flawlessly at this or later\n> times. Of course, no responsibility is taken for possible profits or losses.\n> This software probably has some errors in it, so use it at your own risk. Also\n> no one should be motivated or tempted to invest assets in speculative forms of\n> investment. By using this software you release the author(s) from any\n> liability regarding the use of this software._\n\nThe infinity-grid is a trading algorithm that uses grid trading strategies that\nplaces buy and sell orders in a grid-like manner, while following the principle\nof buying low and selling high. It is designed for trading cryptocurrencies,\nstocks, and derivatives on various exchanges, initially only supporting\n[Kraken](https://pro.kraken.com) Spot exchange with plans to expand to other\nmajor exchanges, is written in Python and currently uses the\n[python-kraken-sdk](https://github.com/btschwertfeger/python-kraken-sdk) library\nto interact with the Kraken API, with additional exchange adapters planned.\n\nThe algorithm requires a PostgreSQL or SQLite database and is designed to be run\nin a container. The algorithm can be configured to use different\ntrading strategies, such as GridHODL, GridSell, SWING, and cDCA. While the\nverbosity levels of logging provide useful insights into the algorithms's\nbehavior, the custom notification channels such as Telegram can be used to\nreceive updates on the algorithms's activity.\n\nNote: This project is the successor of the\n[kraken-infinity-grid](https://github.com/btschwertfeger/kraken-infinity-grid).\n\n**Documentation:**\n\n- https://infinity-grid.readthedocs.io/en/latest/\n- https://infinity-grid.readthedocs.io/en/stable/\n\n**PnL Calculator (for tax purposes):**\n\n- Kraken: https://github.com/btschwertfeger/kraken-pnl-calculator\n\n**Product Support Matrix:**\n\n| Exchange | Status |\n| ---------------------------------------- | ------- |\n| [Coinbase](https://binance.com) | Planned |\n| [Binance](https://binance.com) | Planned |\n| [Kraken](https://pro.kraken.com) | \u2705 |\n| Other ideas? Issues and PRs are welcome! | \ud83d\udca1 |\n\n## \ud83d\udcda Fundamental concepts\n\n`infinity-grid` is a sophisticated trading algorithm designed for\nautomated cryptocurrency trading using a grid strategy. This approach is\nparticularly effective in volatile markets, where frequent price fluctuations\nallow for consistent profit opportunities through structured buying and selling\npatterns.\n\n### \ud83d\udcc8 The core idea: Grid trading\n\nAt its essence, grid trading aims to capitalize on market volatility by setting\na series of buy and sell orders at predefined intervals. The algorithm operates\nwithin a \"grid\" of prices, purchasing assets when prices dip and selling them as\nprices rise. This systematic approach helps in capturing small gains repeatedly,\nleveraging the natural oscillations in market prices.\n\n<div align=\"center\">\n <figure>\n <img\n src=\"doc/_static/images/blsh.png?raw=true\"\n alt=\"Buying low and selling high in high-volatile markets\"\n style=\"background-color: white; border-radius: 7px\">\n <figcaption>Figure 1: Buying low and selling high in high-volatile markets</figcaption>\n </figure>\n</div>\n\n_All currency pairs mentioned here are for illustrative purposes only._\n\n### \ud83d\udcca Key Elements of Grid Trading\n\n1. **Intervals**: Unlike fully static systems, `infinity-grid` uses fixed\n intervals that shift up or down based on price movements, ensuring continuous\n trading and avoids manual interactions. This flexibility is crucial for\n maintaining profitability in diverse market environments.\n\n2. **Volatility Advantage**: High volatility is a friend to grid traders. The\n more the price oscillates, the more opportunities arise to buy low and sell\n high. The algorithm thrives in such conditions, with each price movement\n potentially triggering a profitable trade.\n\n3. **Consistent Position Sizing**: Each trade involves a consistent volume in\n terms of the quote currency (e.g., $100 per trade). This uniformity\n simplifies the management of trades and helps in maintaining a balanced\n portfolio.\n\n### \ud83d\udcc9 Risk Management and Reinvestment\n\n1. **Risk Mitigation**: The algorithm inherently incorporates risk management by\n spreading investments across multiple price levels and maintaining almost\n consistent trade sizes. This diversification reduces the impact of adverse\n market movements on the overall portfolio.\n\n2. **Reinvestment Mechanism**: Accumulated profits can be reinvested, enhancing\n the trading capital and potential returns. The algorithm automatically\n adjusts buy and and places sell orders to reflect the increased capital, thus\n compounding growth over time.\n\n## \ud83d\udcca Available strategies\n\nEach of the following strategies is designed to leverage different aspects of\nmarket behavior, providing flexibility and adaptability to traders depending on\ntheir risk tolerance, market outlook, and investment goals.\n\n### `GridHODL`\n\nThe _GridHODL_ strategy operates on a predefined grid system where buy and sell\norders are placed at fixed intervals below and above the current market price,\nrespectively. This strategy is designed to capitalize on market fluctuations by\nbuying low and selling high, ensuring gradual accumulation of the base currency\nover time.\n\nTechnical Breakdown:\n\n- **Order Placement**: The algorithm dynamically adjusts $n$ buy orders below\n the current market price. For example, with a 4% interval, if the current BTC\n price is $50,000, the first buy order is set at $48,000, the second at\n $46,080, and so on.\n- **Execution**: Upon execution of a buy order, a corresponding sell order is\n immediately placed at 4% above the purchase price respecting a fixed quote\n volume. This creates a cycle of continuous buying and selling, with each cycle\n aiming to yield a small portion in the base currency.\n- **Accumulation**: Unlike traditional trading strategies, GridHODL is designed\n to accumulate the base currency gradually. Each buy order slightly increases\n the holdings, while the fixed order size in terms of quote currency (e.g.,\n $100) ensures consistent exposure.\n\nThis strategy is particularly effective in sideways, slightly, and high volatile\nmarkets, where frequent price oscillations allow for regular execution of the\ngrid orders. Accumulating the base currency over time can lead to significant\ngains, especially when prices rise after a long accumulation phase.\n\n### `GridSell`\n\nThe _GridSell_ is a complementary approach to `GridHODL`, focusing on\nliquidating the purchased base currency in each trade cycle to realize immediate\nprofits. The key distinction is that each sell order matches the total quantity\nbought in the preceding buy order.\n\nTechnical Breakdown:\n\n- **Order Logic**: For every buy order executed (e.g., purchasing $100 worth of\n BTC at $48,000), a sell order is placed for the entire amount of BTC acquired\n at a 4% higher price. This ensures that each trade cycle results in a complete\n turnover of the base currency.\n- **Profit Realization**: The strategy ensures that profits are locked in at\n each cycle, reducing the need for long-term accumulation or holding. It is\n particularly suitable for traders who prioritize short-term gains over base\n currency accumulation.\n- **Risk Mitigation**: By liquidating the entire bought amount, the GridSell\n strategy minimizes exposure to prolonged market downturns, ensuring that the\n trader consistently realizes profits without holding onto assets for extended\n periods.\n\n### `SWING`\n\nThe _SWING_ strategy builds upon `GridHODL` but introduces a mechanism to\ncapitalize on significant upward price movements by selling accumulated base\ncurrency at higher levels.\n\nTechnical Breakdown:\n\n- **Market Adaptation**: This strategy tracks the highest buy price within a\n defined range (e.g., $40,000 to $80,000). If the market price exceeds this\n range (e.g., rises to $83,200), the algorithm initiates sell orders at\n predefined intervals (e.g., 4% above the highest buy price).\n- **Sell Execution**: Unlike `GridHODL`, which focuses on buying and selling in\n cycles, SWING starts selling accumulated base currency once the price\n surpasses the highest recorded buy price. This ensures that profits are\n captured during bullish market trends.\n- **Continuous Accumulation**: Even as it initiates sell orders above the\n highest buy price, the algorithm continues to place buy orders below it,\n ensuring that base currency accumulation continues during market dips.\n- **Profit Maximization**: This dual approach allows traders to benefit from\n both upward trends (through sell orders) and downward corrections (through\n continued accumulation).\n\n> \u26a0\ufe0f It also starts selling the already existing base currency above the current\n> price. This should be kept in mind when choosing this strategy.\n\n### `cDCA`\n\nThe _cDCA_ (Custom Dollar-Cost Averaging) strategy diverges from traditional DCA\nby incorporating dynamic interval adjustments to optimize long-term accumulation\nof the base currency.\n\nTechnical Breakdown:\n\n- **Fixed Interval Purchases**: Unlike time-based DCA, cDCA places buy orders at\n fixed percentage intervals (e.g., every 4% price movement) rather than at\n regular time intervals. This ensures that purchases are made in response to\n market movements rather than arbitrary time frames.\n- **No Sell Orders**: cDCA focuses purely on accumulation. It consistently buys\n the base currency (e.g., $100 worth of BTC) at each interval without placing\n corresponding sell orders, banking on long-term price appreciation.\n- **Adaptive Buy Orders**: The algorithm adapts to rising prices by shifting buy\n orders upward rather than letting them fall out of scope. For instance, if the\n price exceeds $60,000, new buy orders are placed at 4% intervals below this\n new level, maintaining relevance in the current market context.\n- **Long-Term Growth**: This strategy is ideal for traders with a long-term\n investment horizon, aiming to build a significant position in the base\n currency over time, with the expectation of future price increases.\n\n<a name=\"setup\"></a>\n\n## \ud83d\ude80 Setup\n\n<a name=\"preparation\"></a>\n\n### Preparation\n\nBefore installing and running the `infinity-grid` algorithm, you need to make\nsure to fully understand the available trading strategies and their\nconfiguration. Avoid running the algorithm with real money before you are\nconfident in the algorithm's behavior and performance!\n\nDepending on the used exchange, different preparatory steps might be needed. In\nthe following, the steps for use with the Kraken Crypto Asset Exchange is shown:\n\n1. In order to trade at the [Kraken Crypto Asset\n Exchange](https://pro.kraken.com), you need to generate API keys for the\n Kraken exchange (see [How to create an API\n key](https://support.kraken.com/hc/en-us/articles/360000919966-How-to-create-an-API-key)).\n Make sure to generate keys with the required permissions for trading and\n querying orders:\n\n<div align=\"center\">\n <figure>\n <img\n src=\"doc/_static/images/kraken_api_key_permissions.png?raw=true\"\n alt=\"Required API key permissions\"\n style=\"background-color: white; border-radius: 7px\">\n <figcaption>Figure 2: Required API key permissions</figcaption>\n </figure>\n</div>\n\n2. [optional] The algorithm leverages Telegram Bots to send notifications about\n the current state of the algorithm. We need two, one for the notifications\n about the algorithm's state and trades and one for notifications about\n errors.\n\n - Create two bots, name as you wish via: https://telegram.me/BotFather.\n - Start the chat with both new Telegram bots and write any message to ensure\n that the chat ID is available in the next step.\n - Get the bot token from the BotFather and access\n `https://api.telegram.org/bot<your bot token here>/getUpdates` to receive\n your chat ID.\n - Save the chat IDs as well as the bot tokens for both of them, we'll need\n them later.\n\n### Running the algorithm\n\nThe repository of the\n[`infinity-grid`](https://github.com/btschwertfeger/infinity-grid)\ncontains a `docker-compose.yaml` file that can be used to run the algorithm\nusing Docker Compose. This file also provides a default configuration for the\nPostgreSQL database. To run the algorithm, ensure the required environment\nvariables are set and start the containers using:\n\n```console\ndocker compose up -d\n```\n\n## \ud83d\udee0 Configuration\n\n| Variable | Type | Description |\n| -------------------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `INFINITY_GRID_API_PUBLIC_KEY` | `str` | The API public key provided by the exchange. |\n| `INFINITY_GRID_API_SECRET_KEY` | `str` | The API secret key provided by the exchange. |\n| `INFINITY_GRID_RUN_EXCHANGE` | `str` | The exchange to trade on. |\n| `INFINITY_GRID_RUN_NAME` | `str` | The name of the instance. Can be any name that is used to differentiate between instances of the infinity-grid. |\n| `INFINITY_GRID_RUN_USERREF` | `int` | A reference number to identify the algorithms's orders. This can be a timestamp or any integer number. **Use different userref's for different algorithms!** |\n| `INFINITY_GRID_BOT_VERBOSE` | `int`/(`-v`,`-vv`) | Enable verbose logging. |\n| `INFINITY_GRID_RUN_BASE_CURRENCY` | `str` | The base currency e.g., `BTC` or `AVAX`. |\n| `INFINITY_GRID_RUN_QUOTE_CURRENCY` | `str` | The quote currency e.g., `USD` or `EUR`. |\n| `INFINITY_GRID_RUN_AMOUNT_PER_GRID` | `float` | The amount to use per grid interval e.g., `100` (USD). |\n| `INFINITY_GRID_RUN_INTERVAL` | `float` | The interval between orders e.g., `0.04` to have 4 % intervals. |\n| `INFINITY_GRID_RUN_N_OPEN_BUY_ORDERS` | `int` | The number of concurrent open buy orders e.g., `5`. The number of always open buy positions specifies how many buy positions should be open at the same time. If the interval is defined to 2%, a number of 5 open buy positions ensures that a rapid price drop of almost 10% that can be caught immediately. |\n| `INFINITY_GRID_RUN_MAX_INVESTMENT` | `str` | The maximum investment amount, e.g. `1000` USD. |\n| `INFINITY_GRID_RUN_FEE` | `float` | A custom fee percentage, e.g. `0.0026` for 0.26 % fee. |\n| `INFINITY_GRID_RUN_STRATEGY` | `str` | The trading strategy (e.g., `GridHODL`, `GridSell`, `SWING`, or `cDCA`). |\n| `INFINITY_GRID_DRY_RUN` | `bool` | Enable dry-run mode (no actual trades). |\n| `INFINITY_GRID_RUN_SKIP_PRICE_TIMEOUT` | `bool` | Skip checking if there was a price update in the last 10 minutes. By default, the bot will exit if no recent price data is available. This might be useful for assets that aren't traded that often. |\n| `INFINITY_GRID_RUN_TELEGRAM_TOKEN` | `str` | The Telegram bot token for notifications. |\n| `INFINITY_GRID_RUN_TELEGRAM_CHAT_ID` | `str` | The Telegram chat ID for notifications. |\n| `INFINITY_GRID_RUN_TELEGRAM_THREAD_ID` | `str` | The Telegram thread ID for notifications. |\n| `INFINITY_GRID_RUN_DB_USER` | `str` | The PostgreSQL database user. |\n| `INFINITY_GRID_RUN_DB_NAME` | `str` | The PostgreSQL database name. |\n| `INFINITY_GRID_RUN_DB_PASSWORD` | `str` | The PostgreSQL database password. |\n| `INFINITY_GRID_RUN_DB_HOST` | `str` | The PostgreSQL database host. |\n| `INFINITY_GRID_RUN_DB_PORT` | `int` | The PostgreSQL database port. |\n| `INFINITY_GRID_RUN_SQLITE_FILE` | `str` | The path to a local SQLite database file, e.g., `/path/to/sqlite.db`, will be created if it does not exist. If a SQLite database is used, the PostgreSQL database configuration is ignored. |\n\n<a name=\"monitoring\"></a>\n\n## \ud83d\udce1 Monitoring\n\nTrades as well as open positions can be monitored at the exchanges', where they\ncan also be managed. Keep in mind that canceling via UI is possible, but placing\norders that the algorithm will manage is not possible, as it only manages orders\nthat it has placed, e.g. for the Kraken Crypto Asset exchange at\nhttps://pro.kraken.com.\n\n<div align=\"center\">\n <figure>\n <img\n src=\"doc/_static/images/kraken_dashboard.png?raw=true\"\n alt=\"Required API key permissions\"\n style=\"background-color: white; border-radius: 7px\">\n <figcaption>Figure 3: Monitoring orders via Kraken's web UI</figcaption>\n </figure>\n</div>\n\nAdditionally, the algorithm can be configured to send notifications regarding\nthe current state of the algorithm via Telegram Bots (see\n[Preparation](#preparation)).\n\n<div align=\"center\">\n <figure>\n <img\n src=\"doc/_static/images/telegram_update.png?raw=true\"\n alt=\"Required API key permissions\"\n style=\"background-color: white; border-radius: 7px; height: 500px\">\n <figcaption>Figure 4: Monitoring orders and trades via Telegram</figcaption>\n </figure>\n</div>\n\n## \ud83d\udea8 Troubleshooting\n\n- Only use release versions of the `infinity-grid` algorithm. The `master` and\n other branches might contain unstable code! Also pin the the dependencies used\n in order to avoid unexpected behavior.\n- Check the **permissions of your API keys** and the required permissions on the\n respective endpoints of your chosen exchange.\n- If you get some Cloudflare or **rate limit errors**, please check your tier\n level on your exchange and maybe apply for a higher rank if required.\n- **Use different API keys for different algorithms**, because the nonce\n calculation is based on timestamps and a sent nonce must always be the highest\n nonce ever sent of that API key. Having multiple algorithms using the same\n keys will result in invalid nonce errors.\n- Exchanges often have **maintenance windows**. Please check the status page of\n your exchange for more information.\n- When encountering errors like \"Could not find order '...'. Retry 3/3 ...\",\n this might be due to the **exchange API being slow**. The algorithm will retry\n the request up to three times before raising an exception. If the order is\n still not available, just restart the algorithm - or let this be handled by\n Docker compose to restart the container automatically. Then the order will\n most probably be found.\n- Always use unique user reference keys/numbers for each trading bot instance.\n The algorithm will know what orders to handle based on passed user reference\n numbers and selected trading pair.\n\n## \ud83d\udcc8 Backtesting\n\nThere are currently no backtesting mechanisms implemented. This will be added\nsoon.\n\n<a name=\"notes\"></a>\n\n## \ud83d\udcdd Notes\n\nThis project follows the principles of [semantic\nversioning](https://semver.org/) (`v<Major>.<Minor>.<Patch>`). Here's what each\npart signifies:\n\n- **Major**: This denotes significant changes that may introduce new features or\n modify existing ones. It's possible for these changes to be breaking, meaning\n backward compatibility is not guaranteed. To avoid unexpected behavior, it's\n advisable to specify at least the major version when pinning dependencies.\n- **Minor**: This level indicates additions of new features or extensions to\n existing ones. Typically, these changes do not break existing implementations.\n- **Patch**: Here, you'll find bug fixes, documentation updates, and changes\n related to continuous integration (CI). These updates are intended to enhance\n stability and reliability without altering existing functionality.\n",
"bugtrack_url": null,
"license": null,
"summary": "Multi-exchange Infinity Grid Trading Algorithm",
"version": "1.0.0",
"project_urls": null,
"split_keywords": [
"crypto",
" trading",
" trading bot",
" grid trading",
" exchange"
],
"urls": [
{
"comment_text": null,
"digests": {
"blake2b_256": "d2ce4dbf70c8d40e491a18b786ce725cca6e61b409cce76b6d8c011726fc7e3f",
"md5": "196f817ae195239c5fff1ee33dfbd5f3",
"sha256": "f3dd1b4f40a79af93def6b8e9114919cd1a31df8c6082748343dd0a812079957"
},
"downloads": -1,
"filename": "infinity_grid-1.0.0-py3-none-any.whl",
"has_sig": false,
"md5_digest": "196f817ae195239c5fff1ee33dfbd5f3",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.11",
"size": 61890,
"upload_time": "2025-09-02T06:33:15",
"upload_time_iso_8601": "2025-09-02T06:33:15.712429Z",
"url": "https://files.pythonhosted.org/packages/d2/ce/4dbf70c8d40e491a18b786ce725cca6e61b409cce76b6d8c011726fc7e3f/infinity_grid-1.0.0-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": null,
"digests": {
"blake2b_256": "219fd39882e7554d720e23ff0e5d2c211703a64d8c9f20a2f9038df858048ae6",
"md5": "d738089170da8e9ff987012bbfe9ddd0",
"sha256": "47b8d965301e00b868109eb45fa389ef128a51f38e7c23c21a49b87e3cd40c3c"
},
"downloads": -1,
"filename": "infinity_grid-1.0.0.tar.gz",
"has_sig": false,
"md5_digest": "d738089170da8e9ff987012bbfe9ddd0",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.11",
"size": 62683,
"upload_time": "2025-09-02T06:33:16",
"upload_time_iso_8601": "2025-09-02T06:33:16.882253Z",
"url": "https://files.pythonhosted.org/packages/21/9f/d39882e7554d720e23ff0e5d2c211703a64d8c9f20a2f9038df858048ae6/infinity_grid-1.0.0.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2025-09-02 06:33:16",
"github": false,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"lcname": "infinity-grid"
}
JSON