The specific function within a program that processes a particular instruction variant. In native Solana programs, the entrypoint dispatches to different handler functions based on instruction data. In Anchor, each pub fn in the #[program] module is an instruction handler that is automatically routed to via the 8-byte discriminator prefix in the instruction data.
Empieza por la explicación más corta y útil antes de profundizar.
The specific function within a program that processes a particular instruction variant. In native Solana programs, the entrypoint dispatches to different handler functions based on instruction data. In Anchor, each pub fn in the #[program] module is an instruction handler that is automatically routed to via the 8-byte discriminator prefix in the instruction data.
Usa primero la analogía corta para razonar mejor sobre el término cuando aparezca en código, docs o prompts.
Piensa en esto como una de las piezas centrales que tu programa lee, escribe o invoca durante la ejecución.
Ubica el término dentro de la capa de Solana en la que vive para razonar mejor sobre él.
Accounts, instrucciones, PDAs, transacciones y flujo de ejecución.
Convierte el término de vocabulario en algo operacional para producto e ingeniería.
Este término desbloquea conceptos adyacentes rápido, así que funciona mejor cuando lo tratas como un punto de conexión y no como una definición aislada.
Usa este bloque compacto cuando quieras dar contexto sólido a un agente o asistente sin volcar toda la página.
Instruction Handler (instruction-handler) Categoría: Modelo de Programación Definición: The specific function within a program that processes a particular instruction variant. In native Solana programs, the entrypoint dispatches to different handler functions based on instruction data. In Anchor, each pub fn in the #[program] module is an instruction handler that is automatically routed to via the 8-byte discriminator prefix in the instruction data. Relacionados: Instrucción, Entrypoint, Discriminador
Usa contexto del glosario, relaciones entre términos, modelos mentales y builder paths para recibir respuestas estructuradas en vez de output genérico.
Opcional: pega código Anchor, Solana o Rust para que el Copilot mapee primitivas de vuelta al glosario.
El Copilot responderá usando el término actual, conceptos relacionados, modelos mentales y el grafo alrededor del glosario.
Estas ramas muestran qué conceptos toca este término directamente y qué existe una capa más allá de ellos.
A single operation within a transaction that invokes a program. An instruction specifies: (1) the program ID to call, (2) an array of account metas (pubkey, is_signer, is_writable), and (3) an opaque data byte array. Programs decode the instruction data to determine which operation to perform.
The function that the Solana runtime calls when a program is invoked. Native programs use the `entrypoint!()` macro which exposes a function with signature `fn(program_id, accounts, instruction_data) -> ProgramResult`. Anchor generates the entrypoint automatically and routes to the correct handler based on the instruction discriminator.
An 8-byte identifier prepended to account data and instruction data to distinguish types. Anchor computes it as the first 8 bytes of `sha256('account:<AccountName>')` for accounts and `sha256('global:<function_name>')` for instructions. Discriminators prevent type cosplay attacks by ensuring data is deserialized as the correct type.
Estos son los siguientes conceptos que vale la pena abrir si quieres que este término tenga más sentido dentro de un workflow real de Solana.
Estas entradas son fáciles de mezclar cuando lees rápido, haces prompting a un LLM o estás entrando en una nueva capa de Solana.
An instruction generated during cross-program invocation (CPI) that appears in a transaction's metadata as a nested instruction under its parent. Inner instructions are not declared in the original transaction message but are produced at runtime when a program calls another program via invoke or invoke_signed. They are visible in explorers and via the getTransaction RPC method's innerInstructions field.
A single operation within a transaction that invokes a program. An instruction specifies: (1) the program ID to call, (2) an array of account metas (pubkey, is_signer, is_writable), and (3) an opaque data byte array. Programs decode the instruction data to determine which operation to perform.
Las entradas del glosario se vuelven útiles cuando están conectadas. Estos enlaces son el camino más corto hacia ideas adyacentes.
A single operation within a transaction that invokes a program. An instruction specifies: (1) the program ID to call, (2) an array of account metas (pubkey, is_signer, is_writable), and (3) an opaque data byte array. Programs decode the instruction data to determine which operation to perform.
The function that the Solana runtime calls when a program is invoked. Native programs use the `entrypoint!()` macro which exposes a function with signature `fn(program_id, accounts, instruction_data) -> ProgramResult`. Anchor generates the entrypoint automatically and routes to the correct handler based on the instruction discriminator.
An 8-byte identifier prepended to account data and instruction data to distinguish types. Anchor computes it as the first 8 bytes of `sha256('account:<AccountName>')` for accounts and `sha256('global:<function_name>')` for instructions. Discriminators prevent type cosplay attacks by ensuring data is deserialized as the correct type.
Estas entradas viven junto al término actual y ayudan a que la página se sienta parte de un grafo de conocimiento más amplio en lugar de un callejón sin salida.
The fundamental data storage unit on Solana. Every piece of state is stored in an account identified by a 32-byte public key. Accounts hold a lamport balance, an owner program, a data byte array (up to 10MB), and an executable flag. Only the owning program can modify an account's data, but anyone can credit lamports to it.
Executable code deployed on-chain, equivalent to a smart contract on other blockchains. Programs are stateless—they store no data themselves but read/write data in separate accounts they own. Programs are compiled to SBF bytecode and loaded via the BPF Loader. Every program has a unique Program ID (its account's public key).
A single operation within a transaction that invokes a program. An instruction specifies: (1) the program ID to call, (2) an array of account metas (pubkey, is_signer, is_writable), and (3) an opaque data byte array. Programs decode the instruction data to determine which operation to perform.
An atomic unit of execution containing one or more instructions, a recent blockhash, and one or more signatures. All instructions in a transaction execute sequentially and atomically—if any instruction fails, the entire transaction reverts. Transactions have a 1,232-byte size limit (matching IPv6 MTU) and a default 200,000 CU budget.