Arbitrage BOT (CEX/DEX)
A treasury-grade arbitrage engine — not a moonshot trading bot from a Telegram group.
Crypto markets are persistently inefficient. The same asset trades at meaningfully different prices on Binance, Kraken, Coinbase, Bybit and on decentralized venues like Uniswap, PancakeSwap and dYdX — sometimes for minutes, sometimes for hours. The gap is small but it compounds with volume.
BIDUA's Arbitrage Bot is an internal treasury and research project: a CCXT-based engine that monitors price differences across 20+ centralized exchanges and selected DEX liquidity pools, executes risk-managed arbitrage trades, and reports P&L in a daily ops dashboard.
This is an idea-stage initiative. Indian regulation on offshore crypto activity, TDS (1% on every VDA trade) and FEMA implications of capital movement to foreign exchanges materially shape the design. The bot would operate from an offshore entity (in a permitted jurisdiction) with all India-side exposure handled compliantly through FinWault.
Most retail arbitrage bots die because they ignore the boring stuff — withdrawal fees, slippage, KYC limits, exchange downtime. Edge in this game lives in the operations, not the algorithm.
The opportunity, on its own terms.
Spreads have widened post-2022.
As liquidity fragmented across L2s, perp DEXs and centralized venues, arbitrage opportunities became larger and more frequent — not smaller.
CCXT matured into the universal adapter.
A single library now talks to 100+ exchanges with normalized APIs. The integration cost that used to take 18 months is now 6 weeks.
Indian institutional crypto desks are scarce.
Domestic exchanges focus on retail spot. There is no serious arb-desk competition operating with INR/USDT pairs from an Indian compliance posture.
FinWault gives us the reporting backbone.
Daily NAV, treasury reconciliation, tax-ready trade logs — these are FinWault's core competencies, not commodity infrastructure.
Sized in three rings.
- Stablecoin-pair arbitrage (USDT/USDC across venues) is a low-volatility entry strategy with consistent thin spreads.
- DEX-CEX triangular arbitrage opens during volatility spikes — gas-aware execution is the moat.
- Funding-rate arbitrage on perpetual futures is a separate, persistent edge layered on top of spot arb.
- Capacity, not edge, is the binding constraint at small AUM — making this a fit for treasury, not a fund.
How it works, end to end.
Treasury operation
Phase 1 is purely BIDUA-treasury. We deploy a defined capital tranche from group reserves, the bot manages it, and net P&L flows back to treasury. No external investor capital, no fund vehicle, no marketing of returns.
Strategy stack
Three coexisting strategies — (1) spot-to-spot cross-exchange, (2) CEX-DEX triangular, (3) funding-rate / basis trades. Each runs with its own capital pocket and stop-loss limits.
Risk engine
Pre-trade: max position per venue, max gross exposure, withdrawal-fee net-of-spread checks. Live: latency monitor, exchange health pings, kill-switch on abnormal slippage. Post-trade: daily reconciliation against on-chain and exchange statements.
Compliance perimeter
Bot operates from a permitted offshore entity. INR-side flows route through FinWault with full KYC/AML. 1% TDS on Indian-side VDA transactions accounted for upstream of strategy P&L.
Phase 2 productization
If the strategy proves out for 18+ months with documented Sharpe, a managed-account offering may be considered for sophisticated accredited investors — subject entirely to SEBI/FIU and applicable regulation at that time.
Three compounding phases.
Treasury yield
- Net arbitrage P&L on $1-3M deployed
- Funding-rate carry on perp basis
- Stablecoin lending yield on idle capital
- Data feeds reused by FinWault for market analytics
Strategy refinement
- Higher AUM internal allocation (if Sharpe > 2)
- Sale of normalized market-data feeds
- License of execution engine to other treasuries
- Co-located node-as-a-service via BIDUA Hosting
Managed strategy
- Performance fee on managed accounts (if regulatorily permitted)
- Subscription to strategy intelligence dashboard
- Liquidity-provision contracts for select DEXs
- Cross-sell into FinWault wealth offering
Patient cadence, deliberate steps.
-
Q1 2027Legal entity structuring + counsel opinion on FEMA / VDA / TDS treatment for arbitrage flows.
-
Q2 2027v0 engine built on CCXT — paper-trading across 8 CEXs. Latency benchmarks established.
-
Q4 2027Live capital deployed — $250k tranche, spot-arb only. Daily ops dashboard inside FinWault admin.
-
2028DEX integration (Uniswap v4, Aerodrome, dYdX). Triangular and funding-rate strategies live.
-
2029Capital scaled subject to documented risk-adjusted return. Co-location at AWS Tokyo / Singapore for latency.
-
2030Decision point: stay internal-treasury, or productize for accredited investors under prevailing regulation.
Who else is here — and why we're different.
- Built and operated by a multi-sector holding group, not a venture-funded prop shop — patient capital, low burn pressure.
- FinWault provides built-in reconciliation, tax-treatment and audit-grade reporting from day one.
- BIDUA Hosting can provide co-located, low-latency infrastructure at internal cost.
- Compliance-first posture means the project can mature into a regulated product when the policy door opens.
What can go wrong — and how we plan for it.
Regulatory tightening (India)
Mitigation: Offshore entity structure with clean FEMA documentation. Continuous engagement with counsel. Ability to wind down within 30 days.
Exchange counterparty failure (FTX-style)
Mitigation: Max 10% of deployed capital on any single venue. Daily withdrawals to cold wallet above thresholds. Exclude exchanges below defined transparency standards.
Spread compression as market matures
Mitigation: Strategy diversification across spot / triangular / funding-rate. Capacity-limited so we don't chase scale into worse spreads.
Smart-contract / DEX exploit on the bot's positions
Mitigation: Limited DEX exposure to audited, top-5 TVL protocols. Position caps per protocol. Monitoring of governance / upgrade events.
Operational error (bad code, fat finger)
Mitigation: Staged deploys with shadow-trading parallel. Hard position and loss limits at infra layer, not just app layer. Daily SRE review.
Connected BIDUA divisions.
Every BIDUA bet feeds something else in the group. This one connects to:
Live
FinWault
Provides treasury reconciliation, NAV reporting and the regulatory wrapper any productized version would sit inside.
finwault.com
Live
BIDUA Hosting
Low-latency colocation and dedicated bare-metal nodes for execution infrastructure.
biduahosting.com
Live
PersistIP
Network engineering capability for cross-region latency optimization and resilient connectivity.
ip.bidua.in
Questions partners and investors actually ask.
Can I invest in the bot's returns?
No. Phase 1 is purely BIDUA's internal treasury. Any future managed offering would require explicit regulatory clearance and would only be available to accredited investors — and we will say so loudly if and when that happens.
What's the expected return?
Arbitrage at this scale historically targets 8-20% annualized with low correlation to spot — but past performance proves nothing, and we will not publish numbers until at least 12 months of audited live trading exists.
Why CCXT specifically?
CCXT abstracts 100+ exchange APIs into one normalized interface. It is battle-tested, open-source, and the de-facto standard for multi-venue execution. Building bespoke connectors per exchange is wasted effort.
How do you handle Indian tax (1% TDS)?
Indian-side flows are routed through FinWault with TDS deducted and reported. Offshore trading happens in the offshore entity. Counsel signs off on the structure before any capital moves.
What happens if an exchange freezes withdrawals?
Per-venue exposure caps mean a single exchange freeze is a contained loss, not a catastrophic one. The strategy assumes counterparty events will happen and sizes around them.
Are you using AI / ML?
ML is used for slippage prediction and venue-health scoring, not for return generation. The core edge is structural (price difference exists) — not predictive.
Why operate from offshore?
Indian regulation currently prohibits or restricts several activities the bot must perform (operating accounts on offshore venues at scale). The offshore entity is a compliance choice, not a tax dodge — all India-side income flows are reported.
Could this become a fund someday?
Only if (a) Indian regulation creates a clear category for it, (b) the strategy has 18+ months of audited Sharpe > 2, and (c) BIDUA's board chooses to take that route. None of those are assumed.
Building treasury infrastructure, not selling signals.
BIDUA does not sell arbitrage subscriptions, signals or 'guaranteed returns'. If you operate a treasury or institutional desk and want to talk shop on CCXT execution architecture, we are open to peer conversations.