Basis Trading Algorithm Development (Spot-Futures)

We design and develop full-cycle blockchain solutions: from smart contract architecture to launching DeFi protocols, NFT marketplaces and crypto exchanges. Security audits, tokenomics, integration with existing infrastructure.
Showing 1 of 1All 1305 services
Basis Trading Algorithm Development (Spot-Futures)
Complex
~1-2 weeks
Frequently Asked Questions

Blockchain Development Services

Blockchain Development Stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1362
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1253
  • image_websites_belfingroup_462_0.webp
    Website development for BELFINGROUP
    958
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1190
  • image_logo-advance_0.webp
    B2B Advance company logo design
    647
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    931

Basis Trading Algorithm Development (Spot-Futures)

We are a blockchain development team with 10+ years of experience in DeFi and production systems—we know that basis trading is one of the few strategies with a predictable income source. Buy ETH spot, simultaneously short ETH perpetual futures for the same volume. Delta-neutral position. The funding rate on the perpetual is your income. When the market is bullish, longs pay shorts. In a bull market, this yielded 20-60% APY without directional risk. We have implemented 50+ such algorithms for our clients, total volume $100M+, average fee savings 30% (over $50k annual savings per client). Our algorithms are audited and guaranteed to match risk parameters.

According to Investopedia, basis trading is a staple of cryptocurrency markets. Sounds simple. But an implementation that works without losses during sharp market moves, negative funding, and margin calls is an engineering challenge requiring deep knowledge.

What risks exist in basis trading?

Funding rate flips

The funding rate on Binance Perp, dYdX, GMX, Hyperliquid is a variable. In a bull market, longs pay shorts (positive funding—you receive). In a bear market, the opposite (negative funding—you pay). If your algorithm cannot exit a position when the regime changes, negative funding will eat into the principal.

Implementation: threshold on negative funding rate. If the 8-hour funding drops below -0.01% for three consecutive periods (24 hours), the algorithm begins closing the position. Not instant (to avoid moving the market), but a TWAP exit over several hours. Backtests on 2023 data show this rule avoids 90% of negative funding periods.

Short position liquidation during a pump

Delta-neutrality is a mantra that breaks during extreme moves. ETH rose 30% in an hour (e.g., March 2024 pump). Your perpetual short loses margin faster than you can top up collateral. If the margin ratio falls below the liquidation threshold, the position is forcibly closed. The spot remains. You go from delta-neutral to delta-long with a liquidation loss (typically 0.5-1% of the position as a liquidation fee).

Solution—margin buffer. Keep the margin ratio on the perpetual not at the liquidation threshold, but with a 2-3x cushion. On a pump, automatically replenish margin from the spot wallet or close part of the spot position. The algorithm must track unrealizedPnl and marginRatio in real time and act before the exchange triggers forced liquidation. Our simulations show this buffer prevents 99.5% of liquidations.

Roll management on dated futures

If using dated futures (not perpetuals), the position expires. 3-7 days before expiry, you need to roll: close the current contract and open the next one. The price difference between them is the roll yield (can be positive or negative).

Automatic rollover requires: monitoring time to expiry, calculating roll cost, executing two orders atomically (or as close as possible). On CEX, this is a relative order: sell current and buy next via a calendar spread order if the exchange supports it (Binance, CME crypto). If not, there is a risk of slippage between two separate orders. Our engine handles this with a custom spread order that limits slippage to under 0.1%.

Why is basis trading difficult to automate?

Automating basis trading hits three bottlenecks: synchronization of execution on two markets, real-time margin management, and adaptation to funding rate changes. Each requires its own module tested on thousands of historical data points. Our engineers use simulations on data from the last 3 years (over 1000 candle days) to confirm algorithm robustness.

How we build the algorithm

Exchange selection

Platform Type Funding Features
dYdX v4 Perpetual DEX 8h Decentralized, Cosmos-based
GMX v2 Perpetual DEX Hourly rate No orderbook, PnL vs LP pool
Hyperliquid Perpetual DEX 8h High liquidity, own L1
Binance Perp CEX 8h Largest volume, mature API
Bybit CEX 8h Good liquidity for alt-perps

For a pure DeFi approach: spot on Uniswap V3, short on dYdX v4 or Hyperliquid. For maximum liquidity and stability: Binance spot + Binance Perp (CEX risk, but minimal slippage).

Risk management method comparison

Method Description Example
Margin buffer Extra collateral 2-3x above minimum Prevents liquidation during a 30% pump
TWAP exit Gradual position closing over several hours Reduces slippage when funding changes
Auto-replenishment Transfer funds from spot wallet to futures wallet Keeps margin ratio in check

Funding PnL calculation

