⏸Cherry Graffiti
|
AgentsAppsAutomationBitPensionBlogBoardroomBondsBuildButtonsCareersCashboardClientsComponentsContactContentContractsCoursesCreativeDevelopersDividendsDocsExchangeFoundersGigsKintsugiLibraryMarketMetanetMintMoneyButtonMusicPackagesPipelinePortfolioPricingProjectsRewardsRoadmapSchematicsServicesSkillsSmart ContractsStudioTaaSTokensToolsTreasuryVideoWebsitesWorkAgentsAppsAutomationBitPensionBlogBoardroomBondsBuildButtonsCareersCashboardClientsComponentsContactContentContractsCoursesCreativeDevelopersDividendsDocsExchangeFoundersGigsKintsugiLibraryMarketMetanetMintMoneyButtonMusicPackagesPipelinePortfolioPricingProjectsRewardsRoadmapSchematicsServicesSkillsSmart ContractsStudioTaaSTokensToolsTreasuryVideoWebsitesWork
Back to Blog
Featured

DNS-DEX: The Exchange for Tokenized Domains

Richard Boase
|
5 min read
|3 February 2026|
TOKEN: dns-dex-domain-tokenization
.MD Source
dns-dex$402domain tokenizationweb monetizationbsv

Domain names generate value every day. Visitors arrive, consume content, use APIs, access services. That value has always been indirect — monetized through ads, subscriptions, or eventual sale.

DNS-DEX makes domain value direct and tradeable.

What DNS-DEX Is

DNS-DEX is an exchange where tokenized domain assets trade. It is not a platform that imposes rules on how you monetize. It is infrastructure that lets domain owners and investors find each other.

You own a domain. You decide:

  • What to charge for access
  • How to distribute revenue to token holders
  • Whether tokens grant access, dividends, both, or neither
  • What pricing model fits your business

DNS-DEX displays your terms and facilitates trades. That's it.

The $402 Protocol

DNS-DEX builds on the $402 protocol — an HTTP extension that adds three things to any URL:

Verification: A 3-proof bundle (DNS TXT record, /.well-known/path402.json, on-chain inscription) that proves you control the domain and defines its token.

Access Control: The ability to return HTTP 402 (Payment Required) when someone without tokens tries to access protected content.

Payment Rails: BSV micropayment infrastructure for instant, low-fee transactions.

The protocol is plumbing. It enables monetization without prescribing how.

Relationship to $402 Standard: DNS-DEX implements the $402 protocol for domain tokenization. The canonical $402 token standard defines default mechanics: tokens as reusable tickets, dividends only to stakers (KYC + path402d), holder-set pricing. Domain owners can customize within these parameters, but the standard provides sensible defaults and compliance framework.

Owner Decides Everything

The $402 protocol does not tell you how to run your business. You choose:

Pricing

Charge whatever makes sense:

  • Flat rate: 1p per page view, always
  • Per-use: 10 sats per API call
  • Tiered: Free tier, premium tier, enterprise tier
  • Market-driven: Let tokens trade freely, price discovery happens naturally
  • Curves: Early buyers pay more (or less), price adjusts with supply

Revenue Distribution

Split revenue however you want:

  • 100% to yourself (tokens are access-only)
  • Pro-rata to all token holders
  • Weighted: 70% to you, 30% to holders
  • Staker-only: Only infrastructure operators earn
  • Custom: Any formula that fits your model

Token Rights

Tokens can mean whatever you define:

  • Access rights: Hold tokens to view content
  • Revenue share: Receive dividends from domain income
  • Governance: Vote on domain decisions
  • Utility: Burn tokens to use services
  • Speculation: Trade based on expected future value
  • Any combination

Supply

Structure supply to match your goals:

  • Unlimited: Mint forever, price adjusts
  • Capped: Fixed supply, scarcity drives secondary market
  • Burn-on-use: Tokens consumed with each access
  • Inflationary: Scheduled minting to reward long-term holders

