Developing a Cash-and-Carry Arbitrage Algorithm for Crypto

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
Developing a Cash-and-Carry Arbitrage Algorithm for Crypto
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
    1361
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1251
  • image_websites_belfingroup_462_0.webp
    Website development for BELFINGROUP
    957
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1189
  • image_logo-advance_0.webp
    B2B Advance company logo design
    646
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    929

Developing a Cash-and-Carry Arbitrage Algorithm

The basis between spot and perpetual futures on liquid crypto pairs consistently yields 10–20% annually — provided you precisely manage funding rate, fees, and liquidation risks. The strategy sounds simple: buy spot, short futures, collect the spread. But in practice, hidden costs and liquidity anomalies kill profitability if not built into the algorithm. We specialize in precisely such algorithms — with detailed consideration of expiry, margin buffer, and cross-exchange collateral.

How the Basis Works and Where Yield Comes From

Cash-and-carry exploits the divergence between the spot price of an asset and the futures or perpetual price. For dated futures, the basis is defined by the cost of carry formula:

F = S × e^(r-q)×T

where S is the spot price, r is the risk-free rate, q is the asset yield, and T is time to expiry. In crypto, the risk-free rate is historically higher than in traditional assets, so futures trade in contango (F > S) most of the time.

For perpetual futures, the basis is maintained through the funding rate: when the perpetual trades above spot, longs pay shorts every 8 hours (on Binance). The funding rate amount is a direct source of yield for the trader holding a long spot + short perp position. More on the cost of carry model can be found in the Wikipedia article.

Non-Obvious Risks in Cash-and-Carry Arbitrage

Funding rate reversal. The funding rate can turn negative. In a bear market or during a sharp increase in short open interest, shorts start paying longs. The strategy turns from profitable to losing. The algorithm must track funding rate dynamics and close the position when it falls below a threshold (accounting for fees and slippage on close).

Liquidation asymmetry. A short on futures theoretically has unlimited loss, a long spot is limited to zero. During a sharp price increase (30% in an hour, as in some altcoin events), margin on the short futures may be insufficient, even if the long spot is in profit. The strategy is technically delta-neutral but requires a sufficient margin buffer. Rule: margin on short ≥ 2× the maximum historical daily move of the asset.

Exchange counterparty risk. Holding both spot and futures on the same exchange carries the risk of a freeze (FTX case). This can be neutralized via a cross-exchange strategy: spot on one exchange (or DeFi), futures on another. However, this adds complexity to collateral management.

Basis divergence at expiry. For dated futures, theory says F → S at expiry. In practice, 1–2 days before expiry the basis can widen due to demand imbalances — especially in altcoins with low liquidity. The algorithm must account for the optimal exit time.

Why the Algorithm Must Track Funding Rate

The funding rate is the main driver of yield. Even with stable contango, a negative rate over several periods can wipe out all profit. The algorithm monitors the predicted funding rate in real time (available 8 hours ahead) and compares it to a threshold, accounting for opening/closing fees. If the expected net yield falls below the minimum — the system automatically exits the position.

Algorithm Architecture

System Components

Data aggregator. Collects in real time:

  • Spot prices from multiple sources (Binance spot, Coinbase, Kraken) to avoid manipulation
  • Futures/perp prices and open interest
  • Current and predicted funding rate (Binance publishes predicted funding rate 8 hours ahead)
  • Historical funding rate data for rolling annualized yield calculation

Basis calculator. Normalizes data and calculates:

  • Current basis in % and annualized form
  • Estimated yield accounting for entry/exit fees, funding payments
  • Break-even holding period

Position manager. Opens and closes positions based on signals from the basis calculator. Ensures delta-neutrality: size of long spot = notional value of short futures.

Risk monitor. Continuously tracks margin ratio on futures position, funding rate trend, basis anomalies. If conditions are violated — automated exit.

Net Yield Calculation

Real strategy profit after all costs:

