Skip to main content

Angstrom L2 Architecture

Angstrom’s L2 deployment compresses the entire sequencing and MEV capture pipeline into two on-chain pieces: a factory that mints Uniswap v4 pools with the Angstrom hook attached, and the hook itself, which internalizes MEV directly inside the swap callbacks. Everything else—auctions, rewards, unlock controls—happens in that on-chain loop; there are no external coordinators or bespoke mempools to run.

Factory-Guided Deployment​

AngstromL2Factory is the entry point for spinning up markets. It lets anyone permissionlessly deploy an Angstrom hook, initialize the underlying Uni V4 pool, and configure fee splits while keeping protocol-wide limits in place. The factory also exposes read helpers so routers can discover the canonical tax parameters before they quote trades. For bytecode, permission, and admin details, see the factory contract specification.

In practice, integrating teams call the factory to:

  • deploy a verified hook instance together with the desired pool,
  • configure creator/protocol swap and tax fee splits, and
  • fetch the default MEV tax schedule their routers must budget for.

Hook-Led Execution​

Once a pool is live, the hook wraps every swap with two callbacks:

  • beforeSwap measures the transaction’s priority fee, records the deterministic MEV tax as a balance the caller must settle later, and snapshots the pool state required for compensation math.
  • afterSwap splits that recorded tax (and the standard swap fee) between protocol, pool creator, and LPs, crediting each share and running the compensation solver to fairly distribute the MEV tax to Lps.

The core swap path stays identical to vanilla v4—routers simply have an extra native-token delta to clear when they call settle. For a step-by-step walkthrough, see the hook contract docs and the swap flow guide.

Chain & Integration Requirements​

  • Native-token denomination. Pools must treat the native asset as currency0 so the hook can account for and settle the tax in the same currency the sequencer prices.
  • Router budgeting. Integrations need to pre-fund the MEV tax with the swap. Use the factory getters or on-chain helpers (e.g., getSwapTaxAmount) to quote the exact amount.