ANHS Architecture

The Problem With Existing Onchain Names

.apt names (Aptos Name Service) have one use case today: send payments and look up addresses. Nobody knows what .apt names are because there's no product built on top of them. They're a utility primitive with no consumer-facing surface.

The goal is not to compete with ANS. The goal is to build the consumer identity layer that makes .apt names matter to non-crypto users. By wrapping them in a product context (Whop, Polymarket, Decibel) that 50+ million users already use.

The Architecture: Two Layers, One User Experience

The .apt suffix exists purely at the infrastructure layer. At every product surface, your own resolver intercepts the lookup and strips it.

The mapping is:

max.whop  →  (WhopRegistry)  →  max.whop.apt  →  (ANS)  →  0x3f2e...

Users see max.whop everywhere in Whop products. Wallets that read ANS natively see max.whop.apt and resolve correctly. The .apt is a transport detail, not a user-facing string. The same way HTTP exists under every URL but users just see whop.com.

Aptos Name Hosting Service (ANHS)

The canonical TLD authority on Aptos. Not a competitor to ANS. Built on top of it. Companies pay to register a TLD slug in ANHS. ANHS holds the corresponding parent .apt domain and delegates subdomain creation to its own contract.

Any project with users can register a TLD. ANHS handles:

• ›Minting and managing all subdomains
• ›Bidirectional name ↔ address resolution
• ›Transfer and expiration logic
• ›Secondary market royalty routing
• ›Cross-TLD primary name resolution
• ›All APT value accrual mechanics

TLD Registration Model

Companies pay 1000 APT to register a TLD:

• ›Whop pays 1000 APT → registers .whop → ANHS acquires/holds whop.apt
• ›Polymarket pays 1000 APT → registers .poly → ANHS acquires/holds poly.apt
• ›Decibel pays 1000 APT → registers .decibel

TLD owners earn 20% of every per-name minting fee from names in their namespace. This incentivizes Whop to actively promote .whop name adoption. Every user who mints a name puts APT back into Whop's treasury.

Per-name Minting. Atomic Single Transaction

When a user registers max.whop:

1. 02User pays ~1 APT
2. 04ANHS creates a WhopRegistry record: max.whop ↔ 0x3f2e...
3. 06ANHS mints max.whop.apt on ANS in the same transaction (ANHS holds whop.apt as parent)
4. 08User never sees .apt. It exists at infrastructure layer only
5. 10max.whop.apt now resolves natively in Petra, Backpack, any ANS-compatible wallet
6. 12Whop UI shows max.whop. .apt stripped by frontend resolver

The user pays once. The APT fee covers the ANS subdomain minting cost, the burn, the TLD owner cut, and the ANHS treasury cut. All in one transaction.

APT Value Accrual Mechanics

This is the structural reason ANHS matters for the Aptos ecosystem.

Every name registration burns APT:

• ›TLD registration (1000 APT): 40% burned · 40% ANHS treasury · 20% Aptos Foundation
• ›Per-name minting (~1 APT): 30% burned · 30% ANHS · 20% TLD owner (Whop) · 20% Foundation
• ›Annual renewal (0.5 APT/year): 50% burned · 30% ANHS · 20% TLD owner
• ›Secondary market royalty (5% of sale): 50% burned · 50% ANHS

Annual renewal creates continuous APT demand. Names expire. Renewal requires APT. This is recurring demand, not a one-time purchase. At 21 million .whop names renewing at 0.5 APT/year, that's 25 million APT in annual renewal demand partially burned every cycle.

The conversion funnel: Whop has 21 million users. For many of them, registering a .whop name is their first APT purchase. A low entry point makes this the largest potential APT user onboarding funnel in the ecosystem.

Length-based pricing:

• ›1-3 characters: 100 APT/year
• ›4 characters: 20 APT/year
• ›5 characters: 5 APT/year
• ›6+ characters: 1 APT/year

Initial launch: Whop mints 21M names for all existing users. Users get a claim window to claim their username for free. Unclaimed names go to an auction period where anyone can bid. All names from the initial mint expire after 1 year, at which point they come back to market at the standard pricing above.

.whop Names as the Identity Layer

.whop names are not just usernames. They are the identity layer across every Whop product.

Onchain identity: Every PnL card, chart replay clip, signal group call, vault, indicator, and Feed article is permanently attributed to a .whop name onchain. Trading reputation is portable and human-readable. max.whop with a 1.8 Sharpe over 18 months is a brand with genuine secondary market value.

Payment routing: All CA payment streams are routed to .whop names, providing human-readable destinations throughout the platform. Copy trading fees stream to max.whop. Vault distributions flow to contributor .whop names. The payment destination is the name, not the address.

Explorer search: Type max.whop in Whop Explorer and get the full verified profile. Trades, signals, indicators, vaults, clips, articles. The .whop name is the primary key for all identity queries.

Content attribution: Every Content Rewards distribution, every chart replay view, every metered article read. Permanently attributed to the .whop name onchain. The name accumulates economic history.

Indicator namespace: max.whop/rsi-breakout-v2 is a URL-style identifier for a deployed strategy. The indicator's reputation is tied to the creator's .whop name across all versions.

ACE allowlist access control: ACE allowlist contracts can gate by .whop name. "only alphasquad.whop members can decrypt this vault strategy." .whop names make ACE access control human-readable: grant access to max.whop, not 0x3f2e....

Vault identity: alphasquad.whop/vault is the vault's Explorer profile, chart replay library, PnL history, and Content Rewards attribution anchor.

The Wallet Resolution Problem

Until Petra and other Aptos wallets support the ANHS resolver, .whop is a product-internal identity layer. External users type max.whop.apt to send from outside Whop products.

Resolution approaches:

1. 02

   Wallet resolver standard. Publish an open ANHS resolver standard for Petra, Backpack, and Rumble Wallet. When a user types max.whop, the wallet checks the WhopRegistry contract and resolves it. Any TLD registered in ANHS gets wallet resolution for free once the standard is adopted.

2. 04

   Parallel TLD recognition. ANHS recognized as a parallel TLD under the ANS resolution standard. max.whop resolves natively as a real Aptos name.

3. 06

   Product-first, wallets follow. .whop is the product-internal identity. max.whop.apt is the external fallback. Ship with no wallet coordination required, integrate wallet resolution as it becomes available.

The right path is option 3 first, option 1 simultaneously. Ship the product now. Get wallets later.

.whop Names Go-to-market

20 million existing Whop users get free 1-year registration. Every existing Whop user's username is reserved as their .whop name, automatically claimed for 1 year at no cost. If no one renews after the first year, the name goes to a marketplace for secondary purchase. This creates immediate network scale (20M names claimed on day one) and a secondary market from day one (expired names from inactive users go to auction).

Partial product auctions. Businesses and indicator sellers can sell partial amounts of their products via auctions using their .whop name as the identity anchor. A signal caller can auction the right to be in the first 10 copy slots (lower latency, earlier fill). An indicator creator can auction early access to a new strategy version. The .whop name makes the auction provably attributed to the right creator.

1 basis point fee on all .whop name transactions. Every payment, subscription, vault distribution, or indicator earnings stream that routes through a .whop name generates a 1 bip (0.01%) protocol fee. At $691M annual GMV already flowing through Whop, 1 bip = $691K/year from existing flows alone. Scaling directly with platform volume. Alternative: tiered fee based on account tier (premium .whop names unlock lower fees).

Whop Appstore app for .whop names market. A dedicated Whop Appstore web app (browser-based, attached to your Whop page) specifically for browsing, buying, and selling .whop names. Like Content Rewards, it is a Whop Appstore app, not a native mobile app. This is the secondary market surface. High-reputation names with verified track records become valuable assets, and the Appstore app is where they trade.

1. 02Register whop.apt on ANS to establish position cheaply
2. 04Deploy AptosNameHostingService contract with TLD registration, per-name minting with atomic ANS subdomain creation, renewal logic, and burn mechanics
3. 06Deploy WhopRegistry contract
4. 08Integrate .whop name display into Whop Explorer, PnL cards, chart replay attribution, Feed articles
5. 10Demo: max.whop resolves in Whop Explorer, max.whop.apt resolves in Petra
6. 12Take demo to Aptos Foundation. Formal partnership ask, co-marketing for .whop launch
7. 14Open hosting service to other Aptos projects. Decibel, Econia, Thala

ANHS for Other Aptos Projects

When Polymarket launches .poly, their names are automatically indexed in the same identity graph infrastructure. max.poly gets a profile page. QVAC can reason about Polymarket traders. Cross-platform queries become possible: "show me addresses with both a .whop name and a .poly name."

Each new project that joins adds their users' activity to a cross-platform identity graph no single project could build alone.

APT demand at scale: Whop has 21 million users. Even 1% conversion at 1 APT per name is 500,000 APT in demand in the first wave. At full scale, 21M names at 1 APT renewal per year is 21M APT in annual demand. Nobody else has a realistic path to that many new ANS-linked names.

Indexability

.whop names being indexed means the name is the primary key for everything that has ever happened onchain associated with that identity. Trades, signals, vault positions, content, earnings, chart replays, indicators.

The indexer joins .whop name registry events to every on-chain event by address in real time. One query: whop_identity("max.whop") returns the full cross-contract history.

Every contract emits events including the address. The indexer joins those events to the .whop name registry. Every event on-chain gets enriched with the .whop name of the address that triggered it.

QVAC queries using .whop names as entity identifiers across all indexed data. The more TLDs in the ANHS registry, the richer the identity graph for QVAC queries.