Learn · Updated November 18, 2026

Which program is this? Reading program IDs

A Solana program ID is the address of the executable account an instruction calls. Each instruction stores a one-byte index into the transaction's account list, and the key at that index is the program ID. Compare it with a sourced list, and confirm unknown IDs on chain, because a name or a vanity prefix proves nothing.

Where the program ID sits#

A compiled instruction does not carry the program's 32-byte address. It carries programIdIndex, a position in the message's account keys, followed by the account indexes and the data. Compiled instructions walks through those bytes, and base58 and public keys covers turning the 32 bytes into the familiar text form.

For v0 transactions there is a rule that matters to any decoder: the program index must point into the static account keys, never into addresses loaded from a lookup table. The Solana message code says so directly: program IDs "cannot be dynamically loaded from a lookup table." In two mainnet blocks from 18 November 2026, all 3,754 top-level instructions followed it. So you can name the program of every top-level instruction without resolving any address lookup table.

Instructions that one program issues to another during execution, the cross-program invocations, are not in the transaction bytes at all. Inner instructions and CPI explains where those come from.

Well known program IDs, checked 18 November 2026#

Every ID below was executable on mainnet at slot 470,935,874, and each one is named by the source in the right-hand column.

ProgramProgram IDNamed by
System11111111111111111111111111111111solana-sdk sdk-ids
Compute BudgetComputeBudget111111111111111111111111111111solana-sdk sdk-ids
Address Lookup TableAddressLookupTab1e1111111111111111111111111solana-sdk sdk-ids
VoteVote111111111111111111111111111111111111111solana-sdk sdk-ids
StakeStake11111111111111111111111111111111111111solana-sdk sdk-ids
Upgradeable loaderBPFLoaderUpgradeab1e11111111111111111111111solana-sdk sdk-ids
Ed25519 signature verifyEd25519SigVerify111111111111111111111111111solana-sdk sdk-ids
Secp256k1 signature verifyKeccakSecp256k11111111111111111111111111111solana-sdk sdk-ids
Secp256r1 signature verifySecp256r1SigVerify1111111111111111111111111solana-sdk sdk-ids
SPL TokenTokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DAtoken interface crate
Token-2022TokenzQdBNbLqP5VEhdkAS6EPFLC1PHnBqCXEpPxuEbtoken-2022 interface crate
Associated Token AccountATokenGPvbdGVxr1b2hvZbsiqW5xWH25efTNsLJA8knLassociated-token-account interface crate
Memo (v3)MemoSq4gqABAXKb96qnH8TysNcWxMyWCqXgDLGmfcHrmemo interface crate
pump.fun6EF8rrecthR5Dkzon8Nwu78hRvfCKubJ14M5uBEwF6Ppump.fun published IDL
PumpSwappAMMBay6oceH9fJKBRHGP5D4bD4sWpmSwMn52FMfXEAPumpSwap published IDL
Raydium AMM v4675kPX9MHTjS2zt1qfr1NYHuzeLXfQM9H24wFSUt1Mp8raydium-amm source
Raydium CPMMCPMMoo8L3F4NbTegBCKVNunggL7H1ZpdTHKxQB5qKP1CRaydium published IDL
Raydium CLMMCAMMCzo5YL8w4VFF8KVHrK22GGUsp5VTaW7grrKgrWqKRaydium published IDL
Orca WhirlpoolwhirLbMiicVdio4qvUfM5KAg6Ct8VwpYzGff3uctyCcOrca published IDL
Meteora DLMMLBUZKhRxPF3XUpBCjp4YzTKgLccjZhTSDM9YuVaPwxoMeteora published IDL
Meteora DAMM v2cpamdpZCGKUy5JxQXB4dcpGPiikHawvSWAd6mEn1sGGMeteora published IDL
Meteora Dynamic Bonding Curvedbcij3LWUppWqq96dh6gJWwBifmcGfLSB5D4DuSMaqNdynamic-bonding-curve source
Jupiter v6 aggregatorJUP6LkbZbjS1jKKwapdHNy74zcZ3tLUZoi5QNyVTaV4its on-chain IDL account
Pyth receiverrec5EKMGg6MxZYaMdyBfgwp4d5rB9T1VQH5pJv5LtFJpyth_solana_receiver_sdk
Pyth push oraclepythWSnswVUd12oZpeFP8e9CVaEqJg25g1Vtc2biRsTpyth_solana_receiver_sdk
Switchboard On-DemandSBondMDrcV3K4kxZR1HNVT7osZxAHVHgYXL5Ze1oMUvits on-chain IDL account

