Cowrie Research

ekubo

3 min read

Ekubo

  • Name: Ekubo
  • URL: https://ekubo.org/
  • Category: AMM infrastructure / concentrated-liquidity DEX / singleton-and-extension market-making protocol
  • Tags: ethereum-ecosystem
  • Summary: Ekubo is not just another Starknet DEX. It is a singleton concentrated-liquidity core that makes fragmentation cheap instead of pretending to remove it. The interesting control surface is not only the AMM math but which immutable pool extension and routing pattern captures flow.
  • What it does:
    • Provides an AMM core with concentrated liquidity, per-pool tick spacing, and constant-product trading inside regions of constant liquidity
    • Uses a singleton architecture with flash accounting so multi-hop swaps, arbitrage, and position updates can net internally before final token transfers
    • Allows pool-specific extensions to run custom logic before and after initialization, swaps, fee collection, and position updates
    • Supports very fine-grained pricing, with docs describing a 1.000001 tick size and one-tick positions that can behave similarly to onchain limit orders
    • Exposes separate pool state per extension, so custom logic does not commingle capital across other pools
    • Ships both Starknet and EVM contract implementations plus router, indexer, and SDK repositories through the EkuboProtocol GitHub org
  • Key claims:
    • The docs introduction describes Ekubo as AMM infrastructure with super-concentrated liquidity, a singleton architecture with flash accounting, and extensions, and says the contracts are optimized for capital efficiency and low-cost execution.
    • The key-concepts docs make the pricing granularity unusually explicit: Ekubo uses a tick size of 1.000001, which it says is 1/100th of a basis point and smaller than most centralized limit order books. That matters because it makes AMM versus orderbook less binary than usual.
    • The same docs treat flash accounting as a major design distinction. Internal balance accounting means users or arbitrageurs can compose many swaps and position updates and only settle token differences at the end, with the docs explicitly noting fee-free flash-loan-like withdrawal and redeposit inside one transaction.
    • The extensions docs expose the clearest reusable control surface. Ekubo lets each pool specify immutable extension logic that can run at eight lifecycle call points and can re-enter the core contract to perform additional swaps or updates. That makes Ekubo useful for comparing hook-like customization, oracle construction, custom order types, privacy wrappers, and routing policy without assuming every feature requires a separate AMM deployment.
    • Ekubo’s own rationale is analytically important: the docs say liquidity fragmentation is inevitable, so the goal is to reduce its cost to near-zero through singleton design and the till / flash-accounting pattern. That is a sharper comparison point than filing Ekubo as merely a Starknet DEX.
    • The GitHub org frames Ekubo V3 as open-source, permissionless, and ownerless AMM infrastructure with first-party extensions and highly optimized contracts on both EVM and Starknet, which suggests the relevant product surface is broader than one frontend or one chain deployment.
    • The EkuboProtocol governance repository is also useful context. It publishes Starknet token-governance primitives such as an airdrop contract, delegation / staking contract, governor, and L1-owner proxy, but the reviewed AMM materials themselves emphasize immutable pool configuration and ownerless core behavior more than an actively managed protocol governor.

Internal linkages

Graph View

Backlinks