Skip to content
Build with clarity.
A practical guide to the platform, its transaction flow, and the infrastructure underneath.
Introduction
Merged Finance brings token creation and discovery into a focused creator workspace. Start with an identity, review a concrete transaction, and approve it with your wallet. Every published launch record is backed by independently verified onchain evidence.
Merged Finance
The platform combines a token launch wizard, confirmed-token directory, creator dashboard, and network route planner. Your wallet remains the transaction authority. The frontend never stores wallet private keys in its database.
Multichain Architecture
A shared chain registry describes each network independently from its execution capabilities. Tokens have separate deployment records, allowing future EVM factories and bridge integrations to be added without treating network branding as proof of deployment.
Supported Networks
Solana, Ethereum, BNB Chain, Base, and Robinhood Chain form the Merged ecosystem. The current token-creation transaction executes on Solana mainnet. Review always identifies the actual transaction destination.
Solana
Ethereum
BNB Chain
Base
Robinhood ChainToken Creation
Choose a name of up to 32 UTF-8 bytes and a ticker of 1–10 uppercase letters or numbers. The dollar sign is a display convention and is not included in the onchain symbol. Add a description, optional social URLs, and an image up to 5 MB. If you keep the monogram, it is uploaded as your token’s permanent art.
Wallet Connection
All wallet connections use Privy with wallet-only authentication. Ethereum and Solana addresses are separate identities. The account menu lists linked wallets; the launch wizard explicitly selects a connected Solana signer. A wallet must be linked to your authenticated account before the backend accepts its launch intent.
Launch Flow
Identity → Type and Fee → Review → Launch. Preparation uploads metadata, generates a mint locally, simulates a create_v2 transaction through the official Pump.fun SDK, and saves a launch intent. Review the estimated costs, then approve in your wallet. The mint keypair signs locally. The backend records the real signed transaction before broadcast. Use Check onchain status or the dashboard’s Reconcile action until finalized verification is complete.
Token Metadata
Image content, file size, token fields, and social URLs are validated server-side. Filebase stores the image and metadata JSON on IPFS. The public JSON is fetched and checked before transaction construction. The exact uploaded image URL is preserved in the token record. Upload credentials remain server-side.
Liquidity
Standard launches use Pump.fun’s native SOL bonding-curve mechanism. Merged does not create an additional liquidity pool or execute an initial creator buy in this flow. Indexed market data on token pages is supplied by DEX Screener; absent data remains blank. Use the genuine Pump.fun link to inspect the market directly.
Creator Fees
The selected Solana payer is encoded as the token creator. Pump.fun controls its fee schedule, including tier-dependent rates. When RPC data is readable, the wizard shows the global base rates as reference values, not a guaranteed trading rate. The frontend does not modify those fees, collect a platform trading fee, or distribute fees across chains. Earnings are not displayed without verified accounting data.
Bridging Architecture
The bridge page is a route planner with no registered execution adapter. It cannot produce a bridge signature or report a successful transfer. A typed adapter interface leaves room for a future LayerZero integration, which will require independently verified deployments, quotes, and confirmation semantics before activation.
Security
Protected APIs verify a Privy access token and linked wallet ownership. Launch attempts use unique idempotency keys and mint addresses. Signed messages must match the prepared SDK transaction exactly, and all required signatures must verify. The server checks Solana’s mainnet genesis hash, finalized transaction success, the expected Pump program and payer, Token-2022 mint ownership, and onchain metadata. Unknown broadcast outcomes remain recoverable; they are never automatically retried with a new mint.
FAQ
A wallet submission is not a confirmation. If an RPC call times out, open your dashboard and reconcile the existing attempt. Do not create another token to resolve an uncertain broadcast. A restored unsigned draft has no stored mint private key; inspect its history before starting over. Estimates include network fees and simulated account funding, which covers rent and any creation charges. No funds are spent until you approve and submit the wallet transaction.
Primary references
Privy documentation ↗
Pump.fun protocol documentation ↗
Filebase IPFS API ↗
DEX Screener market API ↗
Robinhood network configuration ↗