Documentation
Mainnet execution is locked. No deposits are being accepted.
Launches
POOL is designed to launch coins on Pump.fun's SOL bonding curve. A completed curve graduates to PumpSwap. Launches stay closed until the trusted owner is securely configured and on-chain verification and recovery checks are complete; preparing a form does not spend SOL.
Standard launches use the configured fee split. The default is 15% holders, 5% creator, 35% flagship buyback, 35% top traders and 10% treasury. These percentages apply to creator fees, not the entire trading volume. Team splits divide the creator's share, not the other allocations.
A scheduled launch is a reminder in your open browser tab, not an unattended launch service. Your wallet still needs to approve. Closing the tab cancels the schedule.
xStocks
Choose up to 100 stock associations with searchable names and logos. These associations do not create xStock trading pairs, stock backing or stock exposure. Pump.fun still trades your coin against SOL. Selecting a stock does not buy it.
Sending an xStock in an airdrop requires that token in your wallet. Issuer eligibility, transfer restrictions and market risks may apply. POOL is not affiliated with the stock companies or their issuers.
Airdrops & dev locks
Recipients can be a pasted wallet list or the top holders of $POOL, another coin or an existing launched coin. A new coin has no eligible holder history yet. Up to 100 recipient wallets share the selected percentage of your available token balance.
Airdrop execution remains locked. A durable device journal now saves every signed batch before sending and retries only identical signed bytes. Interrupted plans appear under Recovery. Account rent and network fees are additional; SOL rewards use a separate server-backed payout ledger.
Dev lock execution is locked pending verified proof storage. The intended flow transfers part of your first-buy tokens into Streamflow until the selected unlock time. It happens after launch and can fail independently. A selected lock option is not proof that a lock completed.
Bundle buys
Same-block bundles target Jito's block engine, but acceptance is not a guarantee of inclusion. A launch bundle supports up to four fresh buying wallets plus the launch transaction. Fee-sharing setup needs another transaction.
Generate and download an unfunded wallet backup in the bundle options, then re-select that exact file to verify it. Bundle transaction construction uses those same backed-up wallets, never replacement keys. Ordered signed bundles are journaled before submission and never retried as individual transactions. Bundles remain locked pending on-chain integration verification.
Rewards & safety
Payouts and buybacks need approval from the authorized wallet. No private signing key is stored on the server. The payout ledger fixes each plan and saves signed transaction identity before broadcasting.
Missing transaction history is never proof of failure. An expired, uncertain transfer pauses for manual review rather than being automatically signed again. Only a reliably established finalized failure permits replacement.
Payout calculations now require complete, finalized trade-interval and holder inputs for every eligible coin and venue. The calculation engine accounts for rounding, thresholds and retained funds. Collection of these verified production inputs is not yet integrated; payout execution remains locked.
Lock and Pool mode plans now include fee targets and lock duration. Lock assigns the creator-fee budget to buyback; Pool plans divide it between buying tokens and depositing liquidity after graduation. Execution and automated fee collection are not implemented. There are no instant buyback or liquidity guarantees.
Walletless deposits and automatic dev selling are unavailable. Do not send SOL to an address claiming to launch a POOL coin for you. This release has not been verified as mainnet-ready.