# What is AEGIS?

AEGIS is programmable infrastructure for Uniswap v4 pools. It is not a new AMM, it is not a new chain, and it is not a new pegged asset. It is a set of on-chain contracts that sit directly on top of Uniswap v4's PoolManager and add two capabilities the base AMM does not have:<br>

1. Dynamic, volatility-aware fees that adapt to real-time pool activity and compound a share of earnings into protocol-owned liquidity.
2. Pool-native credit — the ability to borrow liquidity itself, collateralized by the same pool, with no external price oracle in the solvency path.

Both capabilities are delivered as opt-in Uniswap v4 hooks and periphery contracts. Any pool that attaches an AEGIS hook inherits the behavior; pools that don't are unaffected.

### The two products

AEGIS ships as two composable modules that share a common hook, oracle, and policy surface:

AEGIS DFM — Dynamic Fee Mechanism. A Uniswap v4 hook that replaces the static fee tier with a two-component dynamic fee (a slow-moving base and a fast-moving surge) and recycles a configurable share of fees into full-range protocol-owned liquidity. DFM is the live, production-hardened layer of AEGIS.

AEGIS Engine — Pool-native liquidity and credit engine. Builds on DFM's hook and oracle foundation to offer pooled full-range liquidity deposits (sL shares), borrowable liquidity units (L), and an oracle-free solvency model based on a √K collateral floor. Engine is in active development and has not yet been audited.

You can use DFM without Engine. You cannot use Engine without DFM: Engine assumes an AEGIS-approved hook is installed on the underlying pool, and that hook is always DFM or a DFM-compatible variant.

### Built on Uniswap v4

AEGIS is not a fork of Uniswap. Every token balance, every swap, every liquidity change lives in Uniswap v4's singleton PoolManager. AEGIS contracts never custody ERC-20 tokens at rest — all token movement happens inside the PoolManager unlock frame using its ERC-6909 accounting. At the end of every transaction, AEGIS contracts hold no user ERC-20 balances.

Concretely, this means:

* You are trading and providing liquidity on Uniswap v4 pools. Routing, slippage, and composability work exactly as they do for any Uniswap v4 pool.
* AEGIS attaches to pools; it does not replace them.
* If AEGIS contracts were to be disabled, the underlying Uniswap v4 pools would continue to operate. LP value does not depend on AEGIS being "up."

### What AEGIS is not

AEGIS is often mistaken for things it is not. To be precise:<br>

* Not an issuer. AEGIS does not mint a pegged stablecoin, a wrapped asset, or a receipt token that sits on a balance sheet somewhere. sL shares represent a pro-rata claim on a specific pool's full-range liquidity, not a deposit with a third party.
* Not custodial. AEGIS does not take possession of user funds. Tokens move directly between users and Uniswap's PoolManager.
* Not an oracle-dependent lender. Engine's solvency model uses a √K floor computed from the positions themselves, not an external price feed. There is no oracle to manipulate into a liquidation cascade.
* Not a governance token farm. Participation is based on pool activity and position performance, not on buying a token.

### The shape of the rest of this documentation

This site is organized so that readers can stop reading at any point and still have a coherent mental model:<br>

* Start Here — what AEGIS is, why it exists, and which path to follow.
* AEGIS Engine — the core credit story, end to end.
* Using the Engine — role-specific guides for liquidity providers, borrowers, and integrators.
* Engine System Structure — the contracts and accounting for readers who need to verify the story.
* AEGIS DFM — the dynamic-fee layer, its mechanism, and live pool context.
* Trust, Risk & Status — risks, governance, audit status, and deployed addresses.
* Reference — ABIs, contract map, state views, and glossary.

\
If you only have five minutes, read Why AEGIS Exists next, then The Big Idea: Turning Liquidity Into Credit.