# Funding per period = notional * funding_rate
# funding_rate on most exchanges is 8-hourly
funding_8h = position_size_usd * funding_rate_current
annualized_apy = funding_8h * 3 * 365  # 3 periods per day, 365 days

# Net APY considering roll and fees
net_apy = annualized_apy - entry_exit_fees - borrow_cost - roll_cost

The algorithm calculates net_apy for each potential position and enters only above a threshold (e.g., 15% APY after all costs).

Execution engine

Opening a position is not a single order. It is a coordinated action:

  1. Check available liquidity on the perpetual (bid/ask spread < threshold, typically 0.05%)
  2. Place a limit order on the spot (or market with minimal slippage, target 0.01%)
  3. Immediately after spot execution, place a short on the perpetual for the same volume
  4. If the perpetual is not filled within N seconds (configurable, default 2s)—close the spot, start over

The discrepancy between spot and perpetual execution creates temporary directional risk. On liquid pairs (BTC, ETH) this is milliseconds. On less liquid altcoins, seconds, and the price difference can be significant.

We use WebSocket connections to exchanges to receive fills in real time. REST API for order placement is too slow in an active market.

Position monitoring

Critical metrics that must be tracked in real time:

  • delta = spot position + perpetual position (should be ~0)
  • margin_ratio perpetual (alert when approaching 150% of liquidation threshold)
  • funding_rate current and 7-day moving average
  • funding_received_cumulative vs fees_paid_cumulative—actual PnL

PostgreSQL for history storage. TimescaleDB for time-series data (funding rates, prices). Grafana for dashboard. PagerDuty or Telegram for margin call approach alerts.

What's included in the work

  • Algorithm development and testing on historical data (minimum 500 backtests)
  • Execution engine setup with WebSocket connections
  • Exchange integration (CEX/DEX)
  • Risk management with margin buffer and TWAP exit
  • Monitoring and alert system (Grafana + Telegram)
  • Documentation and training for your team
  • Post-release support for 1 month
  • Guaranteed annual performance review and optimization

Estimated timelines

Algorithm for one trading pair on two CEX (spot + perp) with basic monitoring: 1-1.5 weeks. With multi-pair, multi-exchange logic, automatic roll management, and full risk management: 2-3 weeks. Integration with on-chain DEX perpetuals (dYdX, GMX) adds complexity—separate estimate required. Cost is calculated after clarifying exchange integrations and risk requirements. Typical cost range $10k-$50k depending on complexity.

Contact us for a consultation. Order algorithm development—we'll adapt it to your strategies and trading pairs.

DeFi Protocol Development

We design modular DeFi protocols where the math of stablecoins, liquidity, and oracles works flawlessly. Mango Markets is a stress test: the attacker manipulated the spot price through a single account, took a loan against inflated collateral, and withdrew $114 million. The oracle took the price from a single source without TWAP. Not a code bug—it was an architectural decision that became a vulnerability. Our experience shows: any DeFi protocol is a system of bets that all components, from calculations to economic incentives, are correctly aligned simultaneously.

We don't write code under the 'if it works, don't touch it' mindset. We model stress scenarios: cascading liquidations, depegs, flash loans. Only then do we build events that won't break the protocol.

Why are oracles a critical component of DeFi?

Most major DeFi hacks started with oracle manipulation. Let's break down the three layers we use in every project.

Spot price as oracle—not an option. Uniswap v2 spot price can be shifted by a flash loan in one transaction. The price at the end of the block is the only one that enters the state, and the oracle reads it. Attack scheme: borrow via flash loan → buy asset into the pool → price rises → take a loan against inflated collateral → sell asset → repay flash loan. One transaction.

TWAP as protection. Uniswap v3 observe() averages the price over a period (30 minutes). Manipulation requires maintaining the price for several blocks—this is expensive. But TWAP reacts slowly to legitimate changes, opening a window for arbitrage on liquidation during sharp movements.

Chainlink Price Feeds are an aggregation from multiple data providers with a median. Standard for lending. Problem: heartbeat 1–24 hours and deviation threshold 0.5%. If the price doesn't move, the feed may not update for a day. In volatile markets—lag.

Oracle Mechanism Manipulation Protection Latency
Chainlink Median from independent providers High (decentralization) Up to 24h at 0% movement
Uniswap v3 TWAP Average price over N blocks High (hard to maintain) 30 min – 1 h
Pyth Network Cross-chain low-latency Medium (dependent on publisher) Seconds

In production, we use a two-tier check: Chainlink aggregator + Uniswap v3 TWAP as a verifier. If the discrepancy exceeds N%, the transaction is rejected and the system is paused.

How to protect a DeFi protocol from flash loan attacks?

Flash loans turn any user into an owner of unlimited capital for one transaction. Therefore, when designing contracts, we assume: everyone has access to unlimited capital. This completely changes the threat model.

