Your launch control room.
Verify the platform token, lock its fee routing, and manage rounds from your wallet.
Coin creation is closed.
Launch from your creator/admin wallet
Loading…Your wallet will show network and account costs before approval.
Prepare Turkeypad ($TURKEY) at with the owner launch below. Creation and the locked 90/10 split execute in the same transaction.
Prepare now. Launch with fees already locked.
The atomic owner launch installs the permanent split: 90% competition fund / 10% operations. Only the creator/admin wallet signs. The recipient wallets do not need approvals.
- 90% · Competition fund
- 10% · Operations
Prepare the address table ahead of time if needed. The final wallet approval launches the token with its fee routing already installed. Load only the reserved mint key locally; never share a wallet seed phrase.
Protocol fee-sharing detailsPublic coin creation can run during platform setup. The platform token, fee routing, and indexer checks track the remaining setup.
Ready from the first trade.
Create Turkeypad ($TURKEY) at the reserved mint and lock 90% competition fund / 10% operations in one atomic transaction. Any optional dev buy executes after the split is locked.
Loading…Creator/admin walletLoading…1. Prepare before launch
Preparation builds and simulates the complete launch. The final transaction creates the token and locks the fee split in a single wallet approval.
Configure Turkeypad’s 90/10 split
The creator/admin wallet signs the permanent 90% competition fund / 10% operations split after $TURKEY launches. The transaction sweeps accrued fees before locking the recipients. Existing locked configurations are inspected and never overwritten.
Waiting for the current platform status. Refresh to check again.
Required creator/admin wallet
Loading…Reserved $TURKEY mint
Loading…Competition fund wallet
Receives 90% of the platform token’s creator fees. Funds equal team buybacks.
COMPETITION_FUND_WALLETOperations wallet
Receives the remaining 10% for operations and funding.
OPERATIONS_WALLETManual platform buyback wallet
Receives 30% of creator fees from every user-launched coin. You handle $TURKEY buybacks and burns manually.
PLATFORM_BUYBACK_WALLETInternal platform mint
The mint used by the existing platform fee and launch configuration.
PLATFORM_TOKEN_MINTOperator wallet
The public address allowed to finalize elections and submit verified receipts. This can be your fund wallet.
OPERATOR_WALLETTurkeypad creator / admin wallet
The wallet authorized to configure the platform token’s creator-fee split.
PLATFORM_CREATOR_WALLETSolana RPC & indexing
Dedicated Alchemy mainnet RPC. A hosted Cloudflare scheduler checks finalized trades every minute and saves indexing progress in the site database.
SOLANA_RPC_URL + INDEXER_SECRETHosted indexer
Waiting for the hosted scheduler’s first check.
No registered coins yet. The scheduler is idle and makes no indexing RPC calls until coins launch.
Election defaults
Hourly polls close on the hour UTC. The team with the highest qualifying SOL trading volume wins. Its top three registered coins by market cap at close each receive one third of the budget. New coins can win in their launch hour; there is no minimum trade or trader count for the podium. Ties or fewer than three priced coins carry the fund forward. Party buybacks require operator approval; platform-token buybacks from the 30% wallet are manual.
Complete the platform mint launch and its locked 90/10 fee setup above. Election settlement requires current indexing. All signing stays in your wallet.
Distribute accrued creator fees
Anyone can trigger the on-chain distribution to the locked recipients. The connected wallet pays only network and account costs. This does not change fee shares.
Finalize an election
Use the configured operator wallet. Allow two minutes after the hour for final indexing. Settlement uses the closing market-cap snapshot and creates equal budget allocations; it does not move funds. Only one incomplete round can reserve the fund at a time.
Register an on-chain receipt
The server verifies finalized protocol purchases and actual token burns. Purchase amounts are in lamports; burn quantities are raw token units. A signature can only be recorded once.