Builtin Programs
Solana contains a small handful of builtin programs, which are required to run validator nodes. Unlike third-party programs, the builtin programs are part of the validator implementation and can be upgraded as part of cluster upgrades. Upgrades may occur to add features, fix bugs, or improve performance. Interface changes to individual instructions should rarely, if ever, occur. Instead, when change is needed, new instructions are added and previous ones are marked deprecated. Apps can upgrade on their own timeline without concern of breakages across upgrades.
For each builtin program the program id and description each supported instruction is provided. A transaction can mix and match instructions from different programs, as well include instructions from deployed programs.
System Program
Create accounts and transfer lamports between them
- Program id:
11111111111111111111111111111111
- Instructions: SystemInstruction
Config Program
Add configuration data to the chain and the list of public keys that are permitted to modify it
- Program id:
Config1111111111111111111111111111111111111
- Instructions: config_instruction
Unlike the other programs, the Config program does not define any individual instructions. It has just one implicit instruction, a "store" instruction. Its instruction data is a set of keys that gate access to the account, and the data to store in it.
Stake Program
Create stake accounts and delegate it to validators
- Program id:
Stake11111111111111111111111111111111111111
- Instructions: StakeInstruction
Vote Program
Create vote accounts and vote on blocks
- Program id:
Vote111111111111111111111111111111111111111
- Instructions: VoteInstruction
BPF Loader
Add programs to the chain and execute them.
- Program id:
BPFLoader1111111111111111111111111111111111
- Instructions: LoaderInstruction
The BPF Loader marks itself as its "owner" of the executable account it creates to store your program. When a user invokes an instruction via a program id, the Solana runtime will load both your executable account and its owner, the BPF Loader. The runtime then passes your program to the BPF Loader to process the instruction.
Secp256k1 Program
Verify secp256k1 public key recovery operations (ecrecover).
- Program id:
KeccakSecp256k11111111111111111111111111111
- Instructions: new_secp256k1_instruction
The secp256k1 program processes an instruction which takes in as the first byte a count of the following struct serialized in the instruction data:
Pseudo code of the operation:
This allows the user to specify any instruction data in the transaction for signature and message data. By specifying a special instructions sysvar, one can also receive data from the transaction itself.
Cost of the transaction will count the number of signatures to verify multiplied by the signature cost verify multiplier.
Optimization notes
The operation will have to take place after (at least partial) deserialization, but all inputs come from the transaction data itself, this allows it to be relatively easy to execute in parallel to transaction processing and PoH verification.