Expert Quant Developer — Automated Delta Exchange + Exness MT5 Hedge System

I need an expert quantitative/software developer to build a **fully automated, cross-platform perpetual-contract hedging system from scratch** connecting: * Delta Exchange India * Exness MT5 The system must be designed as a **generic, configurable hedging platform**. It must not be hardcoded for gold, XAUTUSD, XAUUSD, or any single instrument. It must support any compatible perpetual contract that can be hedged against an Exness instrument, provided the contract specifications, pricing, currency conversion, and trading rules are configured correctly. The architecture must allow instruments to be added, removed, or modified in the future without rewriting the core calculation or execution engine. ## Objective The system must automatically: * Identify compatible perpetual contracts and hedge instruments * Calculate the correct hedge quantity for each instrument * Execute both legs * Continuously monitor both accounts * Manage hedge imbalance * Calculate margin and liquidation risk * Track funding, fees, spread, slippage, swap, and conversion costs * Handle failures and recovery without requiring manual intervention * Support multiple instruments with separate calculations and risk controls The system must support configurable hedge relationships such as: * Delta perpetual contract ↔ Exness CFD, spot, or derivative instrument * Crypto perpetual contract ↔ Exness crypto instrument * FX-related perpetual contract ↔ Exness FX instrument * Commodity perpetual contract ↔ Exness commodity instrument * Index perpetual contract ↔ Exness index instrument * Any other compatible perpetual contract and Exness instrument supported by the configured specifications The system must not assume that the two instruments have the same contract size, quote currency, tick size, lot size, price unit, or settlement method. ## Current Setup * Delta capital: ₹20,00,000 * Exness capital: ₹20,00,000 * Exness platform: MT5 * Delta margin mode: Isolated * Current Delta instrument: Configurable perpetual contract * Current Exness instrument: Configurable matching or correlated instrument * Current funding reference: Configurable * USD/INR and other currency conversions may differ between platforms and must be treated as live inputs The current instruments are only an initial configuration. The developer must build the system so that additional perpetual contracts and hedge instruments can be added through configuration files or the dashboard. ## Generic Instrument Configuration Each instrument must have a configurable specification containing, where applicable: * Exchange or broker * Symbol * Instrument type * Base asset * Quote asset * Settlement asset * Contract size * Units per lot * Units per contract * Contract multiplier * Tick size * Tick value * Minimum quantity * Maximum quantity * Quantity step * Price precision * Quantity precision * Margin mode * Leverage * Initial margin * Maintenance margin * Funding interval * Funding calculation method * Trading hours * Market status * Long/short availability * Currency-conversion requirements * Fee schedule * Swap schedule * Expiry or perpetual status * Price source * Bid/ask source * Symbol mapping to the corresponding hedge instrument The system must support different contract specifications on each platform and calculate exposure based on actual economic value rather than simply matching displayed quantities. ## Core Requirement Do not hardcode quantities for any instrument. The system must dynamically calculate the best hedge quantity using: * Contract specifications * Contract multiplier * Base-asset exposure * Notional exposure * Quote currency * Settlement currency * Live exchange rates * Live bid/ask prices * Funding * Fees * Spread * Slippage * Swap * Margin requirements * Account equity * Free margin * Volume step * Minimum and maximum quantity * Leverage * Maximum allowed risk * Maximum hedge deviation * Liquidity * Position limits * Platform-specific trading rules The calculation engine must support multiple hedge objectives, including: 1. Base-asset-neutral hedge 2. Notional-value-neutral hedge 3. Quote-currency P&L-neutral hedge 4. INR P&L-neutral hedge 5. Delta-neutral hedge, where applicable 6. Funding-adjusted hedge 7. Cost-adjusted optimal hedge 8. Risk-weighted hedge 9. Partial hedge 10. Custom user-defined hedge ratio The user must be able to select the hedge method separately for each instrument pair. ## Multi-Instrument Calculation Requirement For every configured perpetual contract, the system must independently calculate: * Required hedge quantity * Hedge ratio * Base-asset exposure * Notional exposure * Quote-currency exposure * INR exposure * Residual exposure * Funding-adjusted exposure * Fee-adjusted exposure * Margin requirement * Maximum safe quantity * Minimum executable quantity * Quantity rounding * Rebalancing quantity * Expected P&L * Worst-case P&L * Break-even movement * Maximum tolerable price movement The system must support multiple active hedge pairs simultaneously. Each pair must have its own: * Configuration * Position state * Hedge cycle * Risk limits * Funding data * P&L calculation * Execution state * Alerts * Emergency rules * Audit trail ## Future Instrument Changes I must be able to change or add instruments in the future without modifying the core source code. The system should provide a configuration interface or structured configuration files where I can: * Add a new Delta perpetual contract * Add a new Exness hedge instrument * Map the two instruments * Enter contract specifications * Select the hedge objective * Set the target hedge ratio * Set leverage and margin limits * Set maximum position size * Set funding assumptions * Set fee schedules * Set risk thresholds * Enable or disable the pair * Configure rebalancing rules * Configure emergency rules The system must validate the configuration before allowing live trading. ## Generic Hedge Calculation Do not use a gold-specific example in the implementation or documentation. The system must work generically when one platform uses a different contract multiplier or lot size from the other platform. For example, if one perpetual contract represents a different number of base units per contract than the corresponding Exness instrument represents per lot, the system must automatically calculate the valid quantity combination that minimizes residual exposure while respecting: * Quantity steps * Minimum quantities * Maximum quantities * Available margin * Liquidity * Fees * Spread * Slippage * Risk limits The system must automatically detect exposure imbalance and calculate the best valid rebalancing trade. ## Hedge Optimization For each instrument pair, the engine should evaluate possible valid quantities and select the best combination based on configurable priorities such as: * Lowest residual exposure * Lowest transaction cost * Highest funding profitability * Lowest margin usage * Lowest liquidation risk * Highest liquidity * Lowest slippage * Maximum capital efficiency * Maximum expected net profitability The optimization method must be configurable. It should support exact calculation, step-based search, optimization algorithms, or a combination of these methods depending on the instrument. ## Trading Engine Build: * Delta REST API integration * Delta WebSocket API integration * Exness MT5 integration * Real-time market-data layer * Instrument and symbol mapping * Order execution * Two-leg synchronized execution * Multi-instrument execution * Partial-fill handling * Rejected-order handling * Slippage control * Price-deviation limits * Position reconciliation * Automatic rebalancing * Duplicate-order protection * Idempotent order handling * Order-state tracking * Retry logic * Timeout handling * Cancel/replace logic where supported * Restart recovery * Emergency flattening or risk-reduction logic The execution engine must never assume that both legs fill at the same price, at the same time, or in the same quantity. ## Execution State Machine Each hedge cycle must have a clear state, such as: * Created * Validated * Awaiting market data * Hedge quantity calculated * First leg submitted * First leg partially filled * First leg filled * Second leg submitted * Second leg partially filled * Both legs filled * Rebalancing required * Risk reduction required * Completed * Failed * Recovery required * Emergency mode The system must persist every state transition and recover correctly after a restart. ## Risk Engine Continuously calculate, for every instrument pair and for the overall portfolio: * Balance * Equity * Free margin * Used margin * Margin level * Initial margin * Maintenance margin * Position exposure * Notional exposure * Base-asset exposure * Quote-currency exposure * Hedge ratio * Residual exposure * Liquidation price * Washout price, where applicable * Safe position size * Maximum tolerable price movement * Maximum daily loss * Maximum strategy loss * Maximum hedge deviation * Maximum margin usage * Maximum account concentration * Cross-pair correlation risk * Funding risk * Basis risk * Liquidity risk * Counterparty and platform risk The system must automatically identify which account, instrument, or hedge pair becomes critical first. ## Portfolio-Level Risk The system must not evaluate each hedge pair in isolation. It must also calculate: * Total Delta exposure * Total Exness exposure * Net exposure across all instruments * Currency exposure * Correlated exposure * Aggregate margin usage * Aggregate liquidation risk * Aggregate funding income or cost * Aggregate fees and slippage * Portfolio-level P&L * Portfolio-level maximum loss * Concentration by asset, exchange, broker, and currency The system must prevent a new hedge from violating portfolio-level risk limits. ## Emergency System Implement configurable: * Warning level * Danger level * Emergency level * Kill switch Triggers should include: * High margin usage * Low free margin * Low margin level * Hedge imbalance * Excessive residual exposure * API failure * MT5 disconnect * Delta disconnect * Stale market data * Large spread * Large slippage * Abnormal basis * Abnormal funding * Unexpected position * Unexpected order * Duplicate order * Price gap * Liquidity reduction * Server failure * Network failure * Currency-conversion failure * Configuration mismatch * Contract-specification mismatch * Account-equity decline * Daily-loss limit breach The system must automatically enter recovery or emergency mode according to predefined rules. Emergency actions must be configurable, including: * Stop opening new positions * Pause a specific hedge pair * Pause all hedge pairs * Reduce exposure * Rebalance positions * Cancel open orders * Close one or both legs * Transfer control to emergency mode * Send alerts * Require manual approval before resuming ## Funding and Profitability Engine Track separately for every instrument pair: * Live funding rate * Funding interval * Funding received * Funding paid * Trading fees * Spread * Slippage * Swap * Borrowing or financing costs * Conversion effects * Data and execution costs, where applicable * Gross P&L * Net P&L * Realized P&L * Unrealized P&L * Expected P&L * Worst-case P&L * Break-even cost * Break-even price movement The system should determine whether each hedge pair and the overall strategy remain economically profitable after all costs. It must support different funding and financing models for different perpetual contracts and Exness instruments. ## Dashboard Create a real-time web dashboard showing, for every configured instrument pair: * Delta position * Exness position * Base-asset exposure on each side * Notional exposure on each side * Hedge ratio * Residual exposure * Quote-currency exposure * INR exposure * Live currency-conversion rates * Funding * Fees * Swap * Gross P&L * Net P&L * Margin * Free margin * Margin level * Liquidation price * Washout price, where applicable * Basis * Spread * Slippage * Market-data status * API status * MT5 status * Delta status * Hedge-cycle status * System status * Errors * Alerts Include: * Interactive multi-instrument hedge calculator * Scenario calculator * Contract-specification editor * Instrument-mapping editor * Risk-limit editor * Funding and fee configuration * Position and order history * Hedge-cycle history * Audit-log viewer * Emergency controls * Paper-trading mode * Demo-trading mode * Live-trading enable/disable controls The calculator must allow me to select any configured perpetual contract and any mapped Exness hedge instrument, then calculate the required quantities using the selected hedge objective. ## Database Use PostgreSQL or an equivalent production database to store: * Instrument definitions * Contract specifications * Instrument mappings * Hedge configurations * Orders * Fills * Positions * Market data * Order-book data, where available * Funding * Fees * Swap * FX rates * Hedge cycles * Risk events * Margin snapshots * P&L records * System events * Configuration changes * Audit logs * Emergency actions * User actions All important calculations and execution decisions must be auditable. ## Reliability and Recovery The system must recover safely from: * Application restart * Server restart * Internet failure * API timeout * Exchange disconnect * MT5 disconnect * Partial fills * Order rejection * Delayed execution reports * Duplicate execution reports * Stale market data * Incorrect or missing currency-conversion data * Broker or exchange maintenance * Database interruption After restart, it must: 1. Read actual live positions from both platforms 2. Read open orders from both platforms 3. Reconcile them with the database 4. Detect unknown or unexpected positions 5. Reconstruct the correct hedge state 6. Recalculate exposure and risk 7. Determine whether rebalancing is required 8. Resume only if all safety conditions are satisfied ## Security and Controls Implement: * Secure API-key storage * Environment-based secrets * Role-based access * Read-only and live-trading modes * Two-step confirmation for dangerous actions * IP restrictions, where supported * Complete audit logging * Rate-limit handling * Permission validation * Separate paper, demo, and live environments * Configurable maximum order size * Configurable maximum daily loss * Configurable maximum number of open positions * Configurable emergency shutdown ## Technology Preference Preferred: * Python * FastAPI * MQL5 / MT5 * REST APIs * WebSockets * PostgreSQL * Redis * Docker * Linux * React or equivalent dashboard technology The developer may propose alternative technologies if they improve reliability, execution speed, maintainability, or operational safety. ## Development Process Build in this order: 1. Generic architecture and data model 2. Instrument and contract-specification framework 3. API integrations 4. Market-data layer 5. Currency-conversion layer 6. Generic hedge calculator 7. Multi-instrument optimization engine 8. Risk engine 9. Execution engine 10. Database and audit system 11. Dashboard and configuration interface 12. Failure and recovery system 13. Paper-trading testing 14. Demo-account testing 15. Controlled live deployment 16. Documentation and handover ## Testing Requirements The system must be tested using multiple instrument configurations and must not rely on one specific asset. Testing must include: * Different contract multipliers * Different lot sizes * Different quote currencies * Different settlement currencies * Different quantity steps * Different minimum quantities * Different leverage levels * Different funding models * Different fee schedules * Different market prices * Different currency conversions * Partial fills * Rejected orders * API timeouts * Disconnections * Restart recovery * Stale prices * Large spreads * High slippage * Abnormal funding * Unexpected positions * Emergency shutdown * Rebalancing * Portfolio-level risk limits ## Important I am specifically looking for someone with experience building **real automated trading infrastructure**, quantitative trading systems, arbitrage or hedging systems, perpetual-contract systems, or broker and exchange API execution systems. I do not want a simple MT5 Expert Advisor or a basic trading bot. The final system must be **generic, configurable, rule-based, automated, auditable, scalable, and production-ready**, with no manual quantity calculations during normal operation. The system must allow me to add or modify perpetual contracts and Exness hedge instruments in the future without rewriting the core calculation engine. ## Required Proposal Information Please provide: * Relevant trading projects * Perpetual-contract experience * MT5/MQL5 experience * Python/API experience * Exchange API experience * Experience with contract specifications and quantity conversion * Experience with real-time execution * Experience with risk and liquidation calculations * Examples of multi-instrument systems * Your exact role in those projects * Proposed architecture * Estimated delivery timeline * Testing and deployment plan * Post-deployment support plan * Availability during development * Confirmation that you can commit to the required delivery schedule * Any assumptions, dependencies, or limitations * A clear breakdown of milestones and deliverables * A fixed-price or hourly estimate with expected total hours * Details of how you will validate the system before live deployment ## Delivery Expectations The project must be delivered as a working end-to-end application, not merely as disconnected source-code modules. Before final acceptance, the developer must demonstrate the complete workflow: **Live market data → hedge calculation → risk validation → order execution → position reconciliation → hedge monitoring → rebalancing or emergency handling → funding and P&L reporting.** The system must be delivered with: * Source code * Deployment configuration * Database schema and migrations * API documentation * Configuration documentation * User and operator documentation * Test results * Recovery procedures * Monitoring and alerting setup * Security documentation * Handover session * Post-deployment support terms Any developer who cannot commit sufficient time, technical expertise, and operational support to build and validate this system should not apply.