Definition: A Program-Derived Address (PDA) is a deterministic 32-byte Solana address calculated from a program ID and a set of seeds. A PDA is deliberately off the Ed25519 curve, so no private key can sign for it. Instead, the program ID used to derive it can authorize the PDA during a cross-program invocation (CPI) through Solana’s invoke_signed mechanism.12
| Network | Solana |
|---|---|
| Address type | 32-byte address derived off the Ed25519 curve |
| Inputs | A program ID, seed values, and a bump seed |
| Common uses | Program state, user-specific accounts, and program-controlled authorities |
| Official documentation | Program Derived Address documentation |
| Directories | Solana Directory |
How a PDA is derived
Derivation starts with a program ID and seed byte strings chosen by the program’s design. Solana hashes those inputs with a bump value and a fixed marker. It then checks whether the resulting address is a valid Ed25519 curve point. If it is on the curve, the candidate is rejected; the derivation helper tries another bump until it finds an address off the curve. The standard helper returns the canonical bump, the first bump that produces an off-curve address for those seeds and that program ID.2
The program ID scopes the result: the same seed values used with a different program ID produce a different address. Solana limits a derivation to 16 seeds, and each seed is limited to 32 bytes. Because the seed byte strings are concatenated before hashing, developers should encode them so different seed combinations cannot be confused—for example, use fixed-length values or clear separators where appropriate.2
| Property | What it means |
|---|---|
| Deterministic | The same program ID and seed inputs reproduce the same address when derived with the canonical bump. |
| Off-curve | The address is not a valid Ed25519 public key, so no private key exists for signing ordinary transactions. |
| Program-authorized | The deriving program can authorize the PDA as a signer during a CPI by providing its seeds to invoke_signed. |
| Not automatically an account | Deriving an address does not create an on-chain account or store data there; a separate instruction must create the account. |
What a PDA can and cannot do
Programs use PDAs to give state a predictable address. A program might derive one configuration account for itself or one profile account for each user by including that user’s public key among the seeds. A PDA can also serve as an authority for a token account or vault, letting the program authorize actions through its instructions without managing a separate private key for that address.13
A PDA is an address, not a wallet with a hidden key. It cannot sign a normal user transaction, and knowing its seeds does not grant a caller authority. During a CPI, the runtime checks that the calling program supplies seeds that derive the PDA under that program’s own ID; it then treats the PDA as a signer for that invocation only.13
Deriving a PDA also does not make the resulting address an account or determine who may change account data. An account must be created separately. Once it exists, its on-chain owner field identifies the program allowed to modify its data or debit its lamports, so instructions must validate both the expected address and the account’s owner and state.34
Security considerations
- Use the canonical bump. A non-canonical bump can produce another valid off-curve address for the same seed set, allowing account-substitution bugs when programs assume there is only one address.2
- Make seed encodings unambiguous. Seed byte strings are concatenated before hashing. Without fixed lengths or separators, separate inputs such as
abandcdcan be indistinguishable from one inputabcd.2 - Validate ownership and state. A familiar PDA address does not by itself prove that an account was created, has the expected owner, or contains valid data.4
- Do not treat seeds as secrets. Seeds describe how to calculate an address; program instructions and account checks must enforce authorization.
Page updated: November 12, 2026.
Related Terms
Related Articles
- The Drift Protocol Exploit Explained: Durable Nonces, Social Engineering, and Recovery
- Why Can an Audited Smart Contract Still Be Exploited?
- How Do Crypto Bridges Work—and Why Are They Such a Hack Target?
- Why Crypto Calls It a Wallet—and What the Metaphor Hides
See Also
Sources
- Solana. “Program Derived Addresses (PDAs).” Solana Documentation. Accessed November 12, 2026. https://solana.com/docs/core/pda.
- Solana. “PDA Derivation.” Solana Documentation. Accessed November 12, 2026. https://solana.com/docs/core/pda/pda-derivation.
- Solana. “PDA Accounts.” Solana Documentation. Accessed November 12, 2026. https://solana.com/docs/core/pda/pda-accounts.
- Solana. “Accounts.” Solana Documentation. Accessed November 12, 2026. https://solana.com/docs/core/accounts.