Program addresses

Documentation Index

Fetch the complete documentation index at: https://docs.raydium.io/llms.txt

Use this file to discover all available pages before exploring further.

​

Mainnet-beta

​

On-chain programs

• AMM v4 and Farm v3/v5 are retained for existing pools and positions. The Raydium UI and SDK route new pool creation and new ecosystem farms to CPMM, CLMM, and Farm v6 respectively — see protocol-overview/versions-and-migration.
• The Farm v3 ID above doubles as the $RAY single-asset staking program. Behavior is identical to Farm v3 for LP staking.
• Stable AMM is a separate program that the AMM Routing program can target alongside AMM v4, CPMM, and CLMM. Liquidity is thin compared to the other three programs and the SDK does not expose a first-class API for it; integrators that route through it generally do so via the router.
• Source-code availability. Of the on-chain programs above, only raydium-amm (AMM v4), raydium-cp-swap (CPMM), and raydium-clmm (CLMM) ship with public source repositories under github.com/raydium-io. Stable AMM, LaunchLab, AMM Routing, Burn & Earn / LP Lock, and the Farm programs are not publicly available — verify them against the live API, the on-chain bytecode, and the published IDLs in raydium-io/raydium-idl instead.

​

Shared admin authority

​

Shared config / PDA conventions

# CPMM fee configs (returns an array of {id, index, tradeFeeRate, ...})
GET https://api-v3.raydium.io/main/cpmm-config

# CLMM fee configs
GET https://api-v3.raydium.io/main/clmm-config

​

PDA seeds

// CPMM — all seeds are static ASCII strings unless noted.
const [ammConfig]   = PublicKey.findProgramAddressSync(
  [Buffer.from("amm_config"), u16ToBytes(index)],
  CPMM_PROGRAM_ID,
);
const [authority]   = PublicKey.findProgramAddressSync(
  [Buffer.from("vault_and_lp_mint_auth_seed")],
  CPMM_PROGRAM_ID,
);
const [poolState]   = PublicKey.findProgramAddressSync(
  [Buffer.from("pool"), ammConfig.toBuffer(), token0Mint.toBuffer(), token1Mint.toBuffer()],
  CPMM_PROGRAM_ID,
);
const [lpMint]      = PublicKey.findProgramAddressSync(
  [Buffer.from("pool_lp_mint"), poolState.toBuffer()],
  CPMM_PROGRAM_ID,
);
const [vault0]      = PublicKey.findProgramAddressSync(
  [Buffer.from("pool_vault"), poolState.toBuffer(), token0Mint.toBuffer()],
  CPMM_PROGRAM_ID,
);
const [vault1]      = PublicKey.findProgramAddressSync(
  [Buffer.from("pool_vault"), poolState.toBuffer(), token1Mint.toBuffer()],
  CPMM_PROGRAM_ID,
);
const [observation] = PublicKey.findProgramAddressSync(
  [Buffer.from("observation"), poolState.toBuffer()],
  CPMM_PROGRAM_ID,
);

​

Devnet

​

How to verify an address on-chain

1. Solana Explorer. Paste the address into explorer.solana.com and confirm it’s marked Program with a current upgrade authority. Mainnet-beta should show deploys signed by Raydium’s upgrade authority.
2. CLI. Use solana program show <PROGRAM_ID> -u mainnet-beta to inspect deploy slot, BPF loader, upgrade authority, and data length. Record these in your runbook.
3. IDL attachment. Query the on-chain IDL with anchor idl fetch <PROGRAM_ID> --provider.cluster mainnet. The IDL’s address field should match. The same IDLs are mirrored at github.com/raydium-io/raydium-idl — diff the on-chain IDL against the repo before trusting it.
4. Config/admin authorities. For CPMM/CLMM config accounts, read the owner/protocol_owner field and confirm it matches the current Raydium multisig published in security/admin-and-multisig.

​

Updating this page

• Changes to program IDs are safety-critical. Do not ship a program-ID change without (a) linking to the Raydium announcement, (b) adding an entry in reference/changelog, and (c) running a link-check over the docs to confirm no page still references the old value.
• Deprecations stay in the table with a status note rather than being deleted — existing pools still resolve via the old program.

• Live API: https://api-v3.raydium.io/main/info
• github.com/raydium-io/raydium-idl
• github.com/raydium-io/raydium-cp-swap