# MEV-X Homelander

Post-swap, atomic MEV internalization for DEXs

## Pages

- [MEV-X Homelander](https://mev-x-project.github.io/Homelander-docs/): MEV-X Homelander is a post-swap, atomic MEV internalization framework for AMM pools. Every user swap creates a short-lived arbitrage opportunity as pool balances adjust — today, that opportunity is almost always captured outside the pool that created it, by external searchers, block builders, and validators. Homelander closes that gap: a post-swap hook triggers an on-chain execution layer that detects and captures the opportunity inside the same transaction as the originating swap, before it can be broadcast, bundled, or extracted by anyone outside the system. The result is a deterministic on-chain revenue channel for the pool itself, distributed to the parties who created the opportunity — the pool's deployer, its liquidity providers, and the protocol — instead of leaking to infrastructure operators uninvolved in creating that liquidity or that trade.
- [Architecture](https://mev-x-project.github.io/Homelander-docs/architecture-overview/): Homelander operates as an adjunct execution pipeline, isolated from core AMM mechanics. When no profitable opportunity exists, the pipeline stays inactive and adds no cost to the swap.
- [Integrations Overview](https://mev-x-project.github.io/Homelander-docs/integration-overview/): Homelander connects to a pool through one of three relationships, depending on who's setting it up and what they're allowed to do. This page maps each one to how it works and where the value goes; the pages under each cover the technical detail.
- [For Pool Deployers](https://mev-x-project.github.io/Homelander-docs/for-pool-deployers/): Deploying a pool with Homelander attached is a self-serve, permissionless process on Uniswap v4 — no coordination with any team, no approval step. In practice, most deployers won't construct these calls by hand; a wizard interface handles the sequencing for them. This page describes what happens underneath it.
- [For LP Providers](https://mev-x-project.github.io/Homelander-docs/for-lp-providers/): There's no integration step here, because there's nothing for an LP to integrate. Liquidity providers interact with a Homelander-enabled pool exactly like they would any other pool — same deposit flow, same tooling, no approvals granted to any Homelander contract.
- [For DEXs & Protocols](https://mev-x-project.github.io/Homelander-docs/for-dexs-protocols/): Attaching Homelander to an existing protocol's pools takes one of three forms, depending on what your AMM architecture already exposes. All three settle through the same on-chain core (see [Architecture](../architecture-overview)) and provide the same execution guarantees — atomic, no mempool exposure, no effect on the user's swap output regardless of whether a profitable opportunity exists. What differs is the entry point, and who's allowed to use it.
- [Plugin-Based Integration](https://mev-x-project.github.io/Homelander-docs/plugin-based/): Plugin-based integration attaches Homelander through the AMM's own hook or plugin surface — no proxy, nothing wrapping the pool. Two frameworks support this today: Algebra Integral and PancakeSwap Infinity.
- [Universal DEX Integration](https://mev-x-project.github.io/Homelander-docs/universal-dex/): The Universal integration path enables MEV capture for DEX protocols that don't expose a native hook or plugin interface. A proxy contract wraps the existing router: the proxy executes the swap through the underlying DEX and triggers the Homelander backrun within the same transaction. No modifications to the underlying pool contracts are required.
- [Direct Contract Integration](https://mev-x-project.github.io/Homelander-docs/direct-access/): Direct integration lets any smart contract invoke the Homelander backrun trigger explicitly, after completing its own swap logic. This path suits protocols with custom architectures, aggregators, or any scenario that needs conditional or parameterized MEV capture.
- [Security Overview](https://mev-x-project.github.io/Homelander-docs/security-overview/): Homelander operates strictly as a consumer of post-swap state — whichever entry point it's attached through (hook, plugin, proxy, or direct call — see [Deployment Models](../architecture-overview#deployment-models)), it never performs privileged actions against the pool itself. Its safety profile is bounded by that entry point's own guarantees: if the underlying AMM framework's hook or callback system is secure, Homelander's integration doesn't introduce a new attack surface on top of it.
- [Bailsec Audit](https://mev-x-project.github.io/Homelander-docs/bailsec/): MEV-X Homelander has undergone an independent security audit conducted by Bailsec, focused on the correctness and safety of its on-chain execution logic.
- [Bailsec Differential Audit](https://mev-x-project.github.io/Homelander-docs/bailsec-differential/): MEV-X Homelander has undergone a second independent security audit conducted by Bailsec, focused on the correctness and safety of its on-chain execution logic.
- [MixBytes Audit](https://mev-x-project.github.io/Homelander-docs/mixbytes/): MEV-X Homelander has undergone an independent security audit conducted by MixBytes, focused on the correctness and safety of its on-chain execution logic.
- [Links and Contacts](https://mev-x-project.github.io/Homelander-docs/links-and-contacts/): Self-serve pool deployment and LP participation need no contact with anyone — see [For Pool Deployers](../for-pool-deployers) and [For LP Providers](../for-lp-providers). Attaching Homelander to an existing DEX or protocol is partner-managed; reach out to get your integration path and distribution configuration set up.