Technical task for developing a bot for arbitrage of spreads and funding rates on cryptocurrency exchanges

1. General Information

• Description: Development of a web application (with mobile adaptation capability) for automated search and execution of arbitrage opportunities based on price spreads and funding rates between different cryptocurrency exchanges (futures contracts USDT-perpetual). The bot should monitor price differences and funding rates, generate signals, manage positions, and send notifications to Telegram.
• Goal: Create a tool for users that allows earning from arbitrage without price change risk (market-neutral), focusing on funding rates and spreads.
• Technological Stack(recommended):
  • Frontend: React.js (as in the existing application).
  • Backend: Node.js or Python (FastAPI/Django) for exchange API processing and arbitrage logic.
  • Database: PostgreSQL or MongoDB for storing positions, history, user settings.
  • Integrations: Exchange APIs (MEXC, Gate.io, Bybit, BingX, Bitget), Telegram Bot API.
  • Hosting: AWS, Heroku, or VPS for the web application.
  • Security: API key encryption, user authentication (login/password + 2FA).

2. Functional Requirements

2.1. Registration and Authentication

• "New User" page: Form for creating a new user with fields:
  • IP Address (auto-filled but displayed as 192.168.0.1 in the example).
  • Login (required).
  • Password (required, with show/hide option).
  • Telegram ID (required for notifications).
• Support for multiple users (multi-account).
• Authentication via login/password.

2.2. Exchange Integration

• "Add Exchanges API Keys" button: Form for entering API keys for exchanges:
  • MEXC: Public Key, Secret Key (special handling since no API for futures; use cookies or alternative method).
  • Gate.io: Public Key, Secret Key.
  • Bybit: Public Key, Secret Key.
  • BingX: Public Key, Secret Key.
  • Bitget: Public Key, Secret Key.
• "Add MEXC Key" button: Separate form for entering MEXC cookies (if API is unavailable).
• Support for additional exchanges in the future (e.g., OKX, Binance Futures).
• Automatic key verification (test request to API).

2.3. Notification Settings

• "Add my own telegram bot" button: Field for entering Telegram username (e.g., "father") to receive signals.
• "Test message" button: Send a test message to Telegram for verification.
• "Send Notification to Telegram" checkbox: Enable/disable notifications.

2.4. Global Settings

• "Profit Rate" field: Minimum desired spread percentage (e.g., 0.5, 2).
• "Volume in USDT Filter" field: Minimum trading volume in USDT for filtering illiquid coins (e.g., 100000).
• "Active exchanges for signals" section: Checkboxes for selecting active exchanges (MEXC, Gate.io, Bybit, BingX, Bitget).
• "Set Parameters" button: Save settings.

2.5. Blacklist

• Section for adding symbols (coins) to blacklist (e.g., BTC, ETH, or meme coins like 100000COQ).
• "Symbol" field for adding, dropdown "Exchange" (All or specific).
• "Add" button, list with "Delete" buttons for removal.
• "Expand/Collapse" button to show/hide the list.
• Automatic exclusion of blacklist from signal search.

2.6. Active Positions

• Table with columns: Exchange, Symbol, Side (LONG/SHORT), Amount.
• Highlight "abandoned" positions in red (positions without active bot).
• "Add to Blacklist" button for symbol.
• Automatic update (refresh) of balances and PNL.

2.7. Signals

• Real-time list of signals:
  • Symbol (e.g., ALPACUSDT).
  • Spread (percentage difference, e.g., 1.07).
  • Side (SHORT/LONG).
  • For each exchange: Funding Rate, Price, Volume USDT.
  • Signal time (e.g., 4s).
  • "Copy to Form" button to copy into creation form.
• Filtering by active exchanges, profit rate, and volume.
• Telegram notifications about new signals (format: "Signal: mexc SHORT - gateio LONG: Symbol: ALPACUSDT Spread: 1.07").

2.8. Detailed Symbol/Card View

• Separate card for each symbol (e.g., RHEA, RDO, CESSUSDT).
• Settings fields:
  • Side: SHORT/LONG (toggle).
  • Open Spread: Percentage spread for opening (e.g., 0.4, 6.3).
  • Close Spread: Percentage spread for closing (e.g., -0.2, 4.8).
  • Order Size: Order size in USDT (e.g., 4000, 24000, converted to $).
  • Max Orders: Maximum number of orders (e.g., 3, 4).
  • Allowed Size: Size limit (e.g., 12000/Max:88500).
  • Force Stop: Checkbox, field for $ (e.g., 400).
  • Is Active?: Start/Stop buttons.
• Exchange data (e.g., MEXC vs Gate.io):
  • Funding Rate (e.g., -0.0121%).
  • Next Funding (time).
  • Ask/Bid Price.
  • Size (in USDT).
  • Adjustment: Notify only / Adjust.
  • Max Size.
  • Price.
  • P/L (profit/loss, e.g., ≈29.66 $).
  • Enter Spread (%).
  • Orders (quantity).
• Spread chart: open/close spread line, min/max, historical data (red/green lines).
• Save buttons for each field.
• Overall: Total cards (number of processed symbols).

2.9. Wallets

• Table: Exchange, Wallet Balance ($), Unrealized PNL ($).
• "Refresh balances" button.
• Error handling (e.g., "Error" for Bybit).

2.10. History

• Date filter: From/To.
• "Load" button.
• "Show Detailed Info" checkbox.
• PNL list by exchanges: Total PNL, positions (e.g., MEXC: 182.39, Total positions: 707).
• Disclaimer.

2.11. Trading Automation

• Optional: Automatic opening/closing of positions based on signals (with or without confirmation).
• Monitoring funding rates for arbitrage (short on exchange with positive rate, long on negative).
• Risk management: Force stop upon reaching loss.

3. Non-Functional Requirements

• Performance: Real-time monitoring (update every 5-10 seconds), processing 100+ symbols.
• Security: Encrypted key storage, no-logging sensitive data.
• Interface: Responsive design (mobile/desktop), similar to screenshots (light theme, blue buttons).
• Logging: Signal history, positions, errors.
• Testing: Unit tests for API, integration testing with exchanges (test accounts).
• Documentation: User manual (Ukrainian/English), API docs.

4. Development Stages

1. Analysis and Design: 1 week (wireframes based on screenshots).
2. Backend: 2 weeks (API integration, arbitrage logic).
3. Frontend: 2 weeks (UI/UX).
4. Integration and Testing: 1 week.
5. Deployment and Support: 1 week.

5. Acceptance Criteria

• Full compliance with functionality in screenshots.
• Testing with real data (test API keys will be provided).
• No bugs in notifications, spread/PNL calculations.
• Code on GitHub with documentation.

6. Additional Wishes

• Ability to add new exchanges without restart.
• Charts using Chart.js.
• Localization: Ukrainian/English.

Contact for clarifications!