Deployed 4390324 to develop in en with MkDocs 1.6.1 and mike 2.1.3

This commit is contained in:
github-actions[bot]
2025-08-25 05:06:28 +00:00
parent adb7b2f5af
commit 7d3ca49be7
5 changed files with 65 additions and 63 deletions

View File

@@ -2427,7 +2427,7 @@ So, in order to mitigate Kraken API "Rate limit exceeded" exception, this config
<span class="w"> </span><span class="c1">// ...</span>
<span class="p">}</span>
</code></pre></div>
<p>Kucoin supports <a href="../configuration/#understand-order_time_in_force">time_in_force</a>.</p>
<p>Kucoin supports <a href="../configuration/#understand-order_time_in_force">time_in_force</a> with settings "GTC" (good till cancelled), "FOK" (full-or-cancel) and "IOC" (immediate-or-cancel) settings.</p>
<div class="admonition tip">
<p class="admonition-title">Stoploss on Exchange</p>
<p>Kucoin supports <code>stoploss_on_exchange</code> and can use both stop-loss-market and stop-loss-limit orders. It provides great advantages, so we recommend to benefit from it.
@@ -2466,8 +2466,9 @@ OKX also only provides MARK candles for the past ~3 months. Backtesting futures
<h2 id="gateio">Gate.io<a class="headerlink" href="#gateio" title="Permanent link">&para;</a></h2>
<div class="admonition tip">
<p class="admonition-title">Stoploss on Exchange</p>
<p>Gate.io supports <code>stoploss_on_exchange</code> and uses <code>stop-loss-limit</code> orders. It provides great advantages, so we recommend to benefit from it by enabling stoploss on exchange..</p>
<p>Gate.io supports <code>stoploss_on_exchange</code> and uses <code>stop-loss-limit</code> orders. It provides great advantages, so we recommend to benefit from it by enabling stoploss on exchange.</p>
</div>
<p>Gate.io supports <a href="../configuration/#understand-order_time_in_force">time_in_force</a> with settings "GTC" (good till cancelled), and "IOC" (immediate-or-cancel) settings.</p>
<p>Gate.io allows the use of <code>POINT</code> to pay for fees. As this is not a tradable currency (no regular market available), automatic fee calculations will fail (and default to a fee of 0).
The configuration parameter <code>exchange.unknown_fee_rate</code> can be used to specify the exchange rate between Point and the stake currency. Obviously, changing the stake-currency will also require changes to this value.</p>
<p>Gate API keys require the following permissions on top of the market type you want to trade:</p>
@@ -2478,8 +2479,14 @@ The configuration parameter <code>exchange.unknown_fee_rate</code> can be used t
</ul>
<p>Without these permissions, the bot will not start correctly and show errors like "permission missing".</p>
<h2 id="bybit">Bybit<a class="headerlink" href="#bybit" title="Permanent link">&para;</a></h2>
<p>Futures trading on bybit is currently supported for USDT markets, and will use isolated futures mode.</p>
<p>On startup, freqtrade will set the position mode to "One-way Mode" for the whole (sub)account. This avoids making this call over and over again (slowing down bot operations), but means that changes to this setting may result in exceptions and errors.</p>
<div class="admonition tip">
<p class="admonition-title">Stoploss on Exchange</p>
<p>Bybit (futures only) supports <code>stoploss_on_exchange</code> and uses <code>stop-loss-limit</code> orders. It provides great advantages, so we recommend to benefit from it by enabling stoploss on exchange.
On futures, Bybit supports both <code>stop-limit</code> as well as <code>stop-market</code> orders. You can use either <code>"limit"</code> or <code>"market"</code> in the <code>order_types.stoploss</code> configuration setting to decide which type to use.</p>
</div>
<p>Bybit supports <a href="../configuration/#understand-order_time_in_force">time_in_force</a> with settings "GTC" (good till cancelled), "FOK" (full-or-cancel), "IOC" (immediate-or-cancel) and "PO" (Post only) settings.</p>
<p>Futures trading on bybit is currently supported for isolated futures mode.</p>
<p>On startup, freqtrade will set the position mode to "One-way Mode" for the whole (sub)account. This avoids making this call over and over again (slowing down bot operations), but means that manual changes to this setting may result in exceptions and errors.</p>
<p>As bybit doesn't provide funding rate history, the dry-run calculation is used for live trades as well.</p>
<p>API Keys for live futures trading must have the following permissions:</p>
<ul>
@@ -2494,11 +2501,6 @@ The configuration parameter <code>exchange.unknown_fee_rate</code> can be used t
We therefore recommend the usage of one subaccount per bot. This is especially important when using unified accounts.<br />
Other configurations (multiple bots on one account, manual non-bot trades on the bot account) are not supported and may lead to unexpected behavior.</p>
</div>
<div class="admonition tip">
<p class="admonition-title">Stoploss on Exchange</p>
<p>Bybit (futures only) supports <code>stoploss_on_exchange</code> and uses <code>stop-loss-limit</code> orders. It provides great advantages, so we recommend to benefit from it by enabling stoploss on exchange.
On futures, Bybit supports both <code>stop-limit</code> as well as <code>stop-market</code> orders. You can use either <code>"limit"</code> or <code>"market"</code> in the <code>order_types.stoploss</code> configuration setting to decide which type to use.</p>
</div>
<h2 id="bitmart">Bitmart<a class="headerlink" href="#bitmart" title="Permanent link">&para;</a></h2>
<p>Bitmart requires the API key Memo (the name you give the API key) to go along with the exchange key and secret.
It's therefore required to pass the UID as well.</p>
@@ -2524,7 +2526,7 @@ It's therefore required to pass the UID as well.</p>
<span class="w"> </span><span class="c1">// ...</span>
<span class="p">}</span>
</code></pre></div>
<p>Bitget supports <a href="../configuration/#understand-order_time_in_force">time_in_force</a>.</p>
<p>Bitget supports <a href="../configuration/#understand-order_time_in_force">time_in_force</a> with settings "GTC" (good till cancelled), "FOK" (full-or-cancel), "IOC" (immediate-or-cancel) and "PO" (Post only) settings.</p>
<div class="admonition tip">
<p class="admonition-title">Stoploss on Exchange</p>
<p>Bitget supports <code>stoploss_on_exchange</code> and can use both stop-loss-market and stop-loss-limit orders. It provides great advantages, so we recommend to benefit from it.