Build your wallet list
Generate fresh wallets in your browser or import keys for wallets you already control. Each wallet has its own address.
THE LAUNCH CLUB GUIDE
Multi-wallet launches.
One workspace.
Create your token, prepare your wallets, and plan every opening buy from one place. Multi-wallet support is the core of Launch Club.
Generate or import walletsCustomize every purchaseBack up & track balances
THE CORE EXPERIENCE
Your wallets, one launch plan.
You are not limited to a single developer wallet. Build a list of separate launch wallets, choose what each one buys, and review the complete plan before you commit.
Set each purchase
Fill the list with shared defaults, then adjust individual amounts. Updating purchase settings keeps existing addresses and keys.
Keep track afterward
Link wallets to their launched token, keep a CSV backup, and check saved wallet balances from your creator account.
TWO WAYS TO LAUNCH
Same multi-wallet focus.
Different launch styles.
Direct V4
Launch straight into a Uniswap v4 pool, without a bonding curve or graduation phase.
- You choose
- Initial ETH liquidity and the exact token amount for each wallet.
- Who pays
- The connected creator wallet funds liquidity, all first buys, fees, and gas. Recipient wallets do not need ETH for these first buys.
- How buys complete
- Token creation and all configured first buys succeed together in one transaction. A failure reverts the launch; network gas can still be charged.
- Networks
- Ethereum Sepolia, Robinhood Chain testnet, and Robinhood Chain mainnet, subject to deployment availability.
Pons V2 Bundler
Launch on the Pons curve with ETH or an approved paired asset, followed by independent wallet buys.
- You choose
- A developer buy and a purchase amount in the paired asset for each opening wallet. Zero opening wallets is also supported.
- Who pays
- The connected wallet pays for the launch and developer buy. Each opening wallet needs its purchase funds and ETH for gas; review funding before launch.
- How buys complete
- The launch and developer buy are atomic. Opening wallets buy independently after launch confirms—not in the same atomic transaction. Fills, priority, and same-block execution are not guaranteed.
- Network
- Robinhood Chain mainnet only. Requires a connected wallet that supports atomic transaction batches.
GET STARTED
From idea to a ready wallet list.
Give your token an identity
Choose your launch method and network, then add a name, ticker, description, image, and social links. Use an image URL or the file picker when uploads are available.
Configure your opening wallets
Choose a wallet count and shared purchase amount, then generate the list. Direct V4 uses token amounts; Pons V2 uses amounts of ETH or the selected paired asset. Fine-tune individual rows afterward.
Review addresses and back up keys
Use the pencil beside an address to enter a private key; select OK to apply it or cancel to keep the original wallet. Pons also accepts a wallet-key CSV. Download the latest backup whenever the wallet list changes.
Check costs, then launch
Connect the creator wallet on the correct network and refresh the estimate. For Pons, review any wallet funding or paired-asset approvals and authorize the opening buys. Check every amount before approving the launch in your wallet.
Shared defaults update the whole list.
Changing the common purchase amount also replaces individual amount edits. Existing addresses stay the same. Replacing or reducing a wallet list requires confirmation; keep its backup before you proceed.
BEFORE YOU APPROVE
Every wallet counts.
So does every fee.
0.05 ETH. One launch. All your wallets.
Direct V4 and Pons V2 both charge a flat 0.05 ETH platform launch fee, paid by the connected creator wallet. It is charged once per token launch—not per wallet. Adding opening wallets does not increase this platform fee.
Liquidity, token purchases, trading fees, and network gas are separate. Pons V2 also has its own on-chain Pons launch fee, shown separately before approval. The platform fee is not your total launch cost.
Direct V4: automatic ETH budgets
You set token amounts, not a maximum ETH value for every wallet. The app calculates purchase budgets and shows liquidity, purchases, pool fees, applicable buy fees, the 0.05 ETH platform launch fee, and estimated network gas. Unused purchase ETH is refunded.
The estimated cost and the balance needed upfront are different: your wallet needs room for purchase buffers and gas reserves. Initial liquidity is pool funding, not a platform fee. The latest estimate is checked again before signing.
Both launch methods use the same platform-fee receiver. This is separate from your token’s buy/sell-fee receiver, which still defaults to the token creator. If the configured platform destination and the Direct V4 factory disagree, new launches are paused until they match.
Buy and sell fees default to 0% and can be set from 0–10%. The initial-buy fee toggle controls whether the buy fee also applies to launch purchases. Per-wallet estimates show its effect; sell fees do not apply to first buys.
Pons V2: purchases and gas by wallet
The plan separates the developer buy, opening-wallet purchases, the flat 0.05 ETH platform launch fee, the additional on-chain Pons launch fee, and estimated gas. Trading fees are already included in purchase amounts. Your connected wallet shows the final transaction-batch gas fee before approval.
For non-ETH pairs, purchases stay in the selected asset and network costs stay in ETH. They are not combined using an assumed exchange rate. Each opening wallet needs ETH for its own gas; unused funding remains in that wallet.
YOUR LAUNCH WORKSPACE
Backups, balances, and a record of every wallet.
After a confirmed launch, generated and imported wallet keys are sent over HTTPS for encrypted server storage. Records are linked to the creator, token, network, and launch method, so Direct V4 and Pons V2 wallets remain clearly distinguished.
Open Profile and sign in with the original creator wallet to access saved records and check balances. Exporting stored private keys requires a fresh signature. Changing or renouncing token ownership does not transfer access to these records.
Keep an offline backup. Saved keys are not self-custody-only.
The server operator can decrypt stored private keys. Your CSV also contains private keys: keep it private and offline. Use dedicated launch wallets, never a seed phrase or a main-wallet key.
If saving fails after launch, keep the CSV and retry the save—do not launch the token again. Unsaved keys can be lost on refresh. Balance reads can be delayed or fail; check their status before relying on them. Saved records do not authorize automatic trading.
AFTER LAUNCH
Your launch is only the beginning.
Explore shows launches for the connected creator, not a shared feed of everyone’s tokens. Your saved wallet records are available separately from Profile.
For Direct V4, open the token’s trading page to trade, check activity and holders, or view pool identifiers and ownership status. Liquidity locks, LP burn, and ownership renunciation are manual actions on that page—not automatic launch settings. Other wallets can view status but cannot use controls they do not own.
Pons V2 shows the progress of individual opening buys and offers a downloadable launch report. Near graduation, review the additional warning before continuing. If the curve closes, unsent buys stop; confirmed purchases are not rolled back.
A LITTLE HELP
Common questions.
Is the first wallet always my connected wallet?
No. The connected wallet is the creator and launch payer. Generated wallet rows have their own addresses and keys. In Direct V4 they receive tokens; in Pons they make separately funded opening purchases. The Pons developer buy belongs to the connected wallet.
Why is the launch button disabled?
Check the selected network, token details, wallet count, saved CSV backup, and current cost estimate. Finish any inline key edit or image upload first. Pons also requires an atomic-capable wallet, enough funds in the opening wallets, and your authorization for their buys. The creation page explains any remaining requirement.
Can I change the wallet list after generating it?
Yes. Update individual purchases, import a replacement key, or change the wallet count before launch. Replacing or removing wallets requires confirmation where keys would be discarded. Download an updated CSV afterward. Once a launch is submitted, you cannot change that transaction’s wallet list.
Does multi-wallet mean every buy happens in the same transaction?
Only for Direct V4’s configured first buys. With Pons V2, the launch and developer buy succeed together, but opening wallets send separate transactions afterward. Some may succeed while others fail or remain unsent.
What happens when I regenerate wallets?
A new list creates new addresses and keys. It does not move funds out of the old wallets. Keep the old CSV so you can still access them, and download the new one before launching.
KNOW WHAT YOU CONTROL
Safety & permissions.
Review the network, every wallet address, amounts, fees, and permissions before signing. Mainnet uses real assets. Transactions are irreversible, prices can move, and failed transactions can still consume gas. Multi-wallet support does not guarantee execution priority or returns.
Liquidity locks, LP burn, and token ownership
New Direct V4 liquidity starts unlocked. On the trading page, the eligible creator can choose a timed lock, permanent locker custody, or LP burn. Timed locks require a duration and cannot be shortened. Expiry allows release of the position; it does not automatically withdraw liquidity.
Permanent locker custody has no scheduled release but remains subject to locker upgrades. LP burn instead permanently gives up control of the position and its fees; it does not reduce the token supply. Renouncing token ownership is a separate irreversible action: existing fees remain, but token-owner fee and receiver changes are disabled. Liquidity rights are separate.
Token ownership and platform upgrade permissions
Direct V4 token contracts are not upgradeable. The current Sepolia platform infrastructure is upgradeable by one administrator, without a multisig or timelock. That administrator can change infrastructure behavior, including fee and liquidity-locker rules. Renouncing a token does not remove those powers.
Pons V2 uses the official Pons contracts through an independent Launch Club interface. Launch Club does not control their administrator settings and is not operated or endorsed by Pons. Do not treat the interface or a successful test as an independent security audit.
More information: Privacy policyTerms of use