ZK Rollup Stack — Curated Namespace Set

Build a ZK Rollup
Without Naming Your Infrastructure From Scratch

Eight pre-curated, protocol-grade ENS namespaces covering every layer of a production ZK rollup — execution, proof generation, verification, sequencing, bridging, coordination, and developer access. The naming layer for the rollup teams scaling Ethereum. Every name scored, classified, and resolving on-chain today.

Names in stack
8
Resolving on-chain
8 / 8
Tier range
T11 — T17
Annual lease (full stack)
$59,000/yr

01The Stack

Eight names. Each does one job. Together they cover the full lifecycle of a ZK rollup — from execution through proof generation, verification, sequencing, bridging to L1, coordination, and developer access. Click any name to view its full registry page.

zkrollupprover.eth
Tier 17 · $11,000/yr
Proof generation infrastructure. The component that takes execution traces and generates the zero-knowledge proofs your rollup posts to L1.
zkrollupverifier.eth
Tier 16 · $9,500/yr
On-chain settlement and verification logic. The contract that validates proofs from the prover and finalizes rollup state on Ethereum.
zkrollupapi.eth
Tier 15 · $8,000/yr
Developer-facing access layer. JSON-RPC endpoint, SDK distribution, integration tooling for teams building on top of the rollup.
zkrollupnode.eth
Tier 15 · $8,000/yr
The execution layer. Runs transactions, maintains state, generates execution traces for the prover.
zkrollupsequencer.eth
Tier 15 · $8,000/yr
Transaction ordering layer. Where rollup transactions are batched, ordered, and committed before proof generation — the canonical sequencer namespace.
zkrollupbridge.eth
Tier 13 · $5,500/yr
Settlement bridge to L1. Trustless deposit and withdrawal layer where assets move between L1 and the rollup, secured by validity proofs.
zkrollupcoordinator.eth
Tier 13 · $5,500/yr
Cross-component orchestration. Coordinates sequencer ↔ prover ↔ verifier handoffs in a complete production rollup deployment.
zkrollupinfra.eth
Tier 11 · $3,500/yr
Operational infrastructure namespace — monitoring, logging, alerting, deployment, and supporting services for the rollup stack.

How they fit together

node sequencer prover verifier bridge L1 settlement
coordinator orchestrates node ↔ sequencer ↔ prover ↔ verifier
api node (developer + user access)
infra monitors all 7 above
Each name corresponds to a real subsystem in production ZK rollups. Names you'd actually use as service identifiers, RPC endpoints, namespace roots, or organizational identity for the project.
Full Stack Annual Lease
$59,000/yr
Eight protocol-grade namespaces. Available individually or as the full stack when ENSv2 launches subdomain leasing.
No payment now · We'll contact you when ENSv2 ships

02Why a Curated Stack

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.

Coherent identity
Eight names that share a doctrine: each describes WHAT the thing is at protocol level. No vendor branding, no speculation on the name. Builders see infrastructure, not marketing.
Real on-chain footprint
8 of 8 names already resolve via ENS today (eth.limo). On-chain text records classify each component by function. Verifiable, queryable, integrated into wallets and explorers.
Predictable cost
$59,000/yr for the full stack of eight namespaces. No haggling, no auctions, no flip-floor surprises. Tier-based pricing. Same rate for any team that asks.

03Common Questions

Can I lease just one name from the stack?

Yes. Each name is independently lease-eligible. The "full stack" framing is for teams who want all eight at once — you're not locked in. Most teams start with execution + proving (zkrollupnode, zkrollupprover, zkrollupverifier) and add components over time.

What does "lease" actually mean here?

You get exclusive subdomain rights under the parent name (e.g., your project becomes team.zkrollupnode.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.

Why not just register your own ENS names?

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."

When does this go live?

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.

Is this the only stack you offer?

No. CPR has 44 ontological stacks across the portfolio of over 2,750 names. The other Featured Stacks: Oracle Network Stack, Identity Stack, Restaking Stack, API Infrastructure Stack, and MEV Defense Stack. Browse all 15 verticals or the full registry.

04Production Implementations

The teams shipping ZK rollup infrastructure — provers, sequencers, verifiers, full execution stacks. As leases activate, this section will list who’s building on which namespace. If you’re building a ZK rollup and want a slot here, get in touch.

OPEN
Featured implementation
Proof generation · prover infrastructure
OPEN
Featured implementation
Execution layer · rollup node
OPEN
Featured implementation
Sequencer services · ordering layer
OPEN
Featured implementation
Settlement · on-chain verification