ProgramData Account

What it is

The ProgramData account is where an upgradeable program’s actual code lives. The Program account at the public address is a 36-byte pointer; it points here, to a much larger account holding a ~45-byte state header followed by the program’s ELF bytecode.

Why it exists

Splitting “the address you call” (Program account) from “the code and who can change it” (ProgramData) is what enables upgrades without changing the program’s public address. ProgramData carries the upgrade authority and the deployment slot, and gets rewritten on each upgrade.

Byte layout

The account holds the ProgramData variant of UpgradeableLoaderState (bincode), then the raw ELF:

The header is 45 bytes (4 + 8 + 1 + 32) when an upgrade authority is set; the ELF follows immediately.

Where you see it

Behind every upgradeable program. Take a program’s address, read its Program account programdata_address, fetch that account — this is what you get. It’s usually the largest account associated with a program.

Common gotchas

• The ELF starts at offset 45, not 0. Tools that scan for the 7F454C46 magic must skip the state header. Reading byte 0 as ELF magic fails — byte 0 is the discriminator 03.
• upgrade_authority = None means immutable. Setting the authority to None (a one-way action) makes the program permanently un-upgradeable — a common trust signal that “this code can never change.”
• slot is the last-upgrade slot, not creation. It updates on every redeploy. Useful for “when did this program last change?”
• The account is sized for the largest ELF ever deployed. Upgrading to a smaller program doesn’t shrink the account; the extra space stays allocated (and rent-paid).