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 or a pair from Flap’s live catalog.
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 launchpad and pairs

WIRED loads Flap’s current BNB quote-token catalog directly from Flap and refreshes it every five minutes. BNB is the default. Symbols and approved catalog addresses resolve to the same verified entry.

Live Flap pairs: Loading…

Flap’s Portal rejects contracts outside that catalog with QuoteTokenNotAllowed, so arbitrary BSC contracts cannot be used as launch pairs.

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. 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. Patreon creators place it in their public About section. Weibo creators publish the challenge in a public post; WIRED stores the stable numeric UID and fails closed when Weibo presents visitor verification. 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 an approved pair. BNB is standard and /pairs loads Flap’s live catalog.
4. Review the full preview, then confirm live execution.

Live Flap pairs: Loading…

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

Tap 🇨🇳 中文版 or send /cn for the complete Chinese flow. Send /en to return to English.

X launch bot

Tag @wiredup_bot with @wiredup_bot launch "Token Name" $TICKER. The default pair is BNB, the thread image becomes the token image, and the root-post author is the default fee recipient.

Chinese syntax is also supported: @wiredup_bot 发行「代币名称」 $TICKER 交易对：BNB. Supported Chinese labels are 交易对：, 接收方：, 网站：, 推特：, 描述： and 慈善：. Replies follow the command language.

Optional fields are pair:, recipient:, website:, x:, description:"..." and charity:. Pair accepts a symbol or contract address from Flap’s live BNB catalog. Recipient accepts a full supported social-profile URL. The x: field sets a different X profile/post in token metadata. Description accepts up to 500 characters and must be quoted. Charity accepts giggle or stjude.

Live Flap pairs: Loading…

The bot launches without a confirmation reply, prevents repeat triggers within the same conversation, and posts the contract address, pair, recipient and Flap link after confirmation. Each X account can complete one launch every four hours.

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 and X Quick Deploy: no imported user wallet is required. WIRED covers deployment gas and the initial buy is fixed at zero.

WIRED never requests a private key, seed phrase or recovery phrase through either launch bot.

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.