FounderFounder
For AI agents

Can Founder rug you?

Every fact that matters for that question, with the on-chain account to check it, and the trust points that remain. Written for AI agents and for anyone who checks things themselves. The same text as plain text: founder-pad.fun/llms.txt. Last reviewed against the program source and the chain on 2026-11-05 (the reserve, the fee text, the $PAIRS launch, the fee split on the pools key), 2026-11-03 (launches) and 2026-10-16 (the rest).

Founder 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, gold), opened after migration. One ticker, one live coin. Instant multipairs launched before keep trading.

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. The program checks this before it marks a launch Live, and each point 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. Below is 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.

Live from the chain

reading /api/protocol…
Program upgrade key
Gj5nNRxhvY1aQt6ywUijCyDAxeLbTaqvg2yT5Aipair single key
Admin
Gj5nNRxhvY1aQt6ywUijCyDAxeLbTaqvg2yT5Aipair
Guardian (emergency stop)
not set
Treasury
7LuzGXh4N1XnPbYCjH4MusUdrf9HkyQifK8yWnPTfund
Reward keeper
Hc8nV4CDEEW4wZSWDat1CgQ9iA6nJRb9xxU2Lo8wpair
Attestor (social links)
5Lxt8M5shuZCFyrb64cLX9G5M4zLNvBb3VWN4dXipair
Paused
no
Pool fee split
creator 70% · Founder share 30% (Standard, Creator tax; Reward and Custom: Founder share 100%) · how Founder's share is used is the live burn_share_bps, see Fees; nothing is burned by the instant-multipair program
Launch fee
0 SOL
$PAIRS
WecNBsywJKQLGfBKZzBSix3ykXJ11DfAGUiXCLypair (launched 2026-11-05). In the instant-multipair program burning has not started yet: its Config has no $PAIRS mint set, so nothing is burned there and any burn share is held on-chain. The fee split on the pools key is separate, see the next row
Buyback and burn
Fee split on the Founder pools key: 10% multipair pools · 45% treasury · 45% buy and burn $PAIRS, in one transaction; first ran on 2026-11-05. Whether it is running right now, and the totals: /api/protocol curve.feeSplit

The values above are the state on 2026-11-05. With JavaScript on, this block is refreshed from /api/protocol, which reads the Config and ProgramData accounts on every request.

Official links

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 on this page.

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); 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
A2usBsiZG2pmTBhgan4D5aSpaSP1LjYBuetfNsYtpair
Program data (upgrade key)
CP8ADKL1ug7DJ9jiHALbvF7gkK2edRm2CVGRhN1TF6Gj
Config (roles, parameters)
8Xvf2NnqXH3YtG8nV25aeALvAoC96YqHaSaj1rirsda6
Treasury
7LuzGXh4N1XnPbYCjH4MusUdrf9HkyQifK8yWnPTfund (a plain wallet; the admin can change it)
Pools
Raydium CLMM CAMMCzo5YL8w4VFF8KVHrK22GGUsp5VTaW7grrKgrWqK · 1% tier A1BBtTYJd4i3xU8D6Tc2FzU6ZN4oXZWXKZnCxwbHXr8x
Liquidity lock
Raydium Burn & Earn LockrWmn6K5twhz3y9w1dQERbmgSaRkfnTeTKbpofwE
Per token
Token-2022 mint · launch PDA ["launch", mint] (status Live = checked by the program) · fee vault PDA ["vault", mint] · tax PDA ["reward", 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 in /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. Checked in the browser first. Before the wallet sees it, the page checks the transaction 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. The curve. 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. Fees. 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. Cost. 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. One Jito bundle. The site sends the launch as one 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. One transaction per asset. It creates the Raydium pool, puts that asset's share of the supply into a one-sided position, locks it in Burn & Earn and, if the creator chose to buy, makes 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 one, the first trade can be anyone's, and the site warns about it. The ordering comes from how the site builds the transactions, not from a program rule, and anyone can check it in the pool's first transaction.
  3. No money from the creator in the pools. The creator 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. Checked before it counts. The bookkeeping transactions are signed in the same wallet prompt and sent right after the bundle; in all the creator signs twice. The program marks the launch Live only after it has checked the mint and every locked position.

Founder charges no launch fee: it is 0 in Config and no instruction can change it. The creator pays network rent, about 0.17 SOL per asset, and 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 token cannot do

The program refuses to mark a launch Live unless all of this holds. Check any token with spl-token display <mint> --program-id TokenzQdBNbLqP5VEhdkAS6EPFLC1PHnBqCXEpPxuEb or an explorer.

No mint authority

The supply can never grow. Holders and the program can burn, so it can only shrink.

No freeze authority

No holder's account can be frozen, by anyone.

Only whitelisted extensions

MetadataPointer and TokenMetadata, plus TransferFeeConfig for taxed tokens. No PermanentDelegate, TransferHook, NonTransferable, DefaultAccountState, Pausable or MintCloseAuthority.

Frozen metadata

Pointer and update authorities revoked: the on-chain name, ticker and metadata link can't change.

Tax can't go up

Exactly 1%, 2% or 3%. Without a sunset the rate authority is None, which not even a program upgrade can change. With a sunset it sits with the program PDA, which can only set it to 0 once the burn target is met, then revokes itself.

Tax goes to the program

The withdraw authority for collected tax is always the PDA ["reward", mint], never a wallet.

This covers tokens shown as Live. Someone can bypass the site and create a mint and pools by hand; that 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; such a launch is marked unverified on-chain 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

Fees

These are the fees of instant multipairs (the Founder program). Curve tokens pay the curve fee described under How a launch works.

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.

Transfer tax and holder payouts

Enforced on-chain: 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 and adjustable: a round opens once the pot is worth 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. 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 can't 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 and Best or worst performer are applied by the keeper. No hook adds any power over the token.

Who controls what

Live values are in the block at the top. State on 2026-10-16:

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 (/developers.html). The program, the pool fee tier, the lock and the protocol share are exactly the same, and a partner site never holds a key: the creator signs every transaction in their own wallet. A partner earns by being one recipient of a share of the creator share, written into 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 (PDA ["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

Check it yourself

  1. Upgrade key: https://solscan.io/account/A2usBsiZG2pmTBhgan4D5aSpaSP1LjYBuetfNsYtpair, the Upgrade Authority field.
  2. Roles: fetch Config 8Xvf2NnqXH3YtG8nV25aeALvAoC96YqHaSaj1rirsda6 (416 bytes, owned by the program). Offsets: admin 8, treasury 40, launch fee 72, creator share 80, burn share 178, paused 180, attestor 214, social fee 246, reward keeper 248, pending admin 280, guardian 312, curator 344, buyback keeper 376. Or compare with /api/protocol.
  3. A token: its launch PDA ["launch", mint] has status Live; no mint authority, no freeze authority, the extensions above, and a TransferFeeConfig withdraw authority equal to the program PDA ["reward", mint].
  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.