The whole build, end to end
The launch builder, the wallet vault, the bundle order and the pre-flight all run against what you actually enter. Nothing is stubbed.
RELICLAUNCHERLaunch ConsoleMainnet targetEarly accessGet early access
Launch console
Command centre
Build the token, fund the wallets, order the bundle and read the pre-flight, all from one screen. Everything below runs for real against local state. Signing opens when you connect a wallet.
Wallet balanceNot connectedThe balance reads from your wallet
Launches sent0Nothing has been submitted
Wallets in vault0Generated on the wallets surface
EnginePreviewSimulation runs, signing is closed
Make a launch
4 steps
Step 01
Create the token
Name, ticker, supply and the authorities you revoke on creation.
Step 02Fund the wallets
How many wallets buy, how much each spends, and how far the amounts vary.
Step 03Order the bundle
The mint and every buy assembled into one bundle aimed at a single slot.
Step 04Read the pre-flight
The whole launch is assembled and checked before a transaction exists.
Bundle 1 slotBuy wallets up to 20Pre-flight 0 SOLCustody your wallet
Recent activity
Empty
No launches yet
Your launches and their receipts land here the moment the first one confirms on chain.
What a receipt carries
ConfigurationEvery value you set, exactly as it was sent.recorded
SignaturesWhat your wallet signed, and when.recorded
SlotThe receipt comes from the ledger, not from the submission.from chain
Engine
Preview build
Bundle routeOrders every instruction into one bundle, aimed at a single slot.Preview
SimulationDry run against the order you built. No network, no signing.Live
ProtectionPrivate routing, gating, allowlist and MEV rules.Preview
CustodySigning keypairs come from your wallet. RELICLAUNCHER never holds them.Your wallet
Where things stand
Signing and submission
Keypair generation, signature requests and the send to the block engine arrive with the wallet adapter. Until then the console signs nothing and spends nothing.