Product documentation

How LevLaunch works.

From instrument configuration to a verified fixed-supply token on Solana Mainnet.

01 / product model

A market thesis with a token identity.

Every LevLaunch instrument starts with four decisions: a reference market, LONG or SHORT, a multiplier label, and a fixed-supply token. Together they form the instrument profile shown across the builder, Explorer, metadata, and instrument page.

Market
BTC/USD, ETH/USD, SOL/USD, NVDA/USD, TSLA/USD, or GOLD/USD.
Direction
LONG or SHORT as the creator's stated market view.
Multiplier
1X, 2X, 3X, 5X, or 10X as part of the named instrument profile.
Token
A standard fungible SPL token with immutable Metaplex metadata and fixed supply.
Important distinctionThe market, direction, multiplier, and entry price describe the LevLaunch instrument. The SPL token contract does not rebalance, settle, redeem, or automatically track the selected reference market. Its market price is established only through genuine external trading liquidity.
02 / launch flow

One builder. One Mainnet transaction.

  1. Connect. Use Phantom or Solflare on Solana Mainnet.
  2. Configure. Select the market, direction, multiplier, token name, ticker, image, and fixed supply.
  3. Capture. LevLaunch reads the current reference price from Pyth Pro and records it as the entry price.
  4. Review. The wallet shows the standard Solana token and metadata instructions before signing.
  5. Launch. The transaction creates the mint and creator token account, mints the full supply, creates immutable metadata, and removes mint authority.
  6. Verify. LevLaunch checks the Mainnet transaction, supply, authorities, and metadata PDA before adding the instrument to Explorer.
03 / token and metadata

Standard Solana programs.

LayerProgramRole
TokenTokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DACreates the fungible mint and creator token account, mints the fixed supply, then removes mint authority.
MetadatametaqbxxUerdq28cj1RbAWkYQm3ybzjb6a8bt518x1sCreates immutable name, ticker, URI, and fungible-token metadata linked to the mint.
LevLaunch registryApplication datastoreStores the creator, instrument profile, entry price, image, mint, signature, and creation time after on-chain verification.

LevLaunch does not require a custom Mainnet program deployment for this launch architecture. The archived Rust program is not called by the web launch path.

04 / market prices

Reference prices from Pyth Pro.

LevLaunch requests server-side Pyth Pro prices for all six supported markets. Crypto, US equity, and gold feeds use stable Pyth Lazer identifiers. The entry price and publication time are persisted when the launch is prepared. If a current price cannot be read, launch remains unavailable for that market rather than displaying an invented value.

05 / trading

Liquidity must be real.

LevLaunch does not create a pool, order book, or initial buy. BUY and SELL open only when the instrument has a genuine Jupiter route. Until a route exists, the controls remain disabled and price, market cap, volume, and holder metrics stay blank unless a verified data provider supplies them.

Venue swap fees, slippage, and price impact belong to the selected route and are shown by the venue at trade time. They are not part of the token creation transaction.

06 / internal archive

Collateralized derivatives research.

The repository retains a separate Anchor program for paired claims, collateral vaults, Pyth settlement, offers, redemption, and series PDAs. That implementation remains isolated for future protocol work and is not an active dependency of the current product launch path.

Its specifications and verification records remain in the repository's internal engineering documentation.