Launch for a creator.
Route them the fees.

Launch a token

1. Connect a BNB Chain wallet or launch through the WIRED Telegram bot.
2. Select Flap and choose BNB, a catalog pair, or a verified custom BSC token contract.
3. Enter the token metadata and upload a PNG, JPEG, WebP or GIF of up to 5 MB.
4. Select a supported creator identity or one of WIRED’s fixed charity destinations.
5. Choose an optional deployer buy, review the prepared transaction, and sign only after checking every field.

Browser launches are wallet-signed and the connected wallet pays deployment gas. A launch is recorded only after WIRED confirms the successful onchain receipt.

BNB launchpads and pairs

Flap catalog: BNB, USDT, USD1, U, BTCB, SOL, SPCXB, SKHYB, SPYB, XAUT, QQQB, NVDAB, AAPLB, TSLAB, MSFTB, GOOGLB, HOODB, BABAB, GMEB, NFLXB, MSTRB and DJTB.

A custom Flap pair must be a valid deployed BSC ERC-20 with readable decimals, symbol and a non-zero supply. WIRED verifies it before preparing the launch. Four.meme does not accept arbitrary unregistered pairs through WIRED.

Fee accounting

The applicable policy is locked into each confirmed launch. Flap trading fees are discovered from onchain evidence and reconciled idempotently so the same fee event cannot be counted twice.

Every claim, payout, bridge, buyback, and burn pays its own confirmed network cost from the allocation that caused it. One recipient never subsidizes another. Unused gas reserve remains credited to the same allocation, and accounting fails closed if an operation cannot cover its own cost.

The 30% reserve buys WIRED and sends the purchased tokens to the burn address. A buyback is not reported as burned until both transactions are confirmed onchain.

Social integrations

A launch names one recipient platform and account. WIRED verifies control of that exact identity before creator fees can reach a bound payout wallet. Beta integrations use the same payout safeguards while their public-proof flows continue to be hardened.

Fomo mappings are resolved once through FomoScan and stored permanently. GitHub verification stores the stable numeric user ID so later username changes do not redirect a claim. Platform handles and proof URLs are validated against the selected service before verification.

Verify a recipient

The recipient enters the exact identity used by a confirmed launch. WIRED generates a time-limited, one-time challenge. The recipient publishes it through the selected platform’s supported proof method and submits the public proof. SoundCloud artists and Twitch channels place the challenge in their public profile bio. Telegram Personal uses a private bot handshake.

Identity verification and wallet binding are separate steps. The payout wallet must sign WIRED’s exact binding message; entering an address alone is not sufficient. Fomo is automatic through its proof-verified attached wallet.

Claim fees

1. Open Claims and select the same platform and identity used by the launch.
2. Complete the platform proof and bind the BNB-compatible payout wallet with a signature.
3. Load the currently claimable, reconciled amount and press Claim available fees.
4. WIRED records the payout only after onchain confirmation.

Fomo payouts are automatic. WIRED displays only balances backed by current launchpad and onchain reconciliation evidence.

Verified charities

Charity destinations are fixed in WIRED’s registry; launchers cannot substitute an address. Charity launches require no social-account verification and create no buyback reserve.

For St. Jude, WIRED accumulates its allocation until the net distribution reaches $100. Relay and destination-chain costs are deducted only from St. Jude’s own distribution, with a configured cost ceiling; no creator, charity or platform account pays another account’s gas.

Telegram launch bot

The bot launches through Flap and supports the same creator and charity destinations as the website.

1. Use /launch to begin.
2. Enter metadata, upload an image or send - for the default WIRED image.
3. Choose the recipient and a verified pair. BNB is the standard pair; /pairs shows the live catalog.
4. Review the full preview, then confirm live execution.

Other commands: /pairs, /cancel and /help. Website and X URLs are validated, recipient identifiers must match the selected platform, and nonsense pair values are rejected before preview.

Deployer position manager

Wallet Deploy positions held by the imported wallet can be opened from the bot with /positions. Balances and sell previews are loaded live from BNB Chain.

Available sell sizes are 10%, 25%, 50%, 75% and 100%. The app requests token approval when needed, obtains a live Flap sell preview, applies minimum-output protection and asks for confirmation before signing. Quick Deploy creates no deployer position because its initial buy is always zero.

Wallet behavior

• Browser: the connected BNB wallet signs its launch and pays BNB gas.
• Switch wallet: revoke the current site permission, clear the connection, then connect again.
• Telegram Wallet Deploy: import only an EVM private key inside the secure wallet web app—not in Telegram chat.
• Telegram Quick Deploy: no imported user wallet is required and WIRED covers deployment gas.

The imported private key is encrypted on the user’s device. WIRED stores ciphertext and the public address, rejects plaintext key storage, and never requests a seed phrase or recovery phrase.

Explorer and burn recorder

The explorer lists confirmed BNB launches with token metadata, pair, launchpad, recipient, contract address, creator allocation and public market links. Launch records remain stable while live market fields can refresh independently.

The burn recorder separately shows confirmed BNB spent, WIRED acquired, tokens sent to the burn address, and transaction proof links. Prepared or failed operations never appear as completed burns.

Safety and execution

• Verify the chain, destination contract, transaction value, pair and fee recipient before signing.
• A prepared or simulated transaction is not a completed launch. Completion requires a successful onchain receipt.
• Submitted and uncertain broadcasts are reconciled before any retry to prevent duplicate execution.
• Fee observations and payout operations are idempotent and fail closed when evidence or funding is insufficient.
• Never paste a private key or seed phrase into Telegram chat, the website, or support messages.
• Tokens and third-party launchpads carry smart-contract, liquidity and market risk.