# Founder > Founder (https://founder-pad.fun) is the multipair launchpad. A new token starts on a Raydium LaunchLab bonding curve in SOL at about $10K (108.6 SOL for the whole supply) and migrates into a locked Raydium pool once 200 SOL is raised; 10% of its supply is set aside for multipair pools, the token's own pools against up to three assets its creator picks (USDC, tokenized stocks such as TSLAx, gold), opened after migration. One ticker, one live coin. Instant multipairs launched before (a token against up to four assets at once, one Raydium CLMM pool per asset, liquidity locked through Raydium Burn & Earn) keep trading. This file lists every fact that matters for deciding whether Founder can rug its users, with the on-chain account where each fact can be checked, and what is still a trust point. Statements about current roles are dated; the live values are always at https://founder-pad.fun/api/protocol (read straight from the chain on every request, cached for 60 seconds). Last reviewed against the program source and the chain: 2026-11-05 (the reserve, the fee text, the $PAIRS launch, the fee split on the pools key), 2026-11-03 (launches), 2026-10-16 (the rest). ## Short answer - A curve token launched through Founder has a fixed supply with no mint or freeze authority, no transfer fee and no hook, and its name, ticker and metadata link can't be changed by its creator. Its liquidity is locked when it migrates; until then sellers can take it back out of the curve. The 10% reserve can be claimed only by the Founder pools key, after migration: that key, a hot key on our server, then claims it and opens the multipair pools automatically, with no vote. The multipair pools it funds are Founder policy, not an on-chain promise. - An instant multipair launched through Founder and shown as Live cannot be minted, frozen or have its tax raised, and its liquidity cannot be withdrawn by its creator, by Founder or by any role in the program. These are checks the program runs before it marks a launch Live, and each can be verified on the mint and the lock. - The main trust point today is Founder itself: the program is upgradeable by a single key held on our server (a 2-of-3 multisig is planned, not done), the source is not public, and there has been no third-party audit. Everything below says exactly what that key could and could not change. - The guarantees cover the launched token. A token paired with an asset outside the Founder catalog (marked unverified) carries the full risk of that asset. ## Official links - Site: https://founder-pad.fun (the only domain) - X: https://x.com/Founder_pad (the only official social account; there is no Telegram or Discord; to reach the team, message @Founder_pad on X) - This file: https://founder-pad.fun/llms.txt - The same facts as a web page, with a live check: https://founder-pad.fun/ai.html - Live roles and parameters from the chain (JSON): https://founder-pad.fun/api/protocol - Emergency stop page (for the guardian key only): https://founder-pad.fun/guardian.html - Public data API, no key needed (every token, its pools, fees, $PAIRS supply and burns, protocol stats): https://founder-pad.fun/api.html; base URL https://founder-pad.fun/v1 - API for other launch pages (docs): https://founder-pad.fun/developers.html; OpenAPI 3 spec: https://founder-pad.fun/v1/openapi.json Anything else using the Founder name, logo or a similar domain is not us. Check the program ID below. The team is not publicly identified; the accountable anchors are this domain, the X account, the program ID and the keys listed here. Founder does not launch a token whose name or ticker imitates Founder, $FOUNDER or $PAIRS (since 2026-11-04): the server refuses it before building anything (422 brand_copy), for curve launches, instant multipairs and partner sites alike. A curve token cannot get around this, because the platform's curve rule is closed and only the Founder launch key (inside a launch transaction our server built) or the Founder multisig can open it. For instant multipairs the refusal is the server's only: the program's init_launch still accepts any wallet that builds the transactions by hand, and such a token is kept out of the site's feed. Tokens made without our server, or before the ban, that imitate the name are labelled FAKE by the site (fake: true in the API, a red badge and banner on the page, and a FAKE prefix in link previews). The official $PAIRS is WecNBsywJKQLGfBKZzBSix3ykXJ11DfAGUiXCLypair (launched 2026-11-05, page https://founder-pad.fun/coin/WecNBsywJKQLGfBKZzBSix3ykXJ11DfAGUiXCLypair); any other token named PairsFun or with the ticker PAIRS is fake, as is any token named Founder Pad or with the ticker FOUNDER. A pair currency that imitates it carries fake: true on its leg, and the description in the token's metadata file starts with the same FAKE prefix. ## Identity anchors - Program (mainnet): A2usBsiZG2pmTBhgan4D5aSpaSP1LjYBuetfNsYtpair - Program data account (holds the upgrade key): CP8ADKL1ug7DJ9jiHALbvF7gkK2edRm2CVGRhN1TF6Gj - Config account (all roles and global parameters): 8Xvf2NnqXH3YtG8nV25aeALvAoC96YqHaSaj1rirsda6 - Treasury: 7LuzGXh4N1XnPbYCjH4MusUdrf9HkyQifK8yWnPTfund (a plain wallet; the admin can change it) - Pools: Raydium CLMM CAMMCzo5YL8w4VFF8KVHrK22GGUsp5VTaW7grrKgrWqK, fee tier A1BBtTYJd4i3xU8D6Tc2FzU6ZN4oXZWXKZnCxwbHXr8x (1%) - Liquidity lock: Raydium Burn & Earn LockrWmn6K5twhz3y9w1dQERbmgSaRkfnTeTKbpofwE - Every launched token is a Token-2022 mint. Its launch record is the PDA ["launch", mint] of the program (status Live is the only on-chain sign that the program has checked it); its fee vault is the PDA ["vault", mint]. ## How a launch works Every new launch is a curve token on the Founder platform on Raydium LaunchLab, paired with SOL. The live parameters are under "curve" at https://founder-pad.fun/api/protocol. 1. One transaction, one signature from the creator. The Founder launch key (a hot key on our server, the platform's curve-rule manager) opens the platform's curve rule; Raydium LaunchLab creates the Token-2022 mint (1,000,000,000 supply, 6 decimals, no mint or freeze authority, no transfer fee, no hook) and the curve; the launch key writes a vesting record for 10% of the supply whose only beneficiary is the Founder pools key; the creator's optional buy follows, capped at 10% of supply (about 12.18 SOL), so it is the first trade; the launch key closes the rule again; and a memo records the creator's 1-3 multipair assets. The launch lands whole or not at all. No Founder program instruction takes part. 2. The browser checks that transaction before the wallet sees it, against values built into the site rather than taken from our server: the platform, the launch key, the address table (a frozen list of fixed addresses that keeps the launch inside the size limit), the curve template, the reserve record and its beneficiary, the memo, the metadata link and the buy amount. 3. 662,000,000 tokens are sold on the curve, starting at a market cap of 108.6 SOL. When it raises 200 SOL, only Raydium's migrator can migrate it: the 200 SOL and 238,000,000 tokens go into a Raydium CPMM pool whose LP is locked in Raydium Burn & Earn. Until then the liquidity is what buyers put in, and sellers can take it back out. Most curves never fill. 4. The reserve: 100,000,000 tokens (10%) sit in the curve's token vault until migration; after it, only the Founder pools key can claim them. Right after migration, the pools key claims the reserve itself and opens the multipair pools from it automatically, with no vote; Founder plans to top them up, with its multisig's approval, until they hold about a tenth of the coin's liquidity. That is Founder policy run by the pools key, not an on-chain promise. Top-ups of the multipair pools from Founder's income on the main pool are planned, not running: no top-up has been made yet. Coins launched before 2026-11-05 (the first test coin) name the Founder multisig vault as the beneficiary instead; their pools open by a multisig vote (after the switch Founder decided on 2026-11-05, described below, one approval of that admin vault is enough). 5. One ticker, one live coin on Founder: a coin that migrated keeps its ticker for good, a coin on the curve keeps it while it holds at least 10% of its target (20 SOL), otherwise for 24 hours after launch. Tickers that differ only by case or by look-alike letters count as the same. It works on Founder only; nobody can stop the same ticker elsewhere. 6. Every curve trade pays 1.25% in SOL: 0.25% Raydium, 0.50% creator, 0.50% Founder. After migration the pool's fee key and its creator fee go to Founder. 7. Founder charges no launch fee. The creator pays network rent, about 0.0085 SOL (about 0.0115 SOL with a buy); Founder pays the rent of the reserve record. Trust points of curve tokens: the launch key is a single hot key on our server; it cannot move anyone's funds or change a coin, but if it leaked, someone could open the Founder platform to launches with any parameters (without the reserve, with another supply or target) until the multisig replaces it; the site lists only coins launched on the Founder template. The pools key is a single hot key on our server too, and the beneficiary of every new reserve record, which cannot be changed: if it leaked, someone could take the unclaimed reserve of migrated coins, including coins that migrate later; a new key would protect only coins launched after it. Until a curve migrates, the Founder multisig can change the platform's curve fees, the pool config and fee-key shares it migrates with, and who receives the pool's creator fee; each change waits for the multisig timelock until the switch Founder decided on 2026-11-05 runs: after it, the Founder admin vault is controlled by a single key (the Founder pools key on our server, or any one of three owner keys) with no timelock, so one signature can make these changes at once. That single key can be the pools key: if it leaked, someone could also change the platform settings, take the fee keys of graduated pools that the admin vault holds, and remove the owner keys to take the admin vault over for good. Which setup is live: curve.admin.mode in /api/protocol (multisig or single-key). Locked liquidity (the graduated Raydium pool and the multipair pools) stays locked either way: no Founder key can withdraw it. Raydium can change its own fees and upgrade LaunchLab and CPMM. A curve token's name, ticker and metadata link can't be changed by its creator (LaunchLab has no update instruction); the file behind the link is hosted by us. ## Instant multipairs launched before New instant multipair launches are paused: the server refuses them, and every new launch is a curve token. Instant multipairs launched before keep trading, collecting fees and paying holder rewards, and everything below about the Founder program, Live tokens, liquidity, fees and tax modes applies to them. This is how they were launched: 1. The site sends a launch as one Jito bundle. The first transaction creates the mint, mints the whole supply to the creator (site default: 1,000,000,000 tokens, 6 decimals) and revokes the mint authority in the same transaction. Nothing is minted or sent to Founder, the treasury or any other wallet. 2. Then one transaction per asset: create the Raydium pool, put that asset's share of the supply into a one-sided position, lock it in Burn & Earn, and, if the creator chose to buy, make that buy. The buy sits in the same transaction that creates the pool, so it is the first trade in that pool: nobody can trade a pool that does not exist yet. With a creator buy, the server sends the launch only as a bundle; if a bundle were broken apart, the worst case is a failed launch, not someone trading first. Without a creator buy, the first trade can be anyone's, and the site warns about it. This ordering comes from how the site builds the transactions, not from a program rule, and it can be checked in each pool's first transaction. 3. The creator deposits no quote asset and ends the launch holding only what they bought. The other side of every pool comes from buyers. All pools start at one market cap for the token, about 27.96 SOL, converted to dollars at the SOL price when the creator signs. 4. The bookkeeping transactions (record_leg, record_lock, finalize_launch) are signed in the same wallet prompt as the bundle and sent right after it. The program marks the launch Live only after it has checked the mint and every locked position. In all, the creator signs twice: the address lookup table, then the launch. Founder charges no launch fee (Config launch_fee_lamports = 0, and no instruction can change it). The creator pays network rent, about 0.17 SOL per asset, plus a Jito tip of 0.0001 SOL. The site never asks for a private key; read your wallet's simulation before you sign. ## What a Live Founder token cannot do The program refuses to mark a launch Live unless all of this holds. Check any token's mint with `spl-token display --program-id TokenzQdBNbLqP5VEhdkAS6EPFLC1PHnBqCXEpPxuEb` or an explorer. - No mint authority. The supply can never grow. (Holders and the program can burn, so it can shrink.) - No freeze authority. No account can be frozen. - Only these Token-2022 extensions: MetadataPointer and TokenMetadata, plus TransferFeeConfig for taxed tokens. Anything else fails the check, so a Live token cannot have a PermanentDelegate, TransferHook, NonTransferable, DefaultAccountState, Pausable or MintCloseAuthority extension. - Metadata pointer authority and metadata update authority revoked: the on-chain name, ticker and metadata link are frozen. - Transfer tax, if any, is exactly 1%, 2% or 3%, with no per-transfer cap. For tokens without a sunset, the authority to change the rate is None: nobody can ever change it, not even with a program upgrade. For Custom tokens with a sunset, the rate authority is the program PDA ["reward", mint]; the only thing the program does with it is set the rate to 0 once the burn target is met (relax_tax, callable by anyone) and then revoke itself. - The authority to withdraw collected tax is always the program PDA ["reward", mint], never a wallet. This applies to tokens the program shows as Live. Someone can bypass the site and create a mint and pools by hand; such a token never becomes Live on Founder. Check the launch status and the mint itself. The paired assets are a separate matter. Catalog assets are vetted and marked verified. The program also accepts any other asset with a real pool, and the site lets a creator paste one; such a launch is marked unverified on-chain (Launch.verified = false) and on the site. If that asset's issuer can mint, freeze or move it, it can be used to drain the other pools of the same token. Check every leg of an unverified token. ## Liquidity - Every position is one-sided and locked in Raydium Burn & Earn. The lock's fee key NFT is held by the launch's vault PDA, and the only call the vault ever signs towards the lock program is the fee harvest. No instruction in the Founder program withdraws or reduces liquidity, for any role. - The lock and the pools are Raydium's programs, upgradeable by Raydium, and Raydium's admin controls the fee tier's rates. Founder has no way to unlock a position; the permanence of the lock itself rests on Raydium. - Anyone can trigger fee collection. Collected fees go only into the vault's own token accounts and are split by the program. ## Fees These are the fees of instant multipairs (the Founder program). Curve tokens pay the curve fee described under How a launch works. - Every pool charges 1% per swap. Raydium keeps 16% of that (its protocol and fund cut). The rest, 0.84% of volume, reaches the locked position, in the paired asset only (a Tesla-paired token earns TSLAx, never its own token). - Standard and Creator-tax tokens: 70% of the collected fees to the creator (split between up to five wallets, set at launch and locked at the first collection). The other 30% is Founder's share: it goes to the Founder treasury, except any part held for the $PAIRS burn (see below). That is 0.588% of volume to the creator and 0.252% to Founder. - Reward and Custom tokens: 0% to the creator. All of it, 0.84% of volume, is Founder's share: it goes to the Founder treasury, except any part held for the $PAIRS burn (see below). - The creator share is a Config value written once at initialization; no instruction can change it. Founder's share is split between the treasury and the $PAIRS burn by burn_share_bps: the share of Founder's part that is set aside for the burn. The admin can change it with set_burn_share, only until the $PAIRS mint is set in the program (set_platform_mint); after that it is frozen for good. Live on 2026-11-05: burn_share_bps = 6667, so 20% of the pool fee on a Standard or Creator-tax token (66.7% on Reward and Custom) is held for the $PAIRS burn and 10% (33.3%) goes to the Founder treasury; nothing is burned by that program. $PAIRS itself launched on 2026-11-05, but the program's Config has no $PAIRS mint set, so burning has not started. On 2026-10-21, before $PAIRS existed, the owner decided that the value should be 0 until it did, so that all of Founder's share goes to the Founder treasury. Carrying that out takes one program upgrade and then a set_burn_share call; neither had landed on 2026-11-05 (the program was last upgraded on 2026-10-17, slot 457823682), so the value above stands. That upgrade moves the floor on burn_share_bps from set_burn_share to set_platform_mint: with it any value 0-10000 could be set while the program has no $PAIRS mint; today the lowest value the program accepts is 5000. Whatever the value, setting the $PAIRS mint requires at least 5000, which is at least half of Founder's share set aside for its burn, so a lower value has to be raised again before burning can be switched on. For the history: on 2026-10-17 a program upgrade (slot 457823682) added set_burn_share and the value moved from 7000 to 6667 (20% / 10% of the pool fee). Fees collected under an earlier value keep the split they were booked with. The live value, and the words the site shows for it, are params.burnShareBps and params.feeFlow at https://founder-pad.fun/api/protocol; they win over any dated line in this file. - Each creator-share recipient claims with their own signature, and no instruction can change who the creator is. - $PAIRS is live (launched 2026-11-05, page https://founder-pad.fun/coin/WecNBsywJKQLGfBKZzBSix3ykXJ11DfAGUiXCLypair). In the instant-multipair program burning has not started: its Config has no $PAIRS mint set, so nothing is burned. Any part of the fees booked for the burn (the burn_owed field of each fee ledger) sits in the token's vault and cannot go anywhere else. The only instruction that spends it buys the platform token that the admin names (once, permanently) through the one pool the admin registers for each asset (once, then locked), at no worse than that pool's 20-minute average price minus 5% and at most 1% of its reserve per trade, and burns what it bought in the same transaction. Both choices will be public on-chain; what the buyback achieves depends on them. A separate fee split on the Founder pools key first burned $PAIRS on 2026-11-05: see Buyback and burn below. ## Buyback and burn This is a second mechanism, separate from the instant-multipair program above. The platform fee that Founder earns on its bonding curves is claimed and split by the Founder pools key, the same hot key on our server that claims the reserve. The fee split is Founder policy run by that key: the chain does not force it, and we can change or switch it off. - The split. Platform fee split: 10% to the pools key (rent for multipair pools), 45% to the Founder treasury (7LuzGXh4N1XnPbYCjH4MusUdrf9HkyQifK8yWnPTfund), 45% to buy and burn $PAIRS. It covers only the platform fee Founder earns on its bonding curves. While the split runs, every fee claim is split on its own, and the buyback buys $PAIRS on its main pool and burns exactly what it bought, in the same transaction. It first ran on 2026-11-05. Whether it is running right now: the on field of curve.feeSplit at https://founder-pad.fun/api/protocol. - Where the live numbers are. https://founder-pad.fun/api/protocol, under "curve.feeSplit": on (true while the split is running, false while it is paused), the three shares in basis points, claimedLamports, treasurySentLamports, buybackSpentLamports, burnedRaw ($PAIRS in raw units, 6 decimals) and txs (the latest treasury transfers and buybacks, newest first, each with its transaction signature to look up on Solscan). The page of the official $PAIRS shows the same. Founder can also make one-off extra buybacks on top of the 45% share, paid with SOL that reaches the pools key outside fee claims. They are listed in extras and summed in extraBurnLamports, not in claimedLamports, so buybackSpentLamports can be larger than 45% of claimedLamports, and burnedRaw includes the $PAIRS they burned. - What it is not. It is not a burn by the instant-multipair program: that program's Config still has no $PAIRS mint set. The pools key is a single hot key on our server, so the split is a trust point: nothing on-chain forces the buyback or the transfer to the treasury. ## Transfer tax modes - Standard: no tax. - Creator tax: 1%, 2% or 3% of every transfer goes to the creator, who claims it. This is shown as CREATOR TAX on the site. - Reward: the tax goes to holders. It is sold into the token's own pools and paid out in the basket assets, pro rata to balances. - Custom: the tax is split between holders and burn in any ratio, with an optional sunset that switches the tax off for good once a set share of the supply has burned. - In every taxed mode, the tax charged when the supply is first placed in the pools is burned before anything is split. In Reward and Custom the creator has no special share, but is paid like any holder for whatever they hold. Holder payouts. On-chain rules: a payout goes only to the canonical token account of an actual holder, never more than that holder's pro-rata share of the round at the moment of payment, each wallet at most once per round, never more than the round in total, and at most one round per asset every 10 minutes. Keeper policy (off-chain, adjustable): a round opens once the pot is worth at least the larger of $50 or 0.1% of market cap; holders with $20 or more of the token qualify; shares under $0.02 are not sent. The platform takes no cut of the payout itself. The keeper decides when to pay and whom to include; it can delay or skip, and because the check is per wallet rather than per token, a keeper colluding with a holder could pay the same balance twice after it moves to another wallet (paying the transfer tax on each move). It cannot overpay a wallet or pay a non-holder. Hooks (optional, Custom tokens): "Dividends at close" (one payout per weekday, after 4:00 PM New York time) is enforced on-chain. "Diamond hands" (sellers lose that round's share) and "Best or worst performer" (pay in the day's best or worst asset) are applied by the keeper off-chain. No hook adds any power over the token: no freeze, no mint, no transfer hook. ## Who controls what Live values: https://founder-pad.fun/api/protocol. State on 2026-10-16: - Program upgrade authority: Gj5nNRxhvY1aQt6ywUijCyDAxeLbTaqvg2yT5Aipair, a single key held on our server. This is the main trust point today: whoever holds it can replace the program, and with it any rule on this page that the program enforces. It still could not mint or freeze a launched token, change the rate of a token without a sunset, or withdraw liquidity from the Raydium lock. It could move anything the program's PDAs hold or sign for: the fee-key NFTs of every locked position (and with them all future trading fees of every token), the fees and tax already in the vaults, and the tax authority of sunset tokens. The plan is a Squads 2-of-3 multisig with a 1-hour timelock for both this key and the admin; it has not happened yet. Check with `https://solscan.io/account/A2usBsiZG2pmTBhgan4D5aSpaSP1LjYBuetfNsYtpair`. - Admin (Config): the same key. Can: pause and unpause, set role keys, change the treasury address (affects only the platform's own share), set the burn/treasury split of the platform's share (set_burn_share) until the platform token is named (the floor of 50% is checked when the token is named; the deployed program accepts 50% to 100% until the upgrade described under Fees, then 0% to 100%), name the platform token once (only while that split is at least 50% burn), register one buyback pool per asset (then locked), curate the asset catalog, set a fee on social-account withdrawals (0% today, capped at 20% by the program). Cannot through any instruction: withdraw liquidity, mint or freeze a launched token, raise a transfer tax, change the fee split of a launched token, or take creator or holder shares. Admin changes go through a two-step propose/accept. - Guardian (emergency stop): not set yet. When set, it can only pause and revoke keeper keys; it cannot unpause or move funds. - Reward keeper: Hc8nV4CDEEW4wZSWDat1CgQ9iA6nJRb9xxU2Lo8wpair (server key). Bounded as described under holder payouts. - Attestor (links social accounts to wallets): 5Lxt8M5shuZCFyrb64cLX9G5M4zLNvBb3VWN4dXipair (server key). Cannot withdraw. A first link waits 24 hours before withdrawal, a wallet change 72 hours. - All of these keys sit on one server today. A compromise of that server is the worst case covered by the paragraph on the upgrade key. - Pause stops new launches, holder-reward selling and payouts, and social-escrow actions. It does not stop trading, transfers, fee collection, creator fee claims or creator-tax claims, and the program controls neither the pools nor the token, so it cannot freeze anyone. ## Launches through partner sites New instant multipair launches through partner sites are paused as well; tokens launched through partners before keep their split and label. Other sites launched the same multipairs through the Founder API (https://founder-pad.fun/developers.html). The program, the pool fee tier, the lock and the protocol share are exactly the same; a partner site never holds a key, because the creator signs every transaction in their own wallet. A partner earns by being one recipient of a share of the creator share, set in the fee vault at launch (up to the ceiling agreed for its key) and shown to the creator before they sign. It cannot touch the protocol share. A token launched this way carries via {name, url} in the API and a "via" label on the site only after the chain confirms the partner as a recipient in its fee vault (account ["vault", mint]); until the first fee collection the creator can still change the split, and if the partner is removed from it the label goes away. A partner launch whose name or ticker copies Founder or $PAIRS is refused (brand_copy), like every other launch. ## What is not true, or not yet - The multipair pools of a curve token exist only after that token migrates to its main pool: the reserve is recorded on-chain at launch, and the Founder pools key then opens the pools from it automatically, with no vote. For the official $PAIRS this happened on 2026-11-05 (pools against TSLAx, NVDAx and SPYx); a curve coin that has not migrated has no multipair pools. - The Founder launch key, which every curve launch on the Founder platform needs, is a single hot key on our server (see How a launch works). - The Founder pools key, the beneficiary of every new reserve, is a single hot key on our server as well (see How a launch works). - No third-party audit. The program went through several internal review rounds (AI-assisted, with every finding re-verified), the last dedicated one on 2026-10-03. Code added after it (tax modes, hooks, 10-minute rounds), about a third of the program, is covered by tests, not by an audit. - The source is not public and the deployed build is not verifiable yet. - The program is upgradeable by a single key today (see above). - Token images and descriptions are JSON files served from https://founder-pad.fun/meta/.json (curve tokens: https://founder-pad.fun/m/.json). The link in the mint is frozen, but the file behind it is hosted by us, not on IPFS or Arweave. For tokens launched through this site from 2026-10-17 on, the website, external_url and extensions.website fields in that file point to the token's own Founder page (https://founder-pad.fun/coin/), so terminals and aggregators send people to its on-chain proofs; the creator's own website is kept in a separate creatorWebsite field and shown on that page next to X and Telegram. Older tokens keep the creator's website in extensions.website, and a token launched without this site can carry any link (its page and /api/launch mark it metaForeign). - Tokenized stocks are issued by third parties (xStocks, PreStocks). Their issuers can freeze, pause or move their asset, including the part sitting in a locked pool. Locking protects you from the token creator, not from the issuer of the paired asset. They track a price; they are not the shares. - Fees to X, GitHub or Twitch accounts are not live yet; the site shows them as Soon and the server does not accept them. fomo accounts work: the attestor verifies them by hand, and since fomo has no stable account id, payouts follow the handle if it is renamed or sold. - Anyone can launch. A listing says nothing about who is behind a token, and any token can go to zero. Founder is not offered to persons in the United States, United Kingdom, Canada or Australia; this is a notice, not a technical block. - Mainnet launches started on 2026-10-16. Every instant multipair is an account of the program; curve tokens live on Raydium LaunchLab under the Founder platform. The Tokens page at https://founder-pad.fun lists both. ## Check it yourself 1. Program and upgrade key: `https://solscan.io/account/A2usBsiZG2pmTBhgan4D5aSpaSP1LjYBuetfNsYtpair` (Upgrade Authority field). 2. Roles: fetch Config 8Xvf2NnqXH3YtG8nV25aeALvAoC96YqHaSaj1rirsda6 (416 bytes, owner = the program). Offsets: admin 8, treasury 40, launch fee 72 (u64), creator share 80 (u16), burn share 178 (u16), paused 180, attestor 214, social fee 246 (u16), reward keeper 248, pending admin 280, guardian 312, curator 344, buyback keeper 376. Or compare with https://founder-pad.fun/api/protocol. 3. A token: its launch PDA ["launch", mint] has status Live; its mint shows no mint authority, no freeze authority, the extension list above, and a TransferFeeConfig withdraw authority equal to the PDA ["reward", mint] of the program. 4. Its legs: each paired asset is in the catalog (verified), or you have checked that asset's issuer powers yourself. 5. Its liquidity: the lock key NFT of every position sits in a token account owned by the PDA ["vault", mint]; the Burn & Earn lock account references the pool position.