Protocol

Architecture

A component-level map: the fee router claims SOL, the acquisition engine buys 15 stock tokens, the reserve wallet holds them, and the redemption engine settles proportional baskets.

Components

Fee router: claims verified creator fees in SOL and measures only the newly received amount.
Acquisition engine: splits claimed SOL equally across the 15 registered stock tokens.
Backing pool: the Solana wallet holding the acquired stock tokens.
Redemption engine: computes proportional payouts from execution-time state.
Eligibility ledger: tracks verified purchases, sales and cumulative claimed value per wallet.

Data layer

Solana
   ↓
RPC / indexing layer
   ↓
Protocol data service   (typed reads, caching, retries)
   ↓
Frontend                (renders slot + timestamp of last read)

The frontend caches read-only data briefly and always displays how old that data is. On RPC failure it renders an explicit error state rather than stale numbers presented as live.

Integration boundary

Where the external fee infrastructure cannot natively route fees to a program-owned account, the protocol uses a verification layer: it observes receipts to the designated fee destination, records the receipt and deploys only newly claimed SOL into reserve stocks.

Oracle and data requirements

Reserve balances: the 15 registered SPL stock-token balances held by the pool wallet.
Circulating supply: the $STOCKED SPL mint supply.
Fee receipts: SOL transfer history to the designated fee destination.
Stock prices: live quotes used to value each holding in dollars.
$STOCKED market price: external market data, always labelled separately from backing.