Shelby CDN

Decentralized content delivery network. Every piece of media and content in the Whop stack lives on Shelby: chart replay recordings, Feed articles, Whop Terminal data streams, backtest simulation datasets, vault strategy configs, ACE-encrypted content of all kinds.

Shelby is neutral storage with no access control logic. It stores ciphertext and serves it freely. ACE handles who can decrypt.

Access Control Integration

Old approach: Shelby as access controller. Shelby checks payment before serving content. Problem: Shelby must be trusted, must be online, can be hacked, can be misconfigured.

New approach (ACE + Shelby): Content ACE-encrypted before upload. Shelby stores and serves ciphertext freely. ACE committee controls key release based on Move contract state. Even if Shelby is fully compromised, the attacker gets useless ciphertext. The access control layer (ACE committee + Move module) is entirely separate from the storage layer (Shelby).

This is why the Aptos Labs ACE examples are named shelby-access-control-aptos. The two were designed to work together from the start.

Stored on Shelby

Historical OHLCV candle data: Shelby is the historical market data warehouse that the Indicator Marketplace Monte Carlo backtester runs against. Pyth provides real-time price feeds, while Shelby stores the years of historical candle data required for backtesting. The Terminal also pulls from Shelby's candle archive for indicator training. This makes Shelby load-bearing for the entire indicator ecosystem, not just for media storage.

Chart replay recordings: Every trade auto-screen-recorded and stored on Shelby. Byte-range serving native. Clips can be streamed from any position without downloading the full recording. Standard clips stored as plaintext. Premium extended replays and commentary stored as ACE ciphertext alongside.

Feed articles: Title and first paragraph stored as plaintext (always free). Article body stored as ACE ciphertext. Shelby serves the plaintext header freely. ACE committee releases the key for the body only when the reader has an active CA payment stream (FeedPayment Move module as ContractID).

Whop Terminal data streams: Real-time stream content stored and served by Shelby. ACE-encrypted for premium streams. Paying subscribers decrypt inline. Non-subscribers receive ciphertext.

Backtest simulation datasets: Full Monte Carlo datasets (10k equity curves, trade logs, drawdown distributions) too large for onchain storage. ACE-encrypted and stored on Shelby with a content hash committed onchain. The content hash is the tamper-proof pointer. If someone swaps the Shelby data, it won't match the onchain hash.

Vault strategy configurations: ACE-encrypted vault strategy parameters stored on Shelby or in the Move struct. Vault membership contract as ContractID. Stake = ProofOfPermission = decrypt.

Tamper-proof Onchain Read Logs

Every byte-range read is timestamped and logged onchain. This is the source of truth for Content Rewards view accounting. View counts cannot be inflated. Every ACE decryption event is also logged. Together these form the complete consumption accounting that Content Rewards distributes from.

The onchain log is append-only. Nobody can retroactively change a read record. The basis for weekly Content Rewards distributions is cryptographically verifiable by any party.

Byte-range Reads. The Partial Content Architecture

Shelby serves content at byte-range precision. This is native to the architecture, not bolted on. When a reader pays to unlock section 4 of a 10-section course, Shelby serves exactly those bytes and nothing else.

For ACE-encrypted content, the byte ranges map to ACE domains. Section 4 is encrypted as its own ACE domain. Paying for section 4 means requesting a ProofOfPermission for that specific domain. Shelby serves the corresponding encrypted bytes. ACE committee releases the key for those bytes only.

This enables: paying for section 4 of a course without buying sections 1-3. Paying for a specific paragraph in an article. Paying for one chart replay clip from a session without the full recording. The granularity of access control matches the granularity of the content structure.

DoubleZero Integration

DoubleZero integration for low-latency streaming of high-urgency Terminal content. Breaking market events, liquidation cascades, major price moves, need sub-second delivery. DoubleZero provides the edge delivery layer for Terminal's most time-sensitive streams.

Shelby as the Content Rewards Oracle

The flow:

1. 02Shelby records every read event onchain (timestamped, tamper-proof)
2. 04Every ACE decryption event is also logged (which domain, which address, when)
3. 06Content Rewards reads both logs
4. 08Weekly distribution: views × engagement multiplier × attribution split
5. 10Distributions flow as CA payment streams to .whop names

Shelby is the source of truth. ACE is the event trigger. Content Rewards is the distribution mechanism. Payment streaming is the rail.

Limitations

Shelby is not a payment gateway. It does not check balances or subscriptions before serving content. It does not know who has paid for what. It stores bytes and serves bytes. All access control logic lives in Move modules and is enforced by the ACE committee, not by Shelby's infrastructure.

Payment Streaming

Real-time CA micropayments by the second. Every monetization model on the Whop platform runs through one primitive payment rail.

Powered by Shelby

