Mirroring Binance trades to sub-accounts with under 2ms latency

What problem does this solve?

Retail traders managing multiple accounts or mirroring trades to client sub-accounts face a serious problem: latency. Standard copy trading systems run on slow, centralized platforms that introduce 500ms to 2s of delay. In crypto, where order books move in milliseconds, a 1-second delay turns a profitable limit order execution into a ruinous slippage loss.

Furthermore, native exchange copy trading features are highly restrictive. They prevent limit order replication, custom order scaling, or cross-exchange mirroring (e.g., duplicating Binance trades directly to Bybit or OKX).

How it works

DECODED operates directly at the API protocol layer, bypassing traditional browser automation to guarantee ultra-low latency executions.

• Rust tokio Event Loop: The replication engine uses high-performance async Rust. It connects to the master account's private WebSocket order stream to receive real-time order fill updates.
• Concurrent Execution: When a fill event occurs, Rust spawned tasks duplicate the order parameters (size, price, side) and send them to the target sub-account REST APIs concurrently.
• 100ms Reconciliation: Every 100ms, the system reconciles position states between master and follower accounts to correct any execution drift.

Trade-offs and Limitations

Building a secure API copier requires trade-offs. The most critical is access control:

Replicating trades requires write access to your accounts. To mitigate security risks, you should never enable withdrawal permissions on your API keys. Decoded will reject any connected API key that has withdrawal permissions enabled.

Additionally, fast replication can trigger exchange rate limits. Decoded uses intelligent request batching to prevent API bans.