A clear route to market.

01 / Launch from the website.

Connect a Solana wallet and sign an authentication message. Add the name, ticker, square logo, and optional description and project links. SOL is the default pair. Choose your wallet or an X recipient for the creator share.

The website flow remains wallet-funded. Review saves a persistent request, prepares a Pump.fun transaction, and simulates account rent and network costs. Your wallet signs the exact reviewed message. Live signing and submissions remain disabled pending operational approval; browser drafts are available.

02 / Start with a mention.

Tag the configured bot on X and name the recipient:

@Relayonchain launch $DOG for @creator

Replace DOG with a ticker of 1–10 letters or numbers. The ticker becomes the token name. Replace @creator with the recipient’s X handle. The longer syntax, “launch DOG paired with SOL for x:@creator”, is also supported. Links, extra payment instructions, and recipient overrides are rejected. TikTok recipients remain disabled.

RELAY resolves the recipient to a permanent X account ID and saves one request per post. The requester follows the request link, connects a Solana wallet, reviews costs, and signs the launch transaction. The requester pays all launch costs. RELAY does not fund launches. Social-recipient requests require supported, verified fee routing before authorization. Once live operations are authorized, confirmed launches receive an X reply with the mint and Pump.fun link and appear in the terminal.

Automatic launch execution is not active yet. Accepted requests remain on record while operational approval is pending. There is no required creator endorsement before launch.

Claim your fees from X.

Coming soon: post from your creator account with your existing Solana fee-wallet address.

@Relayonchain claim fees YOUR_SOLANA_WALLET

Replace YOUR_SOLANA_WALLET with the creator wallet shown in your dashboard. Complete account verification once before your first post claim. RELAY checks the permanent X account ID, so renaming a handle does not change who owns the fees. Subsequent eligible post claims need no website sign-in or wallet connection.

RELAY is preparing to cover network costs within sponsorship limits. A claim sweeps the latest associated token and collects available shared creator-vault fees into the existing fee wallet. Unswept fees from other tokens may require a token-specific dashboard claim. RELAY replies with the transaction only after confirmation. No bonus or guaranteed amount is offered.

A post cannot replace the fee wallet or authorize a managed-wallet withdrawal. Use secure dashboard access for withdrawals. This is a Solana fee-collection feature, separate from planned X Money payouts. Live post claims are disabled pending operational approval.

03 / Who covers the costs?

Users fund and sign their own launches, whether they start on the website or on X. RELAY does not cover launch costs.

There is no RELAY platform deduction or transfer tax. Pump.fun’s protocol fee schedule, account rent, and Solana network fees still apply. Creator fees are the eligible creator share, not all trading fees. No initial token purchase is included in RELAY’s creation transaction.

A reserved budget is not a completed payment. Signed transaction bytes are saved before submission. Failed or uncertain transactions retain their budget reservation for operator review.

04 / Paired with SOL.

RELAY currently supports the official Pump.fun SOL creation path. It checks the deployed program and token-creation configuration before preparation. Other pairs are not enabled simply because a post requests them.

05 / The named recipient gets the creator share.

An X handle is a lookup hint, not a payment address. RELAY binds the recipient to their permanent X ID and a Solana fee wallet. Pump.fun’s actual creator field is set to that wallet, separately from the launch payer. RELAY checks the on-chain creator configuration before publishing a new launch.

A verified recipient can associate an external wallet. If no fee destination exists, that wallet becomes the destination for future launches. Where configured, a user-owned Privy wallet can be pregenerated for the permanent X identity before signup. Existing fee destinations are not silently replaced when another wallet is linked.

Eligible fees accumulate in Pump.fun and PumpSwap creator vaults. A supported claim collects to the configured creator wallet. The recipient reviews the transaction; a connected payer covers claim network costs. Signing in or selecting X Money does not move money.

• Available vault fees can span multiple coins and exclude unswept trading fees.
• A token claim can sweep that token’s curve and pool before collecting shared creator vaults.
• Lifetime earned fees require a complete verified event history; until then they are unavailable.
• Claim totals use decoded confirmed provider receipts, not estimated amounts.
• Wallet balances, deposits, withdrawals, and operational SOL reserves are distinct from earnings.

Returns and future fees are not guaranteed. RELAY has no token, holding requirement, or buyback-and-burn module.

06 / Verify ownership, not endorsement.

Official X OAuth uses state and PKCE. Access follows the permanent account ID even if the handle changes. Linking a Solana wallet requires a signed wallet challenge and recent X authentication. A different account using an old handle cannot access the original identity’s fees.

Identity verified, fee wallet accessed, and creator endorsed are separate labels. None of the first two implies endorsement.

07 / Access your fee wallet.

Open the creator dashboard to see associated tokens, claim status, and linked wallets. Privy wallet access requires the same X identity at both RELAY and Privy. Recipient wallets are user-owned and are separate from RELAY’s server-side launch wallet.

Supported wallet withdrawals are SOL and standard SPL tokens, with explicit signing and a disclosed operational reserve. Token-2022 withdrawals and key export are not offered. All live money movement in this release remains locked.

08 / One request. One transaction.

Draft means the request is saved. Funded on a sponsored request means a budget is reserved. Queued means signed bytes are saved. Submitted means the signature is being checked. Confirmed requires chain confirmation and, for new launches, a matching fee destination. Failed and needs review require investigation.

An RPC timeout does not prove failure. RELAY checks the existing signature before rebroadcasting the same bytes. It never creates a second token or asks for another payment merely because a worker restarted. An expired ambiguous transaction stays in review.

Historical launches remain accessible. They are not relabeled as Pump.fun launches, and historical signed requests are reconciled without being submitted through the new provider.

09 / X Money payouts — planned.

X Money is a planned payout option, not an enabled payment service in RELAY. No authorized public third-party payout API for this workflow was found in the official X documentation reviewed on October 27, 2026.

You can save a payout preference after verifying your X account when account services are configured. X OAuth does not establish X Money eligibility. No conversion, fund reservation, payout, or banking connection happens when you save a preference.

Activation requires an authorized provider integration, eligibility checks, explicit consent to any conversion and costs, and reconciled payment receipts. Until then, supported Solana-wallet claims are the intended payout route, subject to live operational availability.

10 / Prepared, awaiting activation.

The site can be explored without activating live transactions. Production account services require PostgreSQL, the database migrations, X OAuth, and a separate worker. Transaction simulation requires a Solana RPC endpoint and public metadata storage.

Social wallet provisioning requires a configured Privy app. RELAY sponsorship uses a separate, policy-restricted Privy server wallet. Mainnet execution remains locked in code and configuration until geographic eligibility and operational requirements are resolved.

Official integration references: Pump.fun protocol and SDK documentation, X API, and Solana transaction submission.