• ›Copy trading fees: Followers pay by the second while actively copying. Stop following = payment stops immediately. No retroactive charges.
• ›Indicator subscriptions: Creator earns per profitable signal fired. Revenue tied to performance, not subscriber count.
• ›Terminal stream subscriptions: Each stream is a separate per-second CA payment. Subscribers pay only while monitoring.
• ›Feed metered reads: Charged by the second while actively reading. Stop reading = payment stops.
• ›Vault revenue sharing: Earnings distribute to contributor .whop names in real time after each profitable close.
• ›Content Rewards distributions: Weekly creator pool distributions flow as CA payment streams.

The ACE Connection

The active CA payment stream is the ACE permission condition for all metered content. FeedPayment, TerminalStream, CopyPremium Move modules all check CA stream status. Stop paying = contract returns false = ACE committee stops releasing keys. Revocation is automatic and instant, no manual intervention, no delayed settlement, no disputes.

CA-private Amounts

All payment amounts are CA-confidential. Only the parties involved know the rates flowing between them. A follower's copy trading fee rate is invisible to the trader being copied. An indicator subscription rate is invisible to other subscribers. Vault distribution amounts are invisible to other contributors.

The fact that a relationship exists (Alice is copying Bob) may be visible for attribution purposes. The amount flowing through that relationship is never visible.

Significance

Payment streaming is not a feature. It's the business model architecture. Every product in the stack that involves ongoing consumption has a natural per-second payment model:

• ›Copy trading: pay for the signal, per second you're exposed to it
• ›Terminal: pay for the data, per second you're watching it
• ›Feed articles: pay for the analysis, per second you're reading it
• ›Indicator subscriptions: pay when it fires and works, not for the subscription itself

This is more honest than any existing subscription model. Users pay for exactly what they consume. Creators earn for exactly what delivers value. The alignment between payment and value is direct and immediate.

Reclaim ZkTLS

Zero-knowledge proof of HTTPS sessions. Proves facts about a web session without revealing the raw data. Works against any exchange or brokerage with HTTPS: Binance, Coinbase, Interactive Brokers, and any other platform.

Proof Capabilities

• ›Dollar PnL from the trader's actual exchange account
• ›Win rate
• ›Volume
• ›Streak
• ›Max drawdown
• ›Negative claims: "I have never had a losing month" can be proven, not just asserted

Whop never sees the raw trade data. The ZK proof attests to the claim against the real account. The proof is compact enough to store onchain alongside the UTT nullifier timestamp.

Why It's Load-bearing for Explorer

Reclaim is what separates Whop Explorer from every other trading leaderboard. Without Reclaim, the numbers on Whop Explorer are self-reported, no different from any existing platform. With Reclaim, the numbers are verified against the trader's actual exchange account without Whop ever seeing the raw data.

Two connections, both critical:

• ›Every PnL card's dollar figure is proven by Reclaim
• ›Explorer's entire leaderboard is built from Reclaim-attested stats

The Complementary Role With ACE

Reclaim proves off-chain web2 data (exchange account PnL) without revealing it. ACE controls access to onchain encrypted data. Together they cover the full privacy and verification stack:

• ›ACE: who can read onchain content
• ›Reclaim: what onchain stats are verifiably true from off-chain sources
• ›UTT: when the trade happened (onchain timestamp, cryptographic)

On-chain Indexer and QVAC

On-chain Indexer

The on-chain GraphQL indexer joins .whop name registry events to every onchain event by address in real time. When a signal fires, when a trade settles, when a chart replay recording is linked, when a Content Rewards distribution flows. All of these emit onchain events including the address. The indexer joins those events to the WhopRegistry record to enrich every event with the .whop name.

Single query example:

query {
  whop_identity(name: "max.whop") {
    address
    pnl_cards { ... }
    signal_calls { win_rate, avg_pnl, total_calls }
    kill_cam_clips { shelby_cid, views, contentrewards_earned }
    vault_positions { vault_name }
    indicators_deployed { name, version, live_sharpe, backtest_sharpe }
    feed_articles { title, read_count, earnings }
  }
}

New onchain event → indexed and queryable within seconds. Not batched daily.

QVAC

Natural language query layer over the full indexed identity graph. Reads on-chain indexed data and Shelby simultaneously. Every .whop name is a QVAC entity.

Example queries:

• ›"Show me all .whop traders with live Sharpe above 1.5 active for 90+ days"
• ›"Which vaults running RSI strategies have positive expectancy this quarter?"
• ›"Find max.whop articles where the trade setup they described was profitable"
• ›"Show me all addresses with both a .whop name and a .poly name and tell me if their trading behavior on Whop correlates with their prediction market accuracy on Polymarket"

The last query, cross-platform identity correlation, is something no existing platform can do because there is no shared identity layer. ANHS + the on-chain indexer is that layer. The more TLDs in the ANHS registry, the richer the cross-platform identity graph available to QVAC.

QVAC reads every account, every candle, every chart replay, every PnL card. Natural language search. QVAC may also be trainable on your own trading history. A personalized prediction layer on top of the public index.