Patent Explainer: DNS-DEX Domain Tokenization (F-005)

What F-005 Does

F-005 describes a system for converting domain name ownership into tradeable blockchain tokens. A domain owner verifies ownership through a multi-proof bundle (DNS TXT record, HTML meta tag, or well-known file), and the system creates fungible tokens whose symbol is derived directly from the domain name. The tokens are priced using a deterministic square-root decay formula, so anyone can independently compute the current price from publicly observable state. Token holders receive proportional micropayment revenue from the domain's web traffic, and the domain's content progressively migrates from centralised cloud hosting to censorship-resistant on-chain storage.

This is the patent that turns every domain name into a fractionally ownable, revenue-generating investment.

The Problem It Solves

1. No domain fractionalisation. Domain names are indivisible assets. A domain is either owned or not. There is no native mechanism to fractionalise ownership into tradeable shares. An investor who believes a domain will appreciate in value must either buy the entire domain or not participate at all.

2. No domain revenue sharing. When a domain generates revenue through advertising, subscriptions, micropayments, or other methods, there is no standardised mechanism to distribute that revenue to multiple stakeholders proportionally. No system provides automated, transparent, on-chain revenue distribution to domain token holders.

3. No serverless domain verification. Traditional domain ownership verification requires DNS lookup utilities (dig, nslookup, host) that are unavailable in serverless computing environments such as Vercel Edge Functions, Cloudflare Workers, and AWS Lambda. No standardised multi-method verification bundle exists that works across all deployment environments.

4. No deterministic domain pricing. Domain name valuation is subjective and opaque. When fractional interests in a domain are offered, there is no algorithmic pricing mechanism that provides transparent, mathematically deterministic pricing. No party can independently compute the current price without relying on a centralised price oracle.

5. No domain-as-token-symbol convention. Existing token systems use arbitrary ticker symbols ($BTC, $ETH, $DOGE) that are disconnected from the underlying asset. There is no convention that maps a domain name directly to its token symbol, creating a self-documenting link.

6. No progressive decentralisation for domain content. Domain content is either centrally hosted (fast but censorable) or fully on-chain (censorship-resistant but slow). There is no architecture enabling progressive migration from one to the other.

How It Works

Multi-Proof Ownership Verification

Domain ownership is verified through a multi-proof bundle comprising three independent methods, any one of which suffices. The methods are attempted in fallback order:

DNS TXT Record — The domain owner adds a TXT record to the domain's DNS configuration at a verification subdomain (_dnsdex.<domain> or _path402.<domain>) or the root domain itself. The record contains a verification code prefixed with dnsdex-verify= or path402-verify=. The system queries public DNS resolvers via DNS-over-HTTPS (Google DNS, Cloudflare DNS) using standard HTTP requests, enabling verification in serverless environments where system-level DNS utilities are unavailable.

HTML Meta Tag — The domain owner adds a meta tag to the domain's web content containing the verification code.

Well-Known File — The domain owner places a verification file at a standardised well-known path.

The verification code is cryptographically derived from a combination of the domain name, the requestor's wallet address, and a timestamp-based seed. The code is deterministic for a given set of inputs, domain-bound (different code for different domains), wallet-bound (different code for different wallet addresses), and time-limited (codes expire after at most one hour).

Domain-as-Token-Symbol Convention

The token symbol for a tokenised domain is derived directly from the domain name by prefixing it with the dollar sign: $<domain.tld>. For example:

• b0ase.com produces $b0ase.com
• coca-cola.com produces $coca-cola.com
• amazon.co.uk produces $amazon.co.uk

Symbol uniqueness is guaranteed by the uniqueness of domain names in the DNS — no two domains can have the same name, therefore no two domain tokens can have the same symbol. This convention extends the $402 protocol's URL path tokenisation upward to the domain level itself.

On-Chain Inscription

Verified domain tokens are inscribed on the BSV blockchain as 1-satoshi ordinal inscriptions. The inscription contains structured metadata including: the protocol identifier ($402), the operation type (publish), the content type (domain_verification), the domain name, the token supply, pricing parameters, the x402 fee, the ownership proof reference, and a timestamp. The transaction ID serves as the canonical reference for the domain token.

Square-Root Decay Deterministic Pricing

The price of each fractional domain token is determined by the formula:

price = base_price / sqrt(supply_remaining + 1)

Where supply_remaining is the number of tokens not yet distributed. This produces a monotonically increasing price curve: when supply_remaining is large (early purchases), the denominator is large and the price is low. As supply_remaining decreases (later purchases), the denominator shrinks and the price increases.

The pricing is deterministic — any party can independently compute the current price from publicly observable state. No order book, no price negotiation, and no centralised price oracle are required. Early participants are mathematically guaranteed to pay less than later participants, creating an incentive for early adoption.

Micropayment Revenue Distribution

Domain visitors pay micropayments via the HTTP 402 payment protocol when accessing gated content. Revenue is split according to a declared ratio between the domain owner and a distribution pool. Token holders receive proportional dividends from the distribution pool based on their token holdings. Revenue events are recorded on-chain, providing transparent accounting. The x402 payment indexing enables real-time revenue tracking and dividend computation.

Sovereign Bridge: Progressive Decentralisation

Domain content is delivered through a three-phase progressive decentralisation model:

Phase 1 — Cloud-Primary: Content is served from cloud infrastructure for standard web performance while domain token metadata is inscribed on-chain for ownership proof.

Phase 2 — Hybrid: Periodic snapshots of domain content are archived to blockchain-based distributed storage, creating verifiable content backups.

Phase 3 — On-Chain Fallback: If cloud infrastructure becomes unavailable, protocol resolvers automatically fall back to serving content from blockchain storage. Token holders may vote via a governance mechanism to redirect the domain to alternative infrastructure.

This architecture enables domain owners to benefit from cloud speed while progressively building censorship-resistant fallback infrastructure.

Live Implementation

• Platform: dnsdex.com — the DNS-DEX domain tokenisation marketplace
• Protocol: path402.com — the $402 protocol underlying domain tokenisation

---

Filed at UKIPO by The Bitcoin Corporation Ltd. Patent pending. Application reference F-005.