StepsStep 3: Activate the vault
Step 3: Activate the vault
Deposit 100 million creator coins to fund your vault, create its shares, and split them for launch.
Activation is your first deposit. It funds the vault, creates the ShareOFT, and splits it for launch. After this, the app walks you through the remaining steps.
Make the deposit
- Open the deploy app and choose Activate.
- Enter your deposit: 100 million creator coins.
- Sign. The app uses one of two paths:
- Permit2 (preferred): one signature covers the deposit and the wrap.
- Approve, then activate: approve the batcher first, then activate.
The vault cannot activate or finalize unless the first deposit is 100 million coins.
What activation does
In one transaction (finalizePhase2), the batcher:
- Moves your coins into CreatorOVault and mints vault claims.
- Wraps those claims into ShareOFT.
- Splits the ShareOFT: 25% vesting to you over 365 days, 25% to Solana, 12.5% for the Base auction, 12.5% for Base liquidity, and 25% held for other chains. Details.
- Bridges the Solana 25% with LayerZero. The transaction's
msg.valuemust cover the LayerZeroquoteSendnativeFee; any surplus is refunded.
Your vault is now activated.
What finalize does not do
Activation doesn't start trading. It does not:
- Set up the earn strategy. Phase 3 registers the v4 pool at 80% and Morpho lending at 10%. Pool coins stay in the vault until the pool is configured. Vault manual.
- Schedule the auction. That is Phase 4 (
launchDeferredAuction). - Settle the auction or open trading.
migrate()and the other settlement steps run after the auction ends.
The app runs these in order after you activate: finalize, then strategies, then the auction. What happens next.
For developers: before finalize
finalizePhase2 needs the Phase 2 core contracts already onchain: the gauge, the CCA launch arm, and the oracle.
Before finalize hands over ownership, the payout router must be marked on the wrapper and set as fee-exempt on the ShareOFT. That has to happen while the batcher still owns those contracts.
deployPhase2Auxiliaries (burn stream, revenue router, revenue policy controller) requires the vault owner to already be the creator. On a fresh vault the batcher still owns it, so this can't run before finalize. It's not part of activation and doesn't schedule the auction.