Identity Stack — Curated Namespace Set

Build an Identity Layer
Without Naming Your Infrastructure From Scratch

Fifteen pre-curated, protocol-grade ENS namespaces covering every layer of a complete identity infrastructure — sovereign jurisdiction primitives at the top (T20 national-id, T19 federal-id, T18 state-id), through resolution, records, permissions, authentication, and KYC compliance. The naming layer for sovereign identity and protocol-grade resolution infrastructure. Every name scored, classified, and resolving on-chain today.

Names in stack
15
Resolving on-chain
15 / 15
Tier range
T13 — T20
Annual lease (full stack)
$136,000/yr

01The Stack

Fifteen names organized into the full identity-doctrine flow: Jurisdiction → Resolution → Records → Permissions → Authentication → Credentials → Compliance. Each name has a distinct architectural role. Click any name to view its full registry page.

national-id.eth
Tier 20 · $15,000/yr
Sovereign identity primitive. The canonical namespace for national-level identity systems — anchors government-issued ID infrastructure on-chain.
federal-id.eth
Tier 19 · $13,750/yr
Federal-jurisdiction identity primitive. Where federal identity infrastructure publishes records, attestations, and authentication endpoints.
state-id.eth
Tier 18 · $12,500/yr
State and regional identity primitive. The canonical layer for state-issued identity binding — driver's licenses, residency, sub-national credentials.
coreresolver.eth
Tier 17 · $11,000/yr
Canonical resolver primitive. The engine that maps ENS names to identity records, jurisdictional bindings, and credential schemas across the registry.
recordinfrastructurelayer.eth
Tier 16 · $9,500/yr
Records infrastructure layer. The data plane where identity records are stored, indexed, and queried — the canonical record-keeping primitive.
enforcementprotocol.eth
Tier 16 · $9,500/yr
Trust and policy enforcement protocol. Where access decisions, jurisdictional rules, and compliance constraints get enforced at the protocol level.
canonicalpermissions.eth
Tier 16 · $9,500/yr
Canonical permission-grant primitive. The namespace where granular permission schemas and access-control patterns publish for ENSv2 roles.
jurisdictionlayer.eth
Tier 15 · $8,000/yr
Jurisdictional binding layer. Where identities bind to legal jurisdictions for regulatory compliance, cross-border verification, and sovereign trust roots.
resolverprotocol.eth
Tier 15 · $8,000/yr
Resolver protocol specification. Reference architecture for ENS-style resolvers handling identity, address, and metadata resolution across chains.
onchainregistry.eth
Tier 15 · $8,000/yr
On-chain identity registry. The canonical public ledger where DID, credential, and identity records publish for anyone to verify trustlessly.
authenticationprotocol.eth
Tier 14 · $6,750/yr
Authentication protocol layer. The canonical spec for proving identity claims — wallet signatures, biometric attestations, multi-factor verification.
attestationlayer.eth
Tier 14 · $6,750/yr
Credential and attestation issuance layer. Where issuers publish verifiable credentials — diplomas, professional licenses, KYC attestations.
verificationprotocol.eth
Tier 14 · $6,750/yr
Verification protocol primitive. Independent audit and cross-checking of credentials — the verifier-side of the issuer/holder/verifier triangle.
kycframework.eth
Tier 13 · $5,500/yr
KYC compliance framework. Binds on-chain identity to off-chain regulatory requirements — AML, sanctions, age verification, source-of-funds.
enforcementengine.eth
Tier 13 · $5,500/yr
Enforcement runtime. Where access decisions actually execute — denying, granting, revoking permissions in real-time across the identity stack.

How they fit together — the identity doctrine

national-id federal-id state-id (sovereign jurisdiction tree)
enforcement runtime kyc (policy + compliance binding)
The full identity-doctrine chain encoded as ENS names: Identity → Auth → Access → Records → Trust → Comply. Each name corresponds to a real subsystem in production identity infrastructure. Names a sovereign issuer, KYC provider, identity wallet, or verification service would actually use as namespace roots.
Full Stack Annual Lease
$136,000/yr
Fifteen protocol-grade namespaces — including three of the highest-tier names in the registry (national-id T20, federal-id T19, state-id T18). 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
Fifteen 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
All 15 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
$136,000/yr for the full stack of fifteen 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 fifteen at once — you're not locked in. Most teams start with the resolution layer (coreresolver, onchainregistry, jurisdictionlayer) 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.coreresolver.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: ZK Rollup Stack, Oracle Network Stack, Restaking Stack, API Infrastructure Stack, and MEV Defense Stack. Browse all 15 verticals or the full registry.

04Production Implementations

The teams shipping identity infrastructure — sovereign primitives, KYC, credentials, resolution, jurisdictional registries. As leases activate, this section will list who’s building on which namespace. If you’re shipping identity infrastructure and want a slot here, get in touch.

OPEN
Featured implementation
Sovereign jurisdiction primitives
OPEN
Featured implementation
Credentials & attestation
OPEN
Featured implementation
KYC & compliance identity
OPEN
Featured implementation
Resolution & records infrastructure