Launch status and rollout
What is built, what is pending, and how the site switches from prelaunch to live.
Live, and clear about what is not.
A trade on the degen.zone curve pays about 4.19% all in. About 0.34% of that goes to degen.zone, about 0.84% to Meteora, and the rest, about 3.02% of volume, reaches the protocol. After graduation, at about 80 SOL raised, trading moves to a Meteora DAMM v2 pool that charges 1% regardless of the curve tier. Meteora keeps 20% of that, and the rest is split by liquidity share between the protocol's locked position and degen.zone's, so about 0.52% of volume reaches the protocol. The protocol's take per trade falls at graduation. It funds holder payouts in tokenized stocks, protocol-owned liquidity, a staking reserve and operations, in a fixed ratio the treasury program enforces. Staking itself is planned, phase 2: the allocation is set aside, but no staking program is deployed and nothing accepts a deposit. Values that have not been read from the chain render as a dash with the reason beside them.
Current status
| Area | Status |
|---|---|
| Wallet connection | Available |
| dr_distributor | Built and tested; not deployed to mainnet |
| dr_treasury | Split, allowlist, flash-fill and epoch funding built and tested; liquidity vault in progress |
| Keeper | In progress |
| Token | Named Flux Vault / $FLUX. Launch on degen.zone's creator tier pending |
| Stock pools | Rollout SPYx → NVDAx → TSLAx → GOOGLx approved, none created |
| Staking | Phase 2 |
| Independent security review | Not completed |
The launch sequence
- A single transaction creates the Meteora Dynamic Bonding Curve pool and transfers the creator role to a treasury program address, so the curve's creator fee stream, and later the creator's locked position in the graduated pool (65% of its liquidity; degen.zone's own locked position holds the other 35%), belong to the program from the first trade.
- The treasury and distributor are initialised by the upgrade authority; the stock allowlist and reward mints are added after each is checked on chain.
- The keeper starts; the first epoch publishes when the first cycle has something to distribute.
- Protocol pools open one at a time, each gated on depth.
How this site goes live
The site reads a deployment file and a launch manifest from a mounted volume. Until the manifest says active and names a reviewed release, every page shows the prelaunch state. Flipping to active is a file write plus a chain read; no rebuild, and the pages converge within seconds. An active manifest without a reviewed release is refused.