Examples

The API Provider

A developer runs api.weatherdata.io. They charge 5 sats per request. Revenue goes 100% to them — tokens grant rate limits, not dividends. Simple pay-per-use monetization.

The Content Creator

A blogger tokenizes techinsights.blog. They issue 10,000 tokens at 500 sats each. Holders get access plus 50% of all future revenue (from new token sales and per-article tips). Early supporters become stakeholders.

The Domain Investor

Someone owns premium.io but hasn't built on it. They tokenize it with 1 million tokens, keep 60%, sell 40%. Token holders get pro-rata share of whatever the domain eventually earns. The domain becomes a tradeable asset before any product exists.

The Community

A DAO tokenizes devs.community. Members buy tokens for access to private channels. Revenue from new member fees goes to existing holders. The community funds itself.

The Enterprise

A company tokenizes internal tools at internal.acme.co. Employees receive tokens as part of compensation. External partners buy access. Different tiers have different token requirements. Governance tokens let stakeholders vote on roadmap.

The $DOMAIN Namespace

DNS-DEX introduces a naming convention: $DOMAIN.tld

  • $GITHUB.com — if GitHub tokenized
  • $VERCEL.com — if Vercel tokenized
  • $b0ase.com — our own tokenized domain

The $ prefix signals "this domain has a tradeable token." It is a lookup in a global directory of monetized URLs.

What DNS-DEX Provides

Discovery: Browse tokenized domains, see their terms, understand what you're buying.

Trading: Buy and sell domain tokens. Market price reflects what participants think the domain is worth.

Verification: Every listed token has verified 3-proof bundle. You know the token actually controls the domain.

Transparency: See pricing model, revenue distribution, supply mechanics, governance rules. No hidden terms.

What DNS-DEX Does Not Do

Impose models: We don't tell owners how to price or distribute. Your domain, your rules.

Custody tokens: Trades settle on-chain. We facilitate, we don't hold.

Guarantee returns: Tokens are worth what the market says. Some domains will thrive. Others won't.

Replace judgment: Read the path402.json. Understand the terms. Make your own decisions.

Get Started

For Domain Owners

  1. Connect wallet at DNS-DEX.com
  2. Enter your domain
  3. Configure your token (name, supply, pricing, revenue split)
  4. Complete verification (DNS TXT, well-known file, inscription)
  5. Your domain is now tradeable

You keep full control. You set all the rules. DNS-DEX just makes your token visible and tradeable.

For Investors

  1. Browse listed domains
  2. Read the terms (pricing model, revenue distribution, access rights)
  3. Decide if the terms make sense for your goals
  4. Buy tokens
  5. Hold for access, dividends, appreciation — whatever the token provides

Every domain is different. Due diligence matters.

The Point

DNS-DEX does not believe in one right way to monetize a domain. Flat fees work for some. Curves work for others. Revenue share makes sense in certain contexts. Access-only tokens make sense in others.

The protocol enables. The owner decides. The market discovers value.

Your domain. Your rules. Your upside.

Visit DNS-DEX.com to tokenize or trade.

For AI Readers

Intent: Position DNS-DEX as a neutral exchange for domain tokens, not a prescriptive platform that imposes a single tokenomics model.

Core Thesis: $402 is a protocol that enables domain monetization. DNS-DEX is infrastructure for trading domain tokens. Pricing, revenue distribution, and token rights are policy decisions made by each domain owner — not protocol requirements.

Key Takeaways:

  • DNS-DEX facilitates trading; owners set their own terms
  • The $402 protocol is plumbing (verification, access control, payment rails)
  • Pricing model is owner choice: flat, curves, market-driven, usage-based
  • Revenue distribution is owner choice: pro-rata, weighted, staker-only, none
  • Token rights are owner choice: access, dividends, governance, utility
  • The $DOMAIN.tld namespace signals tokenized domains
  • Protocol enables, owner decides, market discovers
More Articles
Get in Touch