Net APY = Funding Rate (annualized)
        - Trading fees (entry + exit, both legs)
        - Slippage (bid-ask spread × 2)
        - Borrowing cost (if using margin)
        - Opportunity cost on margin collateral
Parameter Example for BTC DeFi version
Funding rate (APY) 10.95% 8.4% (average)
Trading fees 0.16% 0.5–1% (gas)
Slippage 0.06% 0.1–0.3%
Net yield ≈10.7% APY ≈7–8% APY

Example calculation for BTC cash-and-carry on Binance (real data):

  • Funding rate: 0.01% every 8h = 10.95% APY
  • Taker fees: 0.04% × 4 operations = 0.16% round trip
  • Slippage: ~0.03% × 2 = 0.06%
  • Net yield ≈ 10.73% APY before tax

When funding rate is 0.03% (common in a bullish market), net yield rises to 30%+ APY.

Rollover of Dated Futures

When working with quarterly/monthly futures, a rollover algorithm is needed: close the expiring contract and open the next one. Optimal rollover time is 3–5 days before expiry, when the basis of the next contract has normalized but liquidity of the current one is still sufficient.

Automatic rollover accounts for:

  • Basis difference between current and next contract (if the next is in greater contango — rollover is profitable, if less — it's a cost)
  • Current liquidity of both contracts
  • Spread on both contracts simultaneously (risk: basis may shift while closing the first contract)

To minimize the latter risk, we use TWAP execution: close current and open new contract in parallel with small orders.

On-Chain Implementation: DeFi Version of the Strategy

In DeFi markets, cash-and-carry can be implemented via:

  • Pendle Finance. The protocol splits yield-bearing tokens into Principal Token (PT) and Yield Token (YT). Buying PT at a discount to par plus hedging through Pendle AMM is analogous to cash-and-carry with fixed yield to maturity.
  • Perp on dYdX / GMX v2 / Synthetix Perps. Long spot via Aave/Compound (staked ETH or cbETH) + short ETH perp on dYdX. The spot position earns staking yield (~4% APY), short collects funding rate.

The on-chain version adds gas costs and oracle risk but removes exchange counterparty risk. The exchange version is 10× faster in execution than DeFi but requires trust in a centralized platform.

Comparison of CEX and DEX versions
Characteristic CEX (Binance) DEX (dYdX)
Execution Instant Delayed due to gas
Fees 0.04% taker 0.1-0.5% + gas
Counterparty risk Present None (non-custodial)
Available pairs 200+ 20-30

Development Process

  1. Analytics (3–5 days). Backtesting on historical data: Binance historical funding rates available via API for 2+ years. Model strategy under different market conditions, determine entry/exit thresholds.
  2. Core development (1–2 weeks). Data aggregator, basis calculator, position manager. Connect to exchange APIs (CCXT as universal library or direct WebSocket connections for latency).
  3. Risk management and monitoring (1 week). Automated exit when funding rate < threshold, margin call protection, Telegram alerts.
  4. Paper trading (3–5 days). Run without real money on production data. Verify calculations, latency, edge cases.
  5. Deploy. Test with small amounts, gradually increase positions.

What's Included

  • Data collection and basis calculation algorithm
  • Position management module with delta-neutrality
  • Risk monitor with automatic exit on condition violations
  • Documentation and architectural diagram
  • Deployment on your server or cloud
  • 1 month of post-deployment support

Time Estimates

An algorithm for one pair on one exchange with basic risk management — 2–3 weeks. Multi-asset, multi-exchange strategy with automatic rollover — 4–8 weeks. DeFi version via on-chain protocols — additional 2–3 weeks. Cost is calculated individually.

We have developed over 15 algorithms for crypto arbitrage, 5 years on the market. Experience with Ethereum since 2017. To discuss your strategy, leave a request — we will select the optimal architecture. Get a consultation on choosing a solution for your project.

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.