CTYPTO/freqtrade
1
0
Fork 0
mirror of https://github.com/freqtrade/freqtrade.git synced 2026-02-14 18:20:31 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #12811 from stash86/main-stash

Browse Source 
Add note about different pair naming for HIP-3
This commit is contained in:
Matthias
2026-02-12 07:03:44 +01:00
committed by GitHub
parent aff46acdd0 fea13d1d3d
commit ba6d210662
1 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
docs/exchanges.md
View File

@@ -319,7 +319,6 @@ API Keys for live futures trading must have the following permissions:
We do strongly recommend to limit all API keys to the IP you're going to use it from. We do strongly recommend to limit all API keys to the IP you're going to use it from.
## Bitmart ## Bitmart
Bitmart requires the API key Memo (the name you give the API key) to go along with the exchange key and secret. Bitmart requires the API key Memo (the name you give the API key) to go along with the exchange key and secret.
@@ -458,6 +457,8 @@ Replace `"dex_name_1"` and `"dex_name_2"` with the actual names of the HIP-3 DEX
!!! Note !!! Note
HIP-3 DEXes share the same wallet and free amount of collateral as your main Hyperliquid account. Trades on different DEXes will affect your overall account balance and margin. HIP-3 DEXes share the same wallet and free amount of collateral as your main Hyperliquid account. Trades on different DEXes will affect your overall account balance and margin.
The pair name for HIP-3 pairs will be slightly different than non HIP-3 pairs. Please use `list-pairs` subcommand to get the correct pair naming for all pairs for the specified dexes.
## Bitvavo ## Bitvavo
If your account is required to use an operatorId, you can set it in the configuration file as follows: If your account is required to use an operatorId, you can set it in the configuration file as follows: