EulerSwap primary sources
Last reviewed: 2026-05-11 UTC
What this file is
A compact source map for the EulerSwap pass. I used official Euler docs plus the official repository README. The repo README also points to a dedicated EulerSwap white paper PDF in docs/whitepaper/EulerSwap_White_Paper.pdf, but this pass focused on the readily accessible official docs and repository materials.
Primary sources reviewed
- Official overview: https://docs.euler.finance/concepts/advanced/euler-swap/
- Developer docs landing page: https://docs.euler.finance/developers/euler-swap/
- How it works: https://docs.euler.finance/developers/euler-swap/how-it-works/
- User guide: https://docs.euler.finance/user-guide/euler-swap/
- Official repo README: https://raw.githubusercontent.com/euler-xyz/euler-swap/master/README.md
- Repository: https://github.com/euler-xyz/euler-swap
- Maglev repo: https://github.com/euler-xyz/euler-maglev
Notes pulled forward
- Official docs describe EulerSwap as a DEX integrated directly with Euler lending infrastructure and compatible with Uniswap v4 hooks.
- The key mechanism is that liquidity stays in Euler vaults, where it can keep earning lending yield and serve as collateral, while swaps borrow output inventory just in time.
- The docs emphasize a single-owner pool model rather than pooled LP ownership. That makes individual operator strategy and maintenance a first-class control surface.
- The README adds two analytically useful details: a registry layer with optional validity bonds, and the fact that abandoned pools can keep existing onchain while becoming non-operational once the underlying lending position is withdrawn.
- The docs repeatedly frame shared-liquidity reuse across multiple pairs as a main source of capital efficiency, which is the strongest reason to keep EulerSwap separate from a generic
Eulerentry.
Why it matters
EulerSwap exposes a distinct comparison layer between AMMs and lending markets. It is not just Euler with swaps; it turns vault liquidity, borrow limits, operator installation, registry policy, and hook-compatible routing into one AMM control plane.