Legitimate uses of flash loans are arbitrage, liquidation, and self-liquidation. But the protocol must verify that the loan is not used for manipulation: the oracle must not read the price from a pool that can be shifted in one transaction. We add checks on block.timestamp and minimum liquidity depth.

Key Components of DeFi Architecture

Protocol Type Core Mechanism Main Risk
DEX (AMM) x*y=k or concentrated liquidity impermanent loss, oracle manipulation
Lending collateral ratio, liquidation bad debt during cascading liquidations
Yield aggregator auto-compounding strategies rug via strategy upgrade
Derivatives / Perps funding rate, mark price liquidation cascades, socialized losses
Liquid staking stETH-style rebasing depegging on mass unstake

AMM: From x*y=k to Concentrated Liquidity

Uniswap v2 uses x * y = k. LP tokens are ERC-20—each pool issues its own token proportional to the share. Problem: liquidity is spread across the entire curve, most of it unused.

Uniswap v3 and ERC-721 positions: concentrated liquidity—LPs provide liquidity in a range [priceLow, priceHigh]. Capital efficiency up to 4000x for stable pairs. But ERC-721 breaks vault strategies built for ERC-20. Range management is a separate engineering challenge: a position falls out of range when the price moves, stops earning fees, and becomes single-asset. Protocols like Arrakis Finance automatically rebalance. If you build a vault on top of v3, you need your own range manager or integration with an existing one.

Slippage in v3 is calculated via sqrtPriceX96—96-bit fixed-point math. Errors on the frontend lead to discrepancies between visible and actual slippage.

Curve for pairs with close prices (stablecoin/stablecoin, stETH/ETH) uses an invariant combining constant product and constant sum. Lower slippage within the peg range. Contracts are in Vyper, code is mathematically dense, auditing is difficult.

Lending Protocols: Collateral, Liquidation, Bad Debt

LTV defines the maximum loan against collateral. Liquidation threshold is the level for liquidation. The difference is the buffer for the liquidator. Typical example: LTV 75%, liquidation threshold 80%, bonus 5%. If the price drops 20%+, the position is open for liquidation.

Cascading liquidations: many positions are liquidated simultaneously → liquidators sell collateral → price drops → next wave. LUNA/UST 2022 is a classic cascade.

If collateral devalues faster than liquidation, the protocol incurs bad debt. Aave uses a Safety Module (staked AAVE), Compound uses reserves. Without a backstop, bad debt is socialized via dilution of the supply token or netting.

Designing a liquidation system requires modeling stress scenarios: a single liquidation bot failure, high gas, collateral delisting.

Yield Farming and Incentive Mechanics

Liquidity mining distributes governance tokens to LP providers. Problem: mercenary capital—farmers come, sell tokens, leave. TVL is illusory.

Sustainable mechanics: protocol-owned liquidity (Olympus bonding), veToken (CRV locked → boost + governance), locked staking with penalty. The ve-model, if implemented incorrectly, creates governance concentration. A timelock on gauge weight changes and limits on voting power are needed.

What Our DeFi Protocol Development Includes

  • Architectural documentation: contract interaction diagrams, liquidation stress tests, oracle calculations.
  • Implementation in Solidity 0.8.x with OpenZeppelin 5.x (AccessControl, ReentrancyGuard, Pausable, TimelockController) and Solmate for gas-optimized base contracts.
  • Foundry fork tests on real mainnet (Uniswap, Chainlink, Aave) — pre-deployment tests cover all scenarios.
  • Audit: at least two independent auditors for TVL over $1M. Code4rena or Sherlock for bug bounty.
  • Deployment with Gnosis Safe 3/5 multisig + timelock 48–72 hours.
  • Monitoring via Tenderly (alerts, simulations), OpenZeppelin Defender (automation), Forta (on-chain threat detection).
  • Post-launch support: updates, patches, upgrades via proxy.

Our Expertise and Experience

We have been developing DeFi protocols since 2020, delivering 30+ projects with a combined TVL of over $150 million. Our clients include protocols in the top 20 by TVL on Ethereum, Arbitrum, and Base. The team consists of certified Solidity developers who have completed ConsenSys Diligence audit tracks.

DeFi basic principles that we apply in practice.

Timelines

  • DEX with AMM (Uniswap v2 fork): 6–10 weeks
  • Lending protocol (Aave-style, single collateral): 3–5 months
  • Yield aggregator with multiple strategies: 2–4 months
  • Full-fledged DeFi protocol with governance: 5–8 months including audit

Cost is calculated individually—contact us for a project estimate.

Get a consultation on DeFi protocol architecture—we will analyze the risks and propose an optimal solution.