Fifteen pre-curated, protocol-grade ENS namespaces covering every layer of MEV-resistant infrastructure — from sandwich protection at the user edge, through encrypted mempools and threshold relays, down to the RLN cryptographic primitives that make it all possible. Acquired in the wake of the May 2026 high-profile sandwich attack that put MEV defense back on every roadmap. Every name scored, classified, and resolving on-chain today.
The user-facing surface. Where wallets, dapps, and aggregators publish identity for sandwich-resistance, MEV mitigation, and protective routing. "MEV mitigation" is the umbrella term that emerged from the post-mortems; sandwichprotection is the most-named attack with the most-named cure.
The privacy substrate. Where transactions hide their contents until inclusion — protecting against frontrunning, sandwich attacks, and order-flow extraction. The relay tier is where MEV-Boost-style block-building meets pre-execution privacy.
The end-user namespace. Where wallets, dapps, and protocols anchor end-to-end encrypted transaction flows.
The cryptographic primitives that make encrypted mempools possible. Rate Limiting Nullifiers (RLN) are the Vac/Waku research primitive used to enforce rate limits on encrypted message networks without de-anonymizing senders. The foundation under everything above.
Charter Lessees get a permanent featured rail at the top of the relevant Stack page (not the open-card row — a named "Charter Implementation" position), first refusal on adjacent names in their vertical, and co-launch positioning when ENSv2 ships. Whatever tier price applies at activation never increases. Standard lessees pay the rate at their initiation; Charter rate is permanent.
Hard cap: 5 slots across all 6 Featured Stacks. First-come. After 5, program closes. No payment until ENSv2 leasing activates.
Inquire about Charter status →The May 7, 2026 sandwich attack wasn't an outlier — it was a demonstration. Every retail trader and every protocol routing flow through public mempools is exposed to extractive bots. The teams building the cure need namespace identity that doesn't sound like a marketing department picked it.
Three distinct sub-clusters that together cover the full MEV-defense stack. The 5 CHAIN.MEV names are the user-facing identity layer (sandwichprotection, mevshield, antimev, etc.). The 4 SECURITY.MEMPOOL/PRIVACY names are the substrate where encryption happens. The 6 RLN names are the Vac/Waku-research cryptographic primitives that make the substrate possible. Three layers, one defense.
Yes. Each name is independently lease-eligible. Most teams will start with 1–3 names that match their architecture (a wallet might just lease sandwichprotection.eth; a relay operator might want encryptedrelay.eth + mempoolencryption.eth). The full-stack framing is for teams building the entire MEV-defense surface, not a lock-in.
You get exclusive subdomain rights under the parent name (e.g., your project becomes team.encryptedrelay.eth) plus the ability to mint additional subdomains as your infrastructure grows. The parent name stays in the registry — you don't buy the parent, you lease the subdomain space.
No. These names are vendor-neutral. They describe primitives at the protocol level — what the things ARE, not who runs them. Flashbots, SUAVE, Shutter, Veiled, and any future MEV-defense protocol are all welcome to lease subdomains under these names. The registry is infrastructure, not a brand.
ENSv2 launches the subdomain-leasing primitives we'd use for full automation. ENS team has stated 2026 launch is on track ↗. Until then, leases are pre-arranged via direct contact. Reserve now to be in the first batch.
No. CPR has 44 ontological stacks across the portfolio of over 2,750 names. The other Featured Stacks: ZK Rollup Stack, Oracle Network Stack, Identity Stack, Restaking Stack, and API Infrastructure Stack. Browse all 15 verticals or the full registry.
The teams shipping in this space — encrypted mempools, sandwich resistance, RLN-backed primitives, anti-MEV settlement. As leases activate, this section will list who's building on which namespace. If you're building MEV defense and want a slot here, get in touch.