Documentation

A token launched through IGE Pad behaves like any other token on its chain. On Solana it is deployed through Raydium, so it shows up on the aggregators people already use. On BNB Chain, Ethereum, Arbitrum and Robinhood Chain it is deployed as a standard ERC-20 with a v3 liquidity position on PancakeSwap or Uniswap.

What is different is where the trading revenue goes. Creator fees accrue to a protocol-controlled position, are claimed on a schedule, converted into the reward asset the creator chose at launch, and distributed pro-rata to eligible holders.

Four products share one wallet session, one data model and one fee ledger.

You provide a name, ticker, icon, an optional 300-character description, socials, the quote asset, the amount of tokens seeded into the pool and the reward configuration. IGE Pad then builds the deployment for the venue you picked and asks your wallet for a single approval.

Launch jobs are durable: if a transaction expires before confirmation the job rebuilds and resubmits it rather than losing your funds. Once the pool is live the token is indexed and appears on the IGE landing board automatically.

Two separate things are chosen at launch, and they are often confused:

Tokenized stocks cannot be used as a bonding-curve quote mint, so stock exposure is delivered on the reward side: the protocol market-buys the stock token with the holders' share of the fees and distributes it. That is why a launch can be "backed by" a stock while still trading against a liquid quote asset.

The 50% floor is enforced in the launch form and again on the server - a configuration that pays holders less than half is rejected.

The reward engine runs unattended on a scheduler, per chain, per token. A cycle only starts once accrued fees cover the platform share, the creator share and the holder distribution combined - never before. Nothing is claimed early and nothing is claimed partially.

1. 01Fees accrue to the protocol-held creator position (Solana) or v3 LP position (EVM).
2. 02Once the combined threshold is met, the engine collects the fees on-chain.
3. 03The platform share is taken first.
4. 04The remainder is split: creator share to the creator wallet, holder pool to the reward buy.
5. 05The holder pool is market-bought as the reward asset on the chain's own venue.
6. 06A holder snapshot is taken and each eligible wallet's slice is computed pro-rata.
7. 07Slices above the auto-send floor are transferred immediately; the rest becomes claimable.

Each chain is an independent adapter with its own operator wallet, treasury wallet, RPC set and ledger. A cycle on BNB Chain never touches Solana funds and vice versa.

Eligibility is decided by the creator at launch and enforced by the snapshot, not by anyone's discretion.

On EVM, balances are reconstructed from Transfer logs and then verified against a live balanceOf read before any transfer is signed.

A slice above the auto-send floor is pushed to the wallet without any action. A slice below it becomes a manual claim, shown on the token page and claimed by signing a message with the holding wallet - no gas-heavy approval, no custody handover.

IGE Swap aggregates routes across the major venues on each supported chain and executes in-app - you sign in your own wallet and are never redirected to a partner site. The pay card supports 25 / 50 / 75 / max quick amounts and a clear action. The protocol fee is 0.50%.

IGE Bridge moves value between Solana and the supported EVM networks. The quote, fee and ETA are shown before you sign, a custom recipient wallet can be set per transfer, and completion is detected through a multi-RPC failover with a direct receipt fallback so a transfer is never reported as pending after it has landed. The protocol fee is 0.25%.

Keys never leave your wallet. Launches, swaps, bridges, locks and claims are signed by you. Protocol operator and treasury wallets exist per chain purely to execute fee collection, reward buys and distribution - they never hold user balances and never have authority over a launched token's supply.

Every Solana mint deployed through IGE Pad ends with the base58-legal suffix iGE, mined at launch time, with a best-effort venue prefix letter. EVM deployments use CREATE2 vanity mining for the 975 suffix. Verification deployments always use the name Test IGE and the ticker TIGE, so they are trivial to tell apart from real launches.

Every token description written through IGE Pad ends with Launched on IGEProtocol.fun.

The audit page runs a live end-to-end check and produces a downloadable Markdown report: RPC health per chain, DEX contracts, operator and treasury wallets, quote assets, fee tiers, the token icon upload and public-URL validation pipeline, and the rewards database.

The API page documents each live chain independently: transport, venue, launch flow, public endpoints and code samples. Protocol earnings are not shown there - those live on the Revenue page, broken out per chain.

• Tokens launched here are permissionless. IGE Protocol does not vet, endorse or guarantee any launch.
• Reward assets - including tokenized stocks - carry their own issuer, market and liquidity risk.
• A reward cycle only runs when fees reach the combined threshold; a token with no volume pays nothing.
• Unclaimed manual balances are forfeited after 30 days.
• On-chain execution can fail or expire; failed pre-mint launches are refunded, but network fees are not recoverable.