Trading Bot Integration with SushiSwap SDK: Code, Setup, Monitoring

A trading bot that makes direct SushiSwap contract calls instead of using the SDK can lose up to 30% of routes. The difference is that the SDK automatically provides current router addresses across 30+ chains and builds routes through v3 pools that legacy code simply ignores. In our practice, we often encounter projects where integration bypasses the SDK, resulting in lost liquidity and reduced profits. One client with an arbitrage bot on Arbitrum increased successful routes by 24% and cut gas costs by 18% after switching to @sushiswap/router, thanks to dynamic gas pricing.

We are a team with many years of experience in blockchain development. Over that time, we have completed over 40 trading bot integrations on SushiSwap and other DEXs. In this article, we share key aspects to consider when connecting a bot to the SushiSwap SDK.

Which version of SushiSwap SDK to choose for a trading bot?

SushiSwap SDK v3 (@sushiswap/sdk) and the newer @sushiswap/router are different packages with different APIs. @sushiswap/router is the current standard, supporting SushiSwap v3 (concentrated liquidity), v2, and routing through multiple protocols simultaneously. The old @sushiswap/sdk only works with v2 pools—it's outdated for most tasks. We've seen bots that ran on the old SDK for years, unaware they lost 20-30% of routes due to missing v3 pools.

Why passing an accurate gasPrice is critical for net profit?

import { Router } from '@sushiswap/router'
import { ChainId } from '@sushiswap/chain'

const trade = await Router.getBestRoute({
  chainId: ChainId.ARBITRUM,
  fromToken: WETH,
  toToken: USDC,
  amount: parseUnits('1', 18),
  gasPrice: await provider.getGasPrice(),
})

getBestRoute returns the optimal route considering gas. If a zero or stale gasPrice is passed, the route is optimized only by output token amount, ignoring net profit. The formula for a trading bot is: netProfit = outputAmount - inputAmount - gasCost. The gasPrice should be fetched from the mempool, not cached. In one project, we reduced gas costs by 18% after implementing dynamic gas pricing.

How does monitoring pools via The Graph help a bot?

SushiSwap has subgraphs for each chain. For a bot monitoring liquidity events or tracking price changes, queries through The Graph are more efficient than direct on-chain calls. However, The Graph has a delay of a few seconds, so for real-time, WebSocket subscriptions to Sync (v2) or Swap (v3) events via ethers.js are better. Comparison of methods:

Risks of using an outdated SDK version?

The old @sushiswap/sdk does not support v3 routes, leading to a loss of 20-30% of available liquidity. Additionally, it may not support new chains or EIPs, causing transaction errors. For example, after the transition to EIP-1559, code without an SDK update cannot correctly set maxPriorityFeePerGas, causing transactions to stall. Regularly update the SDK to the latest version—the SushiSwap team adds support for new networks and fixes bugs.

Multi-chain configuration

The SDK automatically resolves contract addresses by chainId, but for custom configurations (own node, custom RPC), you must pass the providers map explicitly:

import { providers } from 'ethers'

const providerMap = {
  [ChainId.ETHEREUM]: new providers.JsonRpcProvider(ETH_RPC),
  [ChainId.ARBITRUM]: new providers.JsonRpcProvider(ARB_RPC),
  [ChainId.POLYGON]: new providers.JsonRpcProvider(POLY_RPC),
}

Using public RPCs (Infura, Alchemy free tier) leads to rate limiting under intensive monitoring. For a production bot, we recommend a private node or a paid tier with guaranteed throughput.

Executing the swap via the router

The SushiSwap v3 router on Arbitrum is 0x...RouteProcessor3. The SDK generates calldata for processRoute() automatically:

const { routeProcessorAddr, routeCode } = trade
const tx = await routeProcessor.processRoute(
  fromToken.address,
  amountIn,
  toToken.address,
  minAmountOut,  // amountOut * (1 - slippage)
  recipient,
  routeCode,
)

minAmountOut is protection against slippage. For an arbitrage bot, slippage tolerance should be minimal (0.1-0.3%), otherwise the transaction could execute at a loss if the market moves between simulation and block inclusion.

What our work includes

1. Analysis of the current bot architecture and trading strategy.
2. Designing routing accounting for multi-chain and multi-version.
3. Writing code using @sushiswap/router, configuring RPC, gas management.
4. Testing on testnet with simulated peak loads.
5. Deployment to mainnet with gradual volume increase.
6. Monitoring and alerting—integration with Tenderly or a custom backend.
7. Configuration and operations documentation.
8. Support for one month after launch.

Timeline estimates

Integration of a trading bot with SushiSwap SDK takes 3–5 days for a single chain. A multi-chain system with routing through multiple protocol versions and pool monitoring takes up to one week. Includes testnet testing and documentation. Contact us for a project assessment—we will prepare a commercial proposal considering your strategy. Get a consultation to learn how to optimize your bot for the current architecture.

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.

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

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.