Programs change. A team can deploy a new version at a new address and move traffic there, so treat this table as dated and check it again before relying on it months from now.

Built in, upgradeable and frozen programs#

The owner of a program account tells you how it is run. In the same check, System, Compute Budget, Vote, the upgradeable loader and the three signature-verify programs were owned by NativeLoader1111111111111111111111111111111: they are built into the validator. Stake and Address Lookup Table, which have been moved out of the validator and into on-chain code, were owned by the upgradeable loader, like SPL Token, Token-2022 and every DEX in the table. Associated Token Account and Memo were owned by BPFLoader2111111111111111111111111111111111, the older loader whose programs cannot be upgraded.

An upgradeable owner means the code behind an ID can change while the ID stays the same. That is why a decoder pinned to one IDL version can start failing on the same program, and why reading an IDL matters as much as the ID itself.

Verifying an ID you do not recognise#

  1. Call getAccountInfo on the address. A program account has executable: true; anything else is not a program.
  2. Look at the owner. One of the loaders means deployed code; the native loader means a built-in program.
  3. Look for a published source that names the ID: a declare_id! line in the project's repository, or the address field of the IDL the team publishes.
  4. For Anchor programs, derive the on-chain IDL account: take the program's address derived from no seeds, then create an address from it with the seed anchor:idl and the program as owner. If that account exists, its data holds the IDL, compressed, and the IDL's address field should match. For Jupiter v6 this gives C88XWfp26heEmDkmfSzeXP7Fd7GQJ2j9dDTUsyiZbUTa.
  5. Check that the ID actually behaves as claimed: decode a few of its instructions with that IDL and confirm the names and accounts make sense.

Filtering shreds by program#

Because every top-level program ID is in the static keys, a receiver can decide whether a transaction is interesting straight after parsing it from shreds, with no RPC call and no lookup table. In the two blocks above, 781 transactions called 94 distinct programs at the top level. Compute Budget appeared in 489 of them, System in 392 and Associated Token Account in 317. A set of the IDs you care about, checked against each instruction's program, removes most of the rest early. Decoding a block from shreds shows where in the pipeline that check fits. For the DEX programs in the table, concentrated liquidity explains the extra tick and bin accounts their swaps carry, and for the two Pyth programs, how oracle updates appear walks through one update.

Questions about program IDs#

Is a program ID the same as a program address?#

Yes. The program ID is the public key of the program's executable account. The two names are used interchangeably.

Why do so many IDs start with readable words?#

Teams grind for vanity prefixes, and the built-in programs use readable base58 strings padded with ones. A readable prefix is a convenience, not a guarantee: anyone can grind an address that starts with the same letters.

Can one transaction call the same program twice?#

Yes. Each instruction has its own program index, and several instructions can point at the same key.

What a program ID does not prove#

Matching an ID tells you which program ran, not what it did. The instruction data decides that, and an upgradeable program can change its layout over time. The ID also says nothing about success: a transaction can call a well known program and fail. And for calls made from inside another program, the top-level ID is only the entry point.

From the ID to the instruction#

Once you know the program, decode its instructions with Anchor using its IDL, or read how swaps look as instructions for the DEX programs above. To see which programs show up in your own live traffic, compare the plans.

Sources#

Raw shreds on your own server

Ultra Low Latency Shreds is $200 and Standard Shreds is $100. You pay in crypto, tell us which IPv4 address and UDP port should receive the stream, and we wire it up by hand.