Extensions to the Whop Name Service architecture covering fractionalization, revenue routing, and marketplace infrastructure.
The Three-tier Domain Hierarchy
Tier 1: User Identities
max.whop
One per Whop user. The personal trading identity. Every PnL card, chart replay, signal call, indicator strategy, and Content Rewards payment is permanently attributed here. This is the name that builds reputation over time. It is an Aptos object owned by the user's wallet.
Tier 2: Community and Business Identities
alphasquad.whop
One per Whop community or business. Every product sold under that community is a product subdomain under this name. The community name is the brand. Revenue from all products flows through this identity. This is the economic root of a Whop business.
Tier 3: Product Identities
alphasquad.whop/rsi-breakout
alphasquad.whop/options-flow
alphasquad.whop/vault
alphasquad.whop/feed
One per product. Each product is its own Aptos object, an NFT, with its own revenue stream, its own Content Rewards history, its own on-chain track record. Products are tied to their parent community name and cannot exist independently of it.
Mode 1: NFT Only (default)
Every .whop name and product subdomain launches in Mode 1. This is the standard, no-setup-required state.
What it means:
- ›The name is an Aptos object with a single owner
- ›All revenue generated routes 100% to the owner's address
- ›The name can be transferred (sold outright) like any Aptos object
- ›No fungible token exists for it
- ›No fractional ownership is possible
- ›No AMM, no secondary market for shares
This is the right state for most names. A user who registers max.whop to build a trading identity doesn't need a coin. A signal group creator who runs alphasquad.whop/signals just wants their subscription revenue. Mode 1 is zero overhead.
The fa_metadata field on the name object is None in Mode 1. Until someone creates an FA for this name, it is a pure NFT.
Mode 2: NFT + FA (opt-in Fractionalization)
Mode 2 activates when a fungible asset is created for a specific .whop name or product subdomain. This requires a deliberate action: either by the name owner themselves, or by a liquidity provider who believes in the name's future revenue.
What activates Mode 2:
- ›Someone calls
create_fa_for_name(name_address, total_supply, initial_price) - ›A new fungible asset is deployed whose metadata is attached to the name object
- ›The
fa_metadatafield on the name object is set fromNoneto the FA's object address - ›Revenue routing changes: all incoming payments now split proportionally across FA token holders
Why a liquidity provider and not just the owner? The owner might not want to deal with tokenomics. A liquidity provider who sees a signal group generating $30K/month can bootstrap an FA, acquire initial supply, and create a market in exchange for early token allocation.
FA Design for Mode 2
When an FA is created for a .whop name, the following parameters are set at creation and cannot be changed:
| Parameter | Description |
|---|---|
total_supply | Fixed at creation. Typically 1,000,000 units. |
decimals | 8 (standard Aptos FA precision) |
name | Full name, such as "AlphaSquad RSI Breakout" |
symbol | Optional. Set by the creator at deployment. Not auto-assigned. |
initial_allocation | How initial supply is distributed (see below) |
The symbol is not automatic. There is no ticker auto-created when alpha.whop is registered. If someone bootstraps an FA for alpha.whop and wants to call the token ALPHA, they set that symbol when deploying the FA. The canonical FA for a name is stored in the name object's fa_metadata field, not inferred from a naming convention.
Initial allocation options:
- ›Bonding curve launch (recommended): Initial supply is sold via the same bonding curve as the Indicator Marketplace launchpad. Price discovery happens before the FA is fully distributed.
- ›Direct distribution: Owner receives 100% of initial supply and sells manually.
- ›LP seeded: LP receives initial supply in exchange for bootstrapping the first AMM pool.
Revenue Routing: Both Modes
The RevenueRouter handles all payment distribution. In Mode 1 it routes everything to the owner. In Mode 2 it becomes a proportional split.
Streaming Distribution (Mode 2: Active Income)
Every CA payment stream that flows through a .whop name, copy trading fees, indicator earnings, Feed paragraph reads, Content Rewards distributions, hits the router at payment time and splits proportionally.
Payment: 0.01 APT copy trade fee arrives at alphasquad.whop
FA total supply: 1,000,000 tokens
Holder A (creator): 700,000 tokens → receives 0.007 APT
Holder B (investor): 200,000 tokens → receives 0.002 APT
Holder C (investor): 100,000 tokens → receives 0.001 APT
Protocol fee: 1 bip taken before split → 0.000001 APT to ANHSThis is real-time. There is no claiming step. CA micropayments route directly to each holder's address at the moment the payment occurs.
Checkpoint Dividend Model (Mode 2: Lump-sum Income)
For large one-time revenue events, a course sale, a bulk vault distribution, an indicator license sale, the streaming model creates too much gas overhead for splitting across many holders. Instead a dividend checkpoint is created.
Holders can batch-claim multiple checkpoints in one transaction. Unclaimed dividends are held in escrow on the name object.
The Subdomain Revenue Hierarchy
Revenue flows through three levels: product → community → protocol.
alphasquad.whop [community root. Mode 1 or 2]
│
│ Revenue flowing TO root:
│ ├── 5% flow-up from all subdomain revenues
│ └── Direct revenue: community subscriptions, etc.
│
├── alphasquad.whop/rsi-breakout [product NFT. Mode 1 or 2]
│ ├── Revenue: 0.5 APT per profitable signal fired
│ ├── 95% → RSI-Breakout FA holders (Mode 2) OR creator (Mode 1)
│ └── 5% flows up to alphasquad.whop root
│
├── alphasquad.whop/vault [product NFT. Mode 1 or 2]
│ ├── Revenue: 3% management fee on vault profits
│ ├── 95% → Vault FA holders (Mode 2) OR creator (Mode 1)
│ └── 5% flows up to alphasquad.whop root
│
└── alphasquad.whop/feed [product NFT. Mode 1 or 2]
├── Revenue: 50% of paragraph read fees (via ContentRewards)
├── 95% → Feed FA holders (Mode 2) OR creator (Mode 1)
└── 5% flows up to alphasquad.whop rootEach level is independently in Mode 1 or Mode 2. The community root can be Mode 1 (owner keeps all 5% flow-up) while a specific product like rsi-breakout is Mode 2 (investors hold FA tokens). These are independent decisions at each level.
Why Fractionalize
For the Name Owner
A signal calling community generating $50K/month is a business worth $500K-$600K at a 10-12x revenue multiple. But the owner cannot access that capital without selling the business entirely.
Mode 2 enables partial liquidity:
- ›Owner fractionalizes
alphasquad.whopinto 1,000,000 tokens - ›Sells 200,000 (20%) via bonding curve for $100K raised
- ›Keeps 800,000 (80%) economic interest and full operational control
- ›Investors receive 20% of all revenue in perpetuity or until they sell their shares
This is tokenized revenue-share in a Whop business. The token represents economic interest in cashflows, not legal ownership of a business entity.
The 90-day minimum: A community name must be active for at least 90 days before Mode 2 can be activated. No fractionalization of fresh names with no track record.
For the Investor
Explorer shows every name's on-chain revenue history. An investor who believes in alphasquad.whop/rsi-breakout, based on its backtest vs live Sharpe history, signal frequency, chart replay record, can buy a fraction of that specific strategy's future revenue without exposure to the rest of the community's products.
For the Liquidity Provider
A liquidity provider who bootstraps Mode 2 for a name:
- ›Deploys the FA contract and sets initial supply parameters
- ›Seeds the first AMM pool (FA token / APT) to create immediate liquidity
- ›Earns LP fees from trading activity in that pool
- ›Earns early token allocation as compensation for the bootstrapping work
Secondary Market: Name Trading
Outright Name Sales (both Modes)
A .whop name object can be transferred like any Aptos object. The Whop Name Marketplace provides a UI for listing names at a fixed price or via auction. When a name sells:
- ›The object changes owner
- ›All future revenue routes to the new owner
- ›The on-chain track record (PnL history, signal history, chart replays) stays permanently attached, and it cannot be separated or deleted
- ›If the name is in Mode 2, the FA tokens are separate from the object. The buyer gets the name but not the existing FA token holders' economic interest
FA Token Secondary Market (Mode 2 Only)
FA tokens for a fractionalized name trade on their AMM pool (FA token / APT). Anyone can buy or sell at any time.
Bonding Curve Launch for New FAs
When a Mode 2 FA is first created for a name, a bonding curve provides initial price discovery before the full AMM opens, identical to the Indicator Marketplace launchpad's graduation curve.
The Whop Name Marketplace
A dedicated Whop Appstore web app for browsing, trading, and fractionalizing .whop names. Attached to your Whop page and accessed through the browser, like Content Rewards.
Browse views:
- ›Available names (unregistered, recently expired, auction listings)
- ›Active FA tokens (Mode 2 names with live secondary markets)
- ›Trending names (recent follower growth, PnL growth, Explorer search traffic)
- ›Recently sold names with prices (price discovery)
Per-name detail page:
- ›On-chain revenue history (trailing 12 months, sourced from Explorer)
- ›Verified trade count and PnL (Reclaim-attested)
- ›Active product subdomains and their individual revenue histories
- ›Implied valuation (auto-computed from revenue multiple, see below)
- ›Current FA token price and market cap (if Mode 2)
- ›FA token holder distribution (top holders, LP pool depth)
Implied valuation computation: Explorer data gives trailing annual revenue for any active name. The marketplace computes:
Monthly revenue × 12 = ARR
ARR × revenue_multiple = implied_valuationRevenue multiples are derived from comparable name sales on the marketplace. Names with 12+ months of consistent on-chain revenue use higher multiples. New names use conservative ones. No self-reporting, and all data is on-chain.
Authority, Discoverability, and Search Ranking
WNS search is not alphabetical. Ranking is a function of the economic and social weight attached to a name.
Factors that raise search rank:
- ›Verified trade count (UTT-timestamped, immutable)
- ›Total verified PnL (Reclaim-attested)
- ›Follower / subscriber count (social signal)
- ›Content Rewards earned (economic weight)
- ›Chart replay view count (content engagement)
- ›Age of the name (time-in-system premium)
- ›Number of active product subdomains
- ›Revenue flowing through the name's payment channels
Names as Search-optimized Storefronts
Every WNS name gets a canonical Explorer URL: explore.whop.com/max.whop. This page is:
- ›The complete verified trading identity (all PnL cards, chart replays, Sharpe history)
- ›The product catalog (all subdomains and their track records)
- ›The subscription entrypoint (buy copy trading, subscribe to signal group, fund indicator, join vault)
- ›The Content Rewards showcase (top-performing content)
Google indexes this page. A signal caller with a high-ranking name gets organic discoverability outside of Whop.
Protocol Revenue: the 1 Bip Fee
Every transaction routing through any .whop name generates a 1 basis point protocol fee:
- ›40% burned as APT (same burn mechanic as name registration fees)
- ›40% to ANHS treasury (operational costs, IBE committee workers for ACE)
- ›20% to Aptos Foundation
Implementation Phases
Phase 2: Community Names and Revenue Routing
Goal: Every Whop community and business gets its own community .whop name. Multi-level revenue routing activates.
What ships:
- ›Community name minting (requires existing Whop community)
- ›Subdomain creation (
community.whop→community.whop/product) - ›
RevenueRouterwith subdomain 5% flow-up - ›Mode 2 activation for community names (with 90-day minimum activity requirement)
- ›FA bonding curve launch for new community name FAs
- ›Basic secondary marketplace (buy/sell/auction names)
- ›Content Rewards integration at subdomain level
Phase 3: Product Subdomains and Full Financial Stack
Goal: Every product on Whop has its own product subdomain with independent Mode 1 / Mode 2 state.
What ships:
- ›Product subdomain minting (gated by community name ownership)
- ›Product-level Mode 2: individual indicators, vaults, signal groups, courses can each have independent FAs
- ›Full AMM liquidity for Mode 2 names
- ›Dividend checkpoint model for bulk revenue events
- ›Full secondary marketplace via Whop Appstore
- ›Implied valuation auto-computation from Explorer data
- ›QVAC integration: WNS data queryable from Explorer
- ›Verified track record gating: product FAs require 6-month on-chain history and minimum Sharpe threshold before listing publicly