Quick start
Six steps. Nothing is signed until the last one, and the step before it costs nothing and can be repeated as many times as you like.
Before you begin
Three things need to be true. None of them take long, and getting them right saves a failed launch later.
- A funded walletPhantom, Solflare or Backpack, holding enough SOL for the buys, the platform fee, the network fees and the rent that each new account costs. Keep a margin above the number the terminal quotes.
- Your token assetsThe image you want on the token, the name, the ticker, and any socials. Have them ready so the create form is one pass rather than three.
- A destination for the sweepThe address that unspent SOL returns to when the launch is done. Usually your main wallet. You can set it at the end, but deciding now is faster.
About the network
Every new account on Solana holds a small SOL deposit called rent. A launch creates the mint, the token accounts and the wallet accounts, so the total is always a little more than the buys alone. The terminal shows this before you sign.
The six steps
- 01
Connect your wallet
Open the app and choose Connect Wallet. Approving the connection lets the site read your address and ask for signatures later. It does not move anything, and it does not give the site your keys.
- 02
Create a token, or paste a mint
Fill in name, ticker, supply, decimals, image and socials to create a new token. If you already have one, paste its mint address instead and the create step is skipped entirely.
- 03
Build the wallet vault
Choose how many wallets buy and what each one spends. RELICLAUNCHER generates the keypairs in your browser, assigns roles, and randomises the amounts by default so the buys do not read as a single cluster.
- 04
Fund the wallets
Move SOL from your connected wallet into the generated ones. The vault shows the required total, the per-wallet amount, and which wallets are short.
- 05
Set the protection rules
Private bundle routing, transaction gating, allowlist mode and MEV protection are on by default. Leave them on unless you have a reason to turn one off, and read the protection page before you do.
- 06
Simulate, then execute
The pre-flight assembles the entire launch and reads it against current chain state. When the result looks right, execute. You sign, the bundle goes out, and the feed reports each stage until the slot confirms.
Worth knowing
The order of these steps is not arbitrary. Funding before simulation is what lets the pre-flight tell you the truth, because it reads the balances that will actually be used.
After the launch lands
Sweep what is left
Buy wallets almost never spend to zero. Slippage bands, rounding and unused reserve wallets all leave SOL sitting in accounts you do not want to manage. One-click sweep returns every unspent balance to the address you nominate.
Export the keys, or throw them away
The generated keypairs live in your browser. Export them if you intend to keep using those wallets. If you do not, sweep first and then clear them, because a keypair with nothing in it is still a keypair someone could find later.
Keep the record
The activity feed holds what happened and in what order. If a launch goes sideways, that record is the first thing to read, and it is what any support conversation will be about.
What a first launch looks like
Rough shape rather than a stopwatch. Most of the time goes on preparation, and the part that touches the chain is over quickly.
Cannot be undone
Once the bundle confirms, the token exists with the supply, decimals and authority settings you chose. Read the create page before you fill the form, not after.
Creating a token
Every field on the create form, and which of them you only get one shot at.