What Is the ENS Ontology?
An ontology is a formal classification of knowledge — a structured system that defines concepts, categories, and relationships within a domain. The ENS Ontology is the first formal classification system published for ENS domain names.
It organizes the entire ENS namespace into 15 top-level verticals and 237 segment paths, each mapped to a real-world industry, protocol primitive, or infrastructure function. Every domain in our registry is assigned a primary segment code in dot-notation — for example CHAIN.L2.BASED, AI.COORD, IDENTITY.ENFORCEMENT, CHAIN.NAMESPACE — which directly drives its score, tier, and annual lease rate.
The ontology is the semantic backbone of the registry. It powers discovery, pricing, bundling, agent routing, and protocol classification. It turns a chaotic namespace into an organized, machine-readable infrastructure layer.
Why It Exists
ENS names have no native structure. Without an ontology, every name is just a string. The ENS Ontology gives every name meaning, context, and position within the broader Web3 infrastructure stack.
Who Uses It
Developers, founders, analysts, and AI agents who need to discover, price, filter, or route ENS names by function — not just by string pattern.
How It’s Built
Each vertical maps to a real-world industry or protocol function. Each segment defines a specific layer within that vertical. Domain assignment is deterministic — not subjective.
Why It Matters for ENSv2
ENSv2’s hierarchical subdomain system needs a semantic layer. Our dot-notation schema mirrors subdomain paths directly — CHAIN.L2.BASED maps to based.l2.chain.eth.
The Vertical Map
The 15 verticals organize into four functional clusters based on the role each one plays in the Web3 infrastructure stack. Click any vertical to reveal its full segment list.
Core Protocol Infrastructure
The foundational layer — blockchain protocols, developer systems, AI coordination, and identity. These verticals carry the highest base scores.
CHAIN Blockchain & Protocol Infrastructure
- L1 Layer 1 Protocols
- L2 Layer 2 Solutions
- L2.BASED Based Rollups
- L2.OPT Optimistic Rollups
- L2.ZK ZK Rollups
- L2.APPCHAIN App-Specific L2s
- L2.SEQ Sequencer Services
- L2.DA Data Availability
- L2.RAAS Rollup-as-a-Service
- VALIDATOR Validators & Nodes
- CONSENSUS Consensus & Security
- BRIDGE Cross-chain & Bridges
- NAMESPACE Namespace Infrastructure
- ENS ENSv2 Infrastructure
- FRAME Frame Transaction Infrastructure
- SUBSTRATE Global Infrastructure Substrate
- INTEROP.OMNI Omnichain Infrastructure
- INTEROP.STD Interoperability Standards
- INTEROP.ID Cross-chain Identity
DEV Developer Tools & Frameworks
- ORCHESTRATOR Orchestrator Pattern Infrastructure
- EXECUTOR Executor Pattern Infrastructure
- ROUTER Router Pattern Infrastructure
- ENGINE Engine & Processor Infrastructure
- GATEWAY Gateway, Hub & Endpoint Infra
- DISPATCHER Handler & Dispatcher Infrastructure
- MANAGER Manager & Controller Infrastructure
- SDK SDKs & Libraries
- API APIs & Gateways
- WORKFLOW Workflow & Pipeline Tools
- DEPLOY Deployment Tools
- TESTING Testing & Debugging
AI Artificial Intelligence & Agents
- INFRA AI Infrastructure & Models
- AGENTS Agent Networks & Registries
- AGENTIC Agentic Systems & Operations
- COORD Agent Coordination & Control
- AUTONOMOUS Autonomous Systems
- AGI AGI Frameworks
- SAFETY.AUDIT Model Auditing & Safety
- SAFETY.POLICY AI Governance & Policy
- SAFETY.ETHICS Responsible AI Infrastructure
- SAFETY.EXPLAIN Transparency & Explainability
DEFI Decentralized Finance & Payments
- LENDING Lending & Borrowing
- DEX DEXs & Trading
- LIQUIDITY Liquidity Provision
- STABLE Stablecoins & Payments
- DERIVATIVES Derivatives & Perpetuals
- SETTLEMENT Payment Rails & Settlement
- INTENTS Intents & Order Flow
- INTENT_INFRA Intent Infrastructure
- AUTOMATION DeFi Automation & Bots
- STABLE_INFRA Stablecoin Infrastructure
Identity, Access & Compliance
The verification layer — who you are, what you can do, and the regulatory frameworks that govern it.
IDENTITY Identity, Auth & Credentials
- DID Decentralized Identity
- CREDENTIALS Credentials & Attestations
- KYC KYC & Compliance Identity
- AUTH Authentication & Authorization
- ACCESS Rights & Access Control
- JURISDICTION Jurisdictional Identity
- TRUST Trust & Enforcement Infrastructure
- ENFORCEMENT Enforcement Root Primitives
- RECORDS Records Management
- GOV_ID Government & Healthcare IDs
SECURITY Security, Privacy & ZK
- ZK Zero-Knowledge Proofs
- ZKVM zkVM Infrastructure
- ZKEVM zkEVM Infrastructure
- PROVER Prover Services & Proof Generation
- PRIVACY Privacy Protocols
- KEYS Encryption & Key Management
- PQC Post-Quantum Cryptography
- CONFIDENTIAL Confidential Computing
COMPLY Compliance, Legal & Enterprise
- REGULATORY Compliance & Regulatory
- AML AML/KYC Services
- AML_INFRA AML Infrastructure
- KYC_INFRA KYC Infrastructure
- AUDIT Audit & Verification Infrastructure
- LEGAL Legal Infrastructure
- AI AI-Driven Compliance Systems
- CHARTER Banking Charters
- INSTITUTIONAL Institutional Finance & Treasury
Finance, Data & Staking
The financial infrastructure layer — traditional finance bridges, on-chain data services, and validator economics.
FINTECH Traditional Finance, Insurance & Risk
- INSURANCE Insurance & Coverage
- BANKING Banking & Lending Platforms
- BANKING_INFRA Banking Infrastructure
- CHARTER Digital Banking Charters
- CUSTODY Custody Services
- TREASURY Treasury & Capital Management
- RETIREMENT Retirement Plans & Admin
- RISK Risk Management & Fraud
DATA Data, Oracles & Analytics
- ORACLE Oracle Networks & Feeds
- INDEX Data Indexing & Query
- ANALYTICS Analytics & Dashboards
- AGGREGATE Data Aggregation
- STREAM Data Streaming Infrastructure
- PROVER Oracle Validators & Provers
- PIPELINE Data Pipelines
- CROSSCHAIN Cross-Chain Indexing
STAKING Staking, Restaking & Validators
- RESTAKE Restaking Protocols
- LIQUID Liquid Staking Tokens
- INFRA Restaking Infrastructure
- SECURITY Security Services
- SLASHING Slashing Protection
- VALIDATOR Validator Services
- COORD Staking Coordination
CONTRACT Smart Contracts & Standards
- PRIMITIVE S-Tier Primitives
- STANDARD ERCs & Protocol Standards
- SYSTEM Smart Contract Systems
- SOLIDITY Solidity Ecosystem
- AUDIT Security Audits
- VERIFY Verification Services
- MANAGE Contract Management & Execution
Governance, Platforms & Real-World Assets
The application layer — where the infrastructure meets users, DAOs, enterprises, and physical-world systems.
GOV Governance, DAOs & Coordination
- DAO DAO Frameworks
- VOTING Voting & Proposals
- TREASURY Treasury Management
- TOOLS Governance Tools
- INFRA Governance Infrastructure
- RULES Rules & Membership Systems
PLATFORM SaaS, Platforms & Business
- BUSINESS Business SaaS
- INDUSTRY Industry-Specific Suites
- CLOUD Cloud Platform Services
- WORKSPACE Workspace & Collaboration
- HR HR & Workforce Management
- HEALTH Healthcare & BioTech Infrastructure
- AUTOMATION Business Automation
ASSETS Real-World Assets & Physical Infrastructure
- TOKENIZE Asset Tokenization & Management
- REALESTATE Real Estate & Property Tech
- RWA_INFRA RWA Infrastructure & Workflows
- MOBILITY Transportation & Mobility
- DEPIN DePIN Coordination & Tokenomics
- MACHINE Machine Economy Infrastructure
- SPACE Satellite Data & Infrastructure
- SUPPLY Supply Chain & Provenance
CONSUMER Social, Gaming, Media & Retail
- SOCIAL Social Networks
- GAMING Gaming Infrastructure
- METAVERSE Metaverse Platforms
- MEDIA Content Creation & Publishing
- CREATOR Creator Tools
- ECOMMERCE E-commerce & Shopping
- RETAIL Crypto Payments at Point of Sale
The Identity Chain — Semantic Relationships
The ontology isn’t a flat list. Verticals have semantic relationships — names in one vertical depend on, extend, or enable names in adjacent verticals. The most important structural pattern is the identity-to-policy chain: each layer builds on the last, creating a complete semantic stack for decentralized identity and access management.
Every name in the registry maps to a specific segment in this chain or one of the other 14 verticals. The result is a machine-readable semantic layer that AI agents, protocols, and enterprise systems can rely on for routing, discovery, and enforcement.
How the Ontology Is Used
The ontology powers every function of the registry — from how names are priced to how they’re discovered, bundled, and leased.
crosschainrouter.eth under CHAIN.INTEROP.OMNI, not buried in general infrastructure.Protocol Primitives
Protocol primitives are names that define fundamental operations in Web3 infrastructure. They’re the highest-scoring names in the ontology — Score 15–20, Category Monopoly and above — because they name things that don’t have alternatives. These are pulled from the live registry, top-scored within each segment.
- coreorchestrator
- dataorchestrator
- accessorchestrator
- agenticorchestrator
- autonomousorchestrator
- national-id
- federal-id
- state-id
- canonicaljurisdiction
- bermudaregistry
- fpgaprover
- asicprover
- nodeprover
- dataprover
- canonicalverification
- canonicalregistry
- canonicalnamespace
- canonicalprotocol
- canonicalinfrastructure
- hierarchicalregistry
- interoperableaddress
- interoperablename
- omnichainprotocol
- omnichainbridge
- omnichainliquidity
- ensv2bridge
- ensv2resolver
- ensv2vault
- namechainresolver
- canonicalresolver
- agenticexecutor
- basedexecutor
- crosschainexecutor
- identityexecutor
- autonomousexecutor
- charterprotocol
- charterframework
- digitalbankcharter
- institutionallayer
- charterinfrastructure
Why This Matters for the ENS Ecosystem
The ENS namespace has grown to millions of names with no formal structure. Marketplaces list names alphabetically or by price. There is no semantic layer — no way to know what a name does, what vertical it belongs to, or how it relates to adjacent names.
The ENS Ontology solves this. It’s the first published, structured classification system for ENS that:
- Assigns every name to a deterministic vertical and segment code.
- Maps names to real-world industries and protocol functions.
- Creates a machine-readable layer for AI agents and automated systems.
- Provides a pricing framework grounded in semantic value, not speculation.
- Aligns with ENSv2’s hierarchical subdomain architecture via dot-notation.
- Enables structured discovery, filtering, and bundling at scale.
As ENSv2 launches and subdomain leasing becomes the dominant use case, the ontology becomes the routing layer — telling systems which names anchor which infrastructure, and what each subdomain namespace is for.
We built this ontology. We published it. We are the authority.
See how the ontology drives pricing in the Pricing Guide, or browse every classified namespace in the main registry.