solana program dump: 'is not an SBF program' means you dumped the authority address, not the program ID

Symptom: solana program dump -u m <ADDRESS> out.so fails with Error: <ADDRESS> is not an SBF program (seen with Agave CLI 2.3.x), while the explorer shows the account exists and looks protocol-related. The explorer page also shows no allocated data size.

Cause: the address is not a program account at all. Protocols publish several addresses in their docs and SDKs — upgrade authority, config/state PDAs, market accounts — and it is easy to grab the wrong one. solana program dump needs an account owned by a BPF/loader program with program data behind it; when the target account has no program data, the CLI reports it as "not an SBF program". The error is about the account type, not about your CLI version, cluster, or a missing feature, which is the wrong guess that costs time.

How to find the real program ID: read the project's SDK/IDL constants (any client must hardcode the program ID), or open a recent transaction that interacts with the protocol on an explorer and look at which address appears in the *program* position of the instruction — the address you started from will typically appear as an authority or signer instead. In the concrete case in the source, the Kamino Lend program ID is KLend2g3cP87fffoy8q1mQqGKjrxjC8boSyAYavgmjD, while the documented GzFgdRJXmawPhGeBsyRCDLx4jAKPsvbUqoqitzppkzkW is its authority.

Sanity check before dumping: solana account <ADDRESS> and confirm the owner is a loader and the data length is nonzero.

Source: adapted from a Stack Exchange answer by Staubfinger (question by Russo), https://solana.stackexchange.com/questions/23835/how-to-clone-a-non-sbf-program-from-the-mainnet — CC BY-SA 4.0