🧠 The ENS Ontology
No one had built a structured, machine-readable classification system for the ENS namespace. Every name existed in isolation — no categories, no relationships, no semantic layer. We built the ontology that changes that. Phase 3 upgrades it to dot-notation segment codes.
📖 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 for ENS domain names.
It organizes the entire ENS namespace into 15 top-level verticals and 170+ segments, each mapped to real-world industries, protocol primitives, and infrastructure functions. Every domain in the ENSv2 Marketplace™ portfolio is assigned to a primary segment code using dot-notation (e.g. CHAIN.L2.BASED, AI.COORD, IDENTITY.ENFORCEMENT) that directly drives its score, pricing, and lease rate.
The ontology is the semantic backbone of the marketplace — it powers discovery, pricing, bundling, agent routing, and protocol classification. It is the structure that 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. The dot-notation schema mirrors subdomain paths directly — CHAIN.L2.BASED maps to based.l2.chain.eth.
🗺️ The Vertical Map
15 verticals organized into functional clusters. Hold any card to reveal its segments. 🔴 Core = highest-volume infrastructure · 🟡 Primary = major verticals · 🟢 Vertical = specialized domains
- CHAIN.L1 — Layer 1 Protocols
- CHAIN.L2 — Layer 2 Solutions
- CHAIN.L2.BASED — Based Rollups
- CHAIN.L2.OPT — Optimistic Rollups
- CHAIN.L2.ZK — ZK Rollups
- CHAIN.L2.RAAS — Rollup-as-a-Service
- CHAIN.L2.SEQ — Sequencer Services
- CHAIN.L2.DA — Data Availability
- CHAIN.VALIDATOR — Validators & Nodes
- CHAIN.ENS — ENSv2 Infrastructure
- CHAIN.GAS — Paymaster & Gas
- CHAIN.BRIDGE — Cross-chain & Bridges
- CHAIN.INTEROP.MSG — Cross-chain Messaging
- CHAIN.INTEROP.OMNI — Omnichain Infrastructure
- CHAIN.INTEROP.ABSTRACT — Chain Abstraction
- CHAIN.UPGRADE — Ethereum Upgrade Infrastructure
- CHAIN.SUBSTRATE — Global Infrastructure Substrate
- DEV.SDK — SDKs & Libraries
- DEV.API — APIs & Gateways
- DEV.ROUTER — Router Pattern Infrastructure
- DEV.EXECUTOR — Executor Pattern Infrastructure
- DEV.ORCHESTRATOR — Orchestrator Pattern Infrastructure
- DEV.ENGINE — Engine & Processor Infrastructure
- DEV.GATEWAY — Gateway, Hub & Endpoint Infra
- DEV.DISPATCHER — Handler & Dispatcher Infrastructure
- DEV.MANAGER — Manager & Controller Infrastructure
- DEV.WORKFLOW — Workflow & Pipeline Tools
- DEV.DEPLOY — Deployment Tools
- DEV.TESTING — Testing & Debugging
- AI.INFRA — AI Infrastructure & Models
- AI.AGENTS — Agent Networks & Registries
- AI.AGENTIC — Agentic Systems & Operations
- AI.COORD — Agent Coordination & Control
- AI.AUTONOMOUS — Autonomous Systems
- AI.NEURAL — Neural Networks & Processing
- AI.AGI — AGI Frameworks
- AI.WORKFLOW — Workflow & Operations Agents
- AI.SAFETY.AUDIT — Model Auditing & Safety
- AI.SAFETY.POLICY — AI Governance & Policy
- AI.SAFETY.ETHICS — Responsible AI Infrastructure
- AI.SAFETY.EXPLAIN — Transparency & Explainability
- AI.SAFETY.RISK — AI Risk Assessment
- DEFI.LENDING — Lending & Borrowing
- DEFI.DEX — DEXs & Trading
- DEFI.LIQUIDITY — Liquidity Provision
- DEFI.YIELD — Yield Farming & Optimization
- DEFI.STABLE — Stablecoins & Payments
- DEFI.DERIVATIVES — Derivatives & Perpetuals
- DEFI.SETTLEMENT — Payment Rails & Settlement
- DEFI.INTENTS — Intents & Order Flow
- DEFI.INTENT_INFRA — Intent Infrastructure
- DEFI.AUTOMATION — DeFi Automation & Bots
- DEFI.STREAMING — Streaming Payments
- DEFI.SWAP — Swap & Collateral Infrastructure
- DEFI.STABLE_INFRA — Stablecoin Infrastructure
- IDENTITY.DID — Decentralized Identity
- IDENTITY.CREDENTIALS — Credentials & Attestations
- IDENTITY.KYC — KYC & Compliance Identity
- IDENTITY.VERIFY — Identity Verification
- IDENTITY.REPUTATION — Reputation Systems
- IDENTITY.REGISTRY — Registry Services
- IDENTITY.ACCESS — Rights & Access Control
- IDENTITY.JURISDICTION — Jurisdictional Identity
- IDENTITY.RECORDS — Records Management
- IDENTITY.TRUST — Trust & Enforcement Infrastructure
- IDENTITY.AUTH — Authentication & Authorization
- IDENTITY.IP — IP Identity
- IDENTITY.ENFORCEMENT — Enforcement Root Primitives
- IDENTITY.GOV_ID — Government & Healthcare IDs
- IDENTITY.EDUCATION — Education Credentials
- SECURITY.ZK — Zero-Knowledge Proofs
- SECURITY.ZKVM — zkVM Infrastructure
- SECURITY.ZKWASM — zkWasm Infrastructure
- SECURITY.ZKPROOF — ZK Protocols & General
- SECURITY.ZKEVM — zkEVM Infrastructure
- SECURITY.PROVER — Prover Services & Proof Generation
- SECURITY.PRIVACY — Privacy Protocols
- SECURITY.AUTOMATION — Security Automation
- SECURITY.KEYS — Encryption & Key Management
- SECURITY.PQC — Post-Quantum Cryptography
- SECURITY.CONFIDENTIAL — Confidential Computing
- SECURITY.RLN — Rate-Limit Nullifiers
- SECURITY.MEMPOOL — Censorship Resistance & Mempools
- COMPLY.REGULATORY — Compliance & Regulatory
- COMPLY.AML — AML/KYC Services
- COMPLY.AML_INFRA — AML Infrastructure
- COMPLY.KYC_INFRA — KYC Infrastructure
- COMPLY.AUDIT — Audit & Verification Infrastructure
- COMPLY.LEGAL — Legal Infrastructure
- COMPLY.AI — AI-Driven Compliance Systems
- COMPLY.CHARTER — Banking Charters
- COMPLY.REG_INFRA — Regulatory Infrastructure
- COMPLY.INSTITUTIONAL — Institutional Finance & Treasury
- COMPLY.FINTECH — Fintech Compliance
- COMPLY.SUPPLY — Supply Chain & Trade Compliance
- COMPLY.TAX — Tax & Accounting Infrastructure
- COMPLY.ENTERPRISE — Enterprise Solutions
- FINTECH.INSURANCE — Insurance & Coverage
- FINTECH.RISK — Risk Management & Fraud
- FINTECH.BANKING — Banking & Lending Platforms
- FINTECH.TREASURY — Treasury & Capital Management
- FINTECH.TAX — Tax & Accounting
- FINTECH.RETIREMENT — Retirement Plans & Admin
- FINTECH.RETIREMENT.401K — 401k & Defined Contribution
- FINTECH.RETIREMENT.IRA — IRA & Individual Retirement
- FINTECH.INVESTMENT — Investment & Asset Management
- FINTECH.CUSTODY — Custody Services
- FINTECH.CHARTER — Digital Banking Charters
- FINTECH.BANKING_INFRA — Banking Infrastructure
- STAKING.RESTAKE — Restaking Protocols
- STAKING.LIQUID — Liquid Staking Tokens
- STAKING.INFRA — Restaking Infrastructure
- STAKING.SECURITY — Security Services
- STAKING.SLASHING — Slashing Protection
- STAKING.VALIDATOR — Validator Services
- STAKING.COORD — Staking Coordination
- STAKING.KEEPER — Keeper & Health Monitoring
- DATA.ORACLE — Oracle Networks & Feeds
- DATA.INDEX — Data Indexing & Query
- DATA.ANALYTICS — Analytics & Dashboards
- DATA.AGGREGATE — Data Aggregation
- DATA.SERVICES — Data Services & APIs
- DATA.STREAM — Data Streaming Infrastructure
- DATA.PROVER — Oracle Validators & Provers
- DATA.PREDICT — Prediction Infrastructure
- DATA.PIPELINE — Data Pipelines
- DATA.CROSSCHAIN — Cross-Chain Indexing
- CONTRACT.PRIMITIVE — S-Tier Primitives
- CONTRACT.DEV — Contract Development
- CONTRACT.SYSTEM — Smart Contract Systems
- CONTRACT.SOLIDITY — Solidity Ecosystem
- CONTRACT.AUDIT — Security Audits
- CONTRACT.STANDARD — ERCs & Protocol Standards
- CONTRACT.VERIFY — Verification Services
- CONTRACT.MANAGE — Contract Management & Execution
- GOV.DAO — DAO Frameworks
- GOV.VOTING — Voting & Proposals
- GOV.TREASURY — Treasury Management
- GOV.TOOLS — Governance Tools
- GOV.INFRA — Governance Infrastructure
- GOV.TREASURY_COORD — Treasury Coordination
- GOV.RULES — Rules & Membership Systems
- PLATFORM.BUSINESS — Business SaaS
- PLATFORM.DEV — Developer SaaS
- PLATFORM.INDUSTRY — Industry-Specific Suites
- PLATFORM.CLOUD — Cloud Platform Services
- PLATFORM.WORKSPACE — Workspace & Collaboration
- PLATFORM.AUTOMATION — Business Automation
- PLATFORM.HR — HR & Workforce Management
- PLATFORM.HR_OPS — HR Operations & Payroll
- PLATFORM.BENEFITS — Employee Benefits & Programs
- PLATFORM.LOYALTY — Loyalty & Rewards Programs
- PLATFORM.HEALTH — Healthcare & BioTech Infrastructure
- ASSETS.TOKENIZE — Asset Tokenization & Management
- ASSETS.REALESTATE — Real Estate & Property Tech
- ASSETS.RWA_INFRA — RWA Infrastructure & Workflows
- ASSETS.LEASE — Rental & Leasing Infrastructure
- ASSETS.OWNERSHIP — Ownership Transfer Layer
- ASSETS.MOBILITY — Transportation & Mobility RWAs
- ASSETS.DEPIN — DePIN Coordination & Tokenomics
- ASSETS.DEPIN_COMPUTE — Compute & Storage DePIN
- ASSETS.DEPIN_ENERGY — Energy & Power DePIN
- ASSETS.DEPIN_BANDWIDTH — Data & Bandwidth Markets
- ASSETS.DEPIN_AVIATION — Aviation & Airspace DePIN
- ASSETS.IOT — IoT & Environmental Monitoring
- ASSETS.INDUSTRIAL — Industrial IoT & Supply Chain
- ASSETS.MACHINE — Machine Economy Infrastructure
- ASSETS.SPACE — Satellite Data & Infrastructure
- ASSETS.SCIENCE — Scientific Compute & Research
- ASSETS.SUPPLY — Supply Chain & Provenance
- ASSETS.TRADE — Trade Finance
- CONSUMER.SOCIAL — Social Networks
- CONSUMER.MESSAGING — Messaging & Communication
- CONSUMER.GAMING — Gaming Infrastructure
- CONSUMER.METAVERSE — Metaverse Platforms
- CONSUMER.MEDIA — Content Creation & Publishing
- CONSUMER.IP — IP & Licensing
- CONSUMER.NFT — NFTs & Collectibles
- CONSUMER.CREATOR — Creator Tools
- CONSUMER.RETAIL — Crypto Payments at Point of Sale
- CONSUMER.ECOMMERCE — E-commerce & Shopping
- CONSUMER.LOYALTY — Consumer Loyalty & Rewards
- CONSUMER.WALLET — Consumer Identity & Wallets
- CONSUMER.CREDIT — Retail Finance & BNPL
🔗 Vertical Breakdowns & Semantic Relationships
The ontology is not just a flat list. Verticals have semantic relationships — names in one vertical depend on, extend, or enable names in adjacent verticals. The most important chain is the Identity Stack.
The Identity Chain — Semantic Relationships
One of the most important structural patterns in the ontology 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 ENSv2 Marketplace™ ontology maps to a specific segment in this chain or one of the other 14 verticals — creating a machine-readable semantic layer that AI agents, protocols, and enterprise systems can rely on.
⚙️ How the Ontology Is Used
The ontology powers every function of the ENSv2 Marketplace™ — from how names are priced to how they are discovered, bundled, and leased.
⚡ Protocol Primitives
Protocol primitives are names that define fundamental operations in Web3 infrastructure. They are the highest-scoring names in the ontology — Score 13–15, Category Monopoly tier — because they name things that don't have alternatives.
bridgeorchestrator
capitalorchestrator
coreorchestrator
dataorchestrator
national-id
stateid
international-id
govid
zkprovernode
fpgaprover
nodeprover
proofaggregator
agentexecutor
rolluporchestrator
protocolexecutor
settlementexecutor
crosschainrouter
omnichainprotocol
chainabstractor
unifiedchain
charterprotocol
digitalbankcharter
fintechcharter
chartergovernance
🌐 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 is 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.
ENSv2 Marketplace™ built this ontology. We published it. We are the authority.