ekubo-primary-sources-2026-05-14

Ekubo primary sources

Reviewed: 2026-05-14 UTC

Core protocol framing

• https://docs.ekubo.org/
  • Best concise statement of what Ekubo thinks it is.
  • Used to confirm the protocol’s own framing around super-concentrated liquidity, singleton architecture, flash accounting, extensions, and the unusual open-source-but-Ekubo-license wording.
  • Also useful because it states the optimization target directly: highest capital efficiency at low execution cost.

Concentrated-liquidity and accounting mechanics

• https://docs.ekubo.org/integration-guides/reference/key-concepts
  • Best source for the lower-level mechanism split.
  • Used to confirm the tick size of 1.000001, one-tick-position / orderbook-like behavior, per-pool tick spacing, and the role of concentrated liquidity in capital efficiency.
  • Also used to confirm the flash-accounting model, including the docs’ explicit statement that users can withdraw from the singleton and redeposit in the same transaction without paying fees, creating a free-flash-loan-like capability.

Extension system

• https://docs.ekubo.org/integration-guides/extensions
  • Best source for why Ekubo deserves to be compared as more than a Uniswap-style AMM clone.
  • Used to confirm that pools can specify immutable extensions with lifecycle hooks before/after initialization, position updates, fee collection, and swaps.
  • Especially important because the docs explain Ekubo’s own theory of fragmentation: liquidity fragmentation is inevitable, so the singleton / till design is meant to reduce its cost to near-zero instead of forcing one monolithic AMM design.

GitHub organization overview

• https://github.com/EkuboProtocol
  • Best source for the broader implementation surface.
  • Used to confirm the org-level description of Ekubo V3 as an open-source, permissionless, ownerless AMM with concentrated liquidity, stableswap pools, and first-party extensions.
  • Also useful because it shows Ekubo as a multi-repo system with EVM contracts, Starknet contracts, router, indexer, SDK, and data tooling rather than a single-chain experiment.

Starknet governance contracts

• https://github.com/EkuboProtocol/governance
  • Best source for governance-adjacent primitives in the Ekubo ecosystem.
  • Used to confirm the existence of Starknet token-governance modules for airdrop distribution, delegation / staking, batch-call governance, and an L2-to-L1 owner proxy.
  • Important mainly as context: the repo shows that the Ekubo team publishes governance infrastructure, but the reviewed AMM docs still emphasize ownerless core contracts and immutable per-pool extension selection as the more immediate control surfaces.

Main takeaways from this pass

• Ekubo clears the bar because it is not just another Starknet DEX or generic concentrated-liquidity AMM.
• The most reusable analytical split is between concentrated-liquidity price precision, singleton flash-accounting settlement, and immutable pool-level extension logic.
• The strongest comparison angle is against Uniswap-v3/v4-style AMMs, orderbook-like one-tick quoting, and other attempts to handle liquidity fragmentation through shared infrastructure rather than through one dominant pool design.
• Ekubo is especially useful because its own docs make the fragmentation thesis explicit: extensions and custom pool logic are expected, so the architectural question becomes where routing, hook logic, and internal settlement power concentrate.