Golang and Rust Developer for a task
Budget: $30 β $250 USD
Trade Execution Workflow
Once a signal is parsed and validated, the bot must:
1. Check Account Balances on both exchanges.
2. Place a Buy Order (market or configurable limit) on Exchange A.
3. Withdraw the asset using the specified network.
4. Track the transaction until itβs confirmed on the blockchain.
5. Detect deposit arrival on Exchange B.
6. Place a Sell Order (market) on Exchange B.
7. Log the full trade cycle, including outcome.
Supported Exchanges (API Integration Required):
1. HTX (Huobi)
2. BitGet
3. Binance
4. MEXC
5. KuCoin
6. WhiteBit
7. OKX
Each API integration must:
- Use secure authentication (API keys stored securely)
- Support:
- Order placement (buy/sell)
- Withdrawal initiation
- Deposit tracking
- Balance checks
- Transaction status polling
Token Handling & Network Support
The bot must handle cross-exchange transfers using the correct chain, based on signal
info (e.g., BEP20, TRC20, SOL).
Handle naming inconsistencies like:
- PARTI on BitGet may be PARTI-Base on OKX
- AVAX on Binance vs AVAX-C on MEXC
Maintain a token-network-exchange mapping database or config file.
Once a signal is parsed and validated, the bot must:
1. Check Account Balances on both exchanges.
2. Place a Buy Order (market or configurable limit) on Exchange A.
3. Withdraw the asset using the specified network.
4. Track the transaction until itβs confirmed on the blockchain.
5. Detect deposit arrival on Exchange B.
6. Place a Sell Order (market) on Exchange B.
7. Log the full trade cycle, including outcome.
Supported Exchanges (API Integration Required):
1. HTX (Huobi)
2. BitGet
3. Binance
4. MEXC
5. KuCoin
6. WhiteBit
7. OKX
Each API integration must:
- Use secure authentication (API keys stored securely)
- Support:
- Order placement (buy/sell)
- Withdrawal initiation
- Deposit tracking
- Balance checks
- Transaction status polling
Token Handling & Network Support
The bot must handle cross-exchange transfers using the correct chain, based on signal
info (e.g., BEP20, TRC20, SOL).
Handle naming inconsistencies like:
- PARTI on BitGet may be PARTI-Base on OKX
- AVAX on Binance vs AVAX-C on MEXC
Maintain a token-network-exchange mapping database or config file.