Fifteen pre-curated, protocol-grade ENS namespaces covering every layer of a complete restaking network — orchestration at the top, EigenLayer-shaped operator and staker roles, execution, vaults, multi-AVS coordination, and liquid restaking. The naming layer for the operator economy emerging on EigenLayer and beyond. Every name scored, classified, and resolving on-chain today.
Fifteen names organized by function. From the orchestration layer down through validator operations, vaults, multi-AVS coordination, and liquid restaking. Each name has a distinct architectural role. Click any name to view its full registry page.
Naming infrastructure is something most teams do badly. Either everything goes under one bland root, or each component is named ad-hoc by whoever was on call that week. A curated stack solves both.
Yes. Each name is independently lease-eligible. The "full stack" framing is for teams who want all fifteen at once — you're not locked in. Most teams start with the operator + staker + vault triangle (eigenlayeroperator, eigenlayerstaker, restakingvault) and add components over time.
You get exclusive subdomain rights under the parent name (e.g., your project becomes team.eigenlayeroperator.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.
You can. But you'd be naming your stack from scratch, with no semantic layer, no taxonomy, no on-chain classification. These names already have the records, the curation, and the documentation. They drop into a builder's mental model as "primitives" rather than "I made up a name."
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, API Infrastructure Stack, and MEV Defense Stack. Browse all 15 verticals or the full registry.
The teams shipping restaking infrastructure — operators, AVS coordinators, liquid restaking protocols, vault and slashing systems. As leases activate, this section will list who’s building on which namespace. If you’re running an AVS or restaking protocol and want a slot here, get in touch.