Launch status and rollout
What is built, what is pending, and how the site switches from prelaunch to live.
Pre-launch, and clear about it.
The deployed configuration splits the 4% protocol fee 1% holders, 1% liquidity, 1% staking and 1% operations, fixed in the treasury program with no setter. 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 | Unnamed. Launch on degen.zone pending the 4% creator tier |
| 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 fee stream and the post-graduation position 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.