GlossaryChapters
Reference

Glossary

Every term used across these pages, defined for someone who does not read transactions. One line first, then the part that actually matters.

Nothing here assumes prior knowledge. If a definition uses another term from this list, that term has its own entry.

Worth knowing

Three of these do most of the work: slot, bundle and block engine. Read those first and the rest of the documentation stops being jargon.

AllowlistA list of addresses allowed to buy while the gate is open.
Used when the opening window belongs to specific people rather than the open market. It controls addresses, not people, so an address on your list can pass its allocation to anyone.
Block engineThe route a bundle takes to reach the validator building the block.
Instead of broadcasting to the whole network and hoping, a bundle is handed to the block engine, which delivers the ordered set to the slot leader. This is what keeps a launch off the public path while it is in flight.
Bonding curveA pricing formula where the price rises as more is bought.
There is no pool to seed and no liquidity to provide. The curve itself prices the token as a function of how much has been purchased, so early buyers pay less than later ones by construction. pump.fun style launches work this way.
BundleA group of transactions that land together, in order, or not at all.
The core of what RELICLAUNCHER does. The create instruction and every buy are ordered into one bundle aimed at one slot. Nothing can be inserted between them, and if any part fails, none of it is applied.
DecimalsHow finely one token divides.
Six decimals means one token splits into a million parts. Nine matches SOL. Zero means whole tokens only. It is set once at creation and cannot be changed afterwards.
Freeze authorityThe right to freeze a specific holder's token account.
Whoever holds it can stop a chosen address from sending the token, which means stopping them selling. Traders check for it within seconds of a launch. Most launches revoke it permanently at creation.
Front runningSeeing a transaction coming and getting in first.
The reason bundles exist. A create transaction broadcast on the public path is visible before it settles, and anyone watching can buy the opening supply before the person who created the token does.
LamportThe smallest unit of SOL.
One SOL is one billion lamports, the way one dollar is one hundred cents. Fees and rent are often quoted in lamports because the amounts are so small, and it is a unit rather than a separate currency.
MEVValue extracted by controlling the order of transactions.
Short for maximal extractable value. If someone can decide what executes before and after your transaction, they can profit from that position. A sandwich attack is the most common form and MEV protection exists to make your buys a bad target for it.
MetadataThe name, ticker, image and links attached to a token.
Uploaded before the mint so the token never appears unnamed. Unlike supply and decimals, metadata stays editable as long as you hold the authority for it.
MintThe account that defines a token, and its address.
The mint is the token's identity on Solana. Its address is the only reliable way to refer to a token, because tickers can be duplicated by anyone and frequently are.
Mint authorityThe right to create more of the token after launch.
Whoever holds it can dilute every holder at any time. Revoking it at creation fixes the supply permanently, which is what most fair launches do and what the terminal does by default.
Priority feeAn optional extra paid to move a transaction up the queue.
When block space is contested, a priority fee raises your transaction's position. It goes to the network, not to RELICLAUNCHER, and it is shown separately in the cost breakdown.
RentA deposit every account holds to exist on Solana.
Not a charge. It sits in the account and comes back when the account is closed. A launch creates many accounts, so the rent adds up and needs to be funded before anything else happens.
Sandwich attackBuying just before your transaction and selling just after it.
The attacker profits from the price movement your own buy created, and you fill worse than you should have. MEV protection is aimed directly at this.
SlippageHow far the price is allowed to move before a buy refuses.
Set it at one percent and a buy that would fill more than one percent worse than quoted fails rather than accepting the price. Tight slippage protects you and makes failure more likely. Loose slippage does the reverse.
SlotOne turn to build a block, roughly four hundred milliseconds.
Each slot has one leader who decides the order of everything in it. Two transactions in the same slot have a fixed order and nothing can be inserted between them, which is exactly why a bundle targets one slot.
SniperAn automated buyer waiting for new tokens to appear.
Snipers watch for launches and buy the opening supply within milliseconds. They are the reason the gap between a create and a buy matters, and the reason bundling closes it.
SPL tokenThe standard a Solana token follows.
Every token RELICLAUNCHER creates is an SPL token, which is why every wallet and explorer already knows how to display it without anything being registered anywhere.
SweepReturning unspent balances from the generated wallets.
One click walks every generated wallet, sends what is left to an address you nominate, and closes the accounts it can so their rent comes back with it. It moves SOL and does not sell tokens.
TipWhat a bundle pays for inclusion in a slot.
Inclusion is competitive, and the tip is what decides whether your bundle wins the slot against others. It goes to the network. RELICLAUNCHER takes no share of it.
Wallet adapterThe standard way a Solana site talks to your wallet.
The site asks for a signature and the wallet decides whether to give one. Your key never enters the page, which is why connecting is safe and approving is the step that matters.
Ready

Open the terminal

Connect a wallet and run your first simulation. It costs nothing.

Launch App