coordinated batch
All 36 club markets use one verified configuration and one operational batch-broadcast target. Current Raydium LaunchLab InitializeV2 has no future open_time/startTime field, so exact same-second activation cannot be guaranteed; each market becomes active when its Initialize confirms.
coordinated batch
7 qualifier slots pending
NOT SCHEDULED
SOL per curve
pre-graduation target
The 29 automatic qualifiers can be prepared now. The final seven token identities stay blocked until the Champions League play-off winners are known.
Create all 36 fixed-supply mints, finalize metadata, revoke mint/freeze authority according to policy and publish every contract address before trading.
Use the pinned Raydium SDK and the same verified economic parameters for every club. Do not persist stale signed transactions: rebuild with a fresh blockhash close to the coordinated broadcast target.
Send the 36 Initialize transactions in one controlled launch window. LaunchLab has no deferred-open field, so each curve becomes active when its own transaction confirms; exact same-second activation is not promised.
Every club uses the same supply, quote asset, creator-fee policy, curve family and scheduled opening timestamp. The only differences are club identity, ticker, logo and final mint address.

Prepared for the common launch manifest once the mint, metadata and authority checks are complete.

Prepared for the common launch manifest once the mint, metadata and authority checks are complete.

Prepared for the common launch manifest once the mint, metadata and authority checks are complete.

Prepared for the common launch manifest once the mint, metadata and authority checks are complete.

Prepared for the common launch manifest once the mint, metadata and authority checks are complete.

Prepared for the common launch manifest once the mint, metadata and authority checks are complete.

Prepared for the common launch manifest once the mint, metadata and authority checks are complete.

Prepared for the common launch manifest once the mint, metadata and authority checks are complete.

Prepared for the common launch manifest once the mint, metadata and authority checks are complete.

Prepared for the common launch manifest once the mint, metadata and authority checks are complete.

Prepared for the common launch manifest once the mint, metadata and authority checks are complete.

Prepared for the common launch manifest once the mint, metadata and authority checks are complete.

Prepared for the common launch manifest once the mint, metadata and authority checks are complete.

Prepared for the common launch manifest once the mint, metadata and authority checks are complete.

Prepared for the common launch manifest once the mint, metadata and authority checks are complete.

Prepared for the common launch manifest once the mint, metadata and authority checks are complete.

Prepared for the common launch manifest once the mint, metadata and authority checks are complete.

Prepared for the common launch manifest once the mint, metadata and authority checks are complete.

Prepared for the common launch manifest once the mint, metadata and authority checks are complete.

Prepared for the common launch manifest once the mint, metadata and authority checks are complete.

Prepared for the common launch manifest once the mint, metadata and authority checks are complete.

Prepared for the common launch manifest once the mint, metadata and authority checks are complete.

Prepared for the common launch manifest once the mint, metadata and authority checks are complete.

Prepared for the common launch manifest once the mint, metadata and authority checks are complete.

Prepared for the common launch manifest once the mint, metadata and authority checks are complete.

Prepared for the common launch manifest once the mint, metadata and authority checks are complete.

Prepared for the common launch manifest once the mint, metadata and authority checks are complete.

Prepared for the common launch manifest once the mint, metadata and authority checks are complete.

Prepared for the common launch manifest once the mint, metadata and authority checks are complete.

Placeholder only. Do not create immutable public metadata until the play-off winner occupying this slot is known.

Placeholder only. Do not create immutable public metadata until the play-off winner occupying this slot is known.

Placeholder only. Do not create immutable public metadata until the play-off winner occupying this slot is known.

Placeholder only. Do not create immutable public metadata until the play-off winner occupying this slot is known.

Placeholder only. Do not create immutable public metadata until the play-off winner occupying this slot is known.

Placeholder only. Do not create immutable public metadata until the play-off winner occupying this slot is known.

Placeholder only. Do not create immutable public metadata until the play-off winner occupying this slot is known.
Programmatic LaunchLab createOnly configuration using the pinned SDK. No deferred startTime/open_time field is assumed.
Every club market settles against the same quote asset.
LaunchLab constant-product curve type 0, with a planned CPMM migration path after graduation.
Set at the current planning floor to reduce the total capital burden created by launching 36 markets at once. Verify live Raydium limits before signing.
80% curve allocation and 20% reserved for the migration path.
No hidden project first buy and no founder club-token inventory.
36 × 24 SOL. This is cumulative trader/community quote capital required if every curve eventually graduates — not a project launch expense.
Illustrative minimum-path fee volume if aggregate buy-side flow equals the combined graduation target at 0.35% creator fee. Actual two-way trading can be higher or lower.
Illustrative at 50% official-link attribution. The 0.1% LaunchLab referral is separate from project creator-fee revenue and applies to LaunchLab-page trading attributed to the referral.
Illustrative creator Fee Key income per 10,000 SOL post-grad volume using the current modeled CPMM fee split. Read the live Platform PDA / pool fee config before mainnet.
Cold governance, reserve custody and temporary mint/freeze authority. Never use for routine claims.
Creates all 36 scheduled LaunchLab markets and holds creator Fee Keys before project revenue is forwarded.
Dedicated wallet for initial $UCL/SOL liquidity and LP/Fee-Key custody. Kept separate from Club Coin creator operations.
Receives project creator-fee revenue before the fixed 50/30/20 settlement.
Receives the 50% rewards share only.
Receives the 30% buyback share only; executions stay public and volume-aware.
Receives the 20% marketing share only.
Receives disclosed founder referral income. It never receives the project 50/30/20 creator-fee flow.
0% launch unlock, 12-month cliff and 24-month linear vesting.
Disclosed LaunchLab referral income from trades attributed to official project launch links goes to the Founder Operating wallet.
Creator-fee revenue still goes to Rewards / $UCL Buyback / Marketing. Founder referral income remains separate.
Exactly 36 named clubs; no CP/LP qualifier placeholders remain
One operational batch target is fingerprinted for coordination; it is not an on-chain deferred-open field
Supply, decimals, metadata and contract addresses independently verified
Mint/freeze authority state verified before public trading
Collector → 50/30/20 test settlement confirmed on-chain
Club-name/logo and project-brand usage cleared or changed before immutable metadata
Actual public-offer/admission-to-trading structure reviewed for MiCA obligations
Fees, referral mechanics, founder allocation, mints and wallet roles published before trading
Resolve the final field, finalize 36 token identities and metadata URIs, verify all base-mint signers and current LaunchLab config, then build and simulate every createOnly request before any broadcast. The operational target coordinates the batch; it does not delay activation on-chain.