Deployment Methodology
Exactly what happens when you launch a token through LARP, including every signature and fee.
8.1 Summary
This section is written plainly. Deploying an asset through LARP creates a real token on Solana. The transaction is constructed by the LARP server, signed by your wallet, and executed by the network.
8.2 Steps
- Connect a Solana wallet (Phantom, Solflare, Backpack or any Wallet Standard wallet). LARP receives only your public key.
- Complete the form: name, ticker, description, image, and optional links and developer buy.
- Select Review. The server normalises your ticker, reverses it, uploads metadata, builds the transaction, and simulates it against the network to estimate the exact SOL cost.
- Review the fees and approvals shown on screen. Nothing has been signed at this point.
- Select Execute. Your wallet displays the transaction. Approve it to proceed, or reject it to cancel.
- The signed transaction is broadcast. The interface waits for confirmation and only then reports success, with the mint address, signature and explorer links.
8.3 Launch providers
| Provider | Networks | What is created | Developer buy |
|---|---|---|---|
| spl (default) | devnet, mainnet | SPL mint (6 decimals, fixed supply minted to you), Metaplex metadata; mint authority revoked; no freeze authority | Not applicable |
| pumpportal | mainnet only | pump.fun bonding-curve token via PumpPortal's local-transaction API | Optional, in SOL |
The provider is selected by server configuration (LAUNCH_PROVIDER). Mainnet is refused unless LARP_ENABLE_MAINNET=true.
8.4 Transaction integrity
The reversal is applied on the server. The server generates a fresh mint keypair, includes the reversed symbol in the token metadata instruction, and signs the transaction with the mint key before returning it. Any modification of the transaction by the client would invalidate the mint signature, so the deployed symbol is the reversed one. The mint key is used once and discarded; it is never your key and grants no control over your wallet.
8.5 Failure states
- Rejected in wallet: nothing is broadcast and nothing is charged.
- Simulation failure (for example, insufficient balance): shown before signing; nothing is charged.
- Expired blockhash: the interface prepares a fresh transaction automatically.
- Confirmation timeout: the transaction may still land. The signature is shown so you can check the explorer. LARP does not report success until confirmation is observed.