A zero-dependency Rust framework for writing Solana programs that prioritizes performance and precise control over convenience. Pinocchio uses zero-copy patterns for accessing program inputs and has no standard library dependency, significantly reducing compute unit usage compared to solana-program or Anchor. It does not generate IDLs automatically, requiring tools like Shank or Codama for client generation.
Comece pela explicação mais curta e útil antes de aprofundar.
A zero-dependency Rust framework for writing Solana programs that prioritizes performance and precise control over convenience. Pinocchio uses zero-copy patterns for accessing program inputs and has no standard library dependency, significantly reducing compute unit usage compared to solana-program or Anchor. It does not generate IDLs automatically, requiring tools like Shank or Codama for client generation.
Use primeiro a analogia curta para raciocinar melhor sobre o termo quando ele aparecer em código, docs ou prompts.
Pense nisso como uma ferramenta ou abstração que reduz atrito no workflow de desenvolvimento em Solana.
Coloque o termo dentro da camada de Solana em que ele vive para raciocinar melhor sobre ele.
Anchor, validators locais, explorers, SDKs e fluxos de teste.
Transforme o termo de vocabulário em algo operacional para produto e engenharia.
Este termo destrava conceitos adjacentes rapidamente, então funciona melhor quando você o trata como um ponto de conexão, não como definição isolada.
Use este bloco compacto quando quiser dar contexto aterrado para um agente ou assistente sem despejar a página inteira.
Pinocchio (pinocchio) Categoria: Ferramentas de Dev Definição: A zero-dependency Rust framework for writing Solana programs that prioritizes performance and precise control over convenience. Pinocchio uses zero-copy patterns for accessing program inputs and has no standard library dependency, significantly reducing compute unit usage compared to solana-program or Anchor. It does not generate IDLs automatically, requiring tools like Shank or Codama for client generation. Relacionados: Framework Anchor, Steel, Codama
Use contexto do glossário, relações entre termos, modelos mentais e builder paths para receber respostas estruturadas em vez de output genérico.
Opcional: cole código Anchor, Solana ou Rust para o Copilot mapear primitivas de volta para termos do glossário.
O Copilot vai responder usando o termo atual, conceitos relacionados, modelos mentais e o grafo ao redor do glossário.
Esses ramos mostram quais conceitos esse termo toca diretamente e o que existe uma camada além deles.
The most popular framework for building Solana programs in Rust. Anchor provides macros (#[program], #[account], #[derive(Accounts)]) that auto-generate boilerplate for account validation, serialization, discriminators, and error handling. It includes a CLI (anchor init/build/test/deploy), IDL generation, and TypeScript client generation. Reduces program code by ~80% compared to native development.
An opinionated Rust framework for writing Solana programs built on top of solana-program, exposing macros, functions, and patterns for safe and expressive on-chain code. Steel provides granular access to Solana program primitives while maintaining readability. Unlike Anchor's all-or-none approach, developers can selectively use only the Steel components they need.
A code generation toolchain that takes a Solana program's IDL and generates fully-typed client SDKs in multiple languages. Codama processes IDLs produced by Shank or Anchor and emits TypeScript clients. It is the successor of the Kinobi project and is commonly used in the Pinocchio + Shank + Codama workflow for native Solana program development.
Estes são os próximos conceitos que valem abrir se você quiser que este termo faça mais sentido dentro de um workflow real de Solana.
Entradas de glossário só ficam úteis quando estão conectadas. Esses links são o caminho mais curto para ideias adjacentes.
The most popular framework for building Solana programs in Rust. Anchor provides macros (#[program], #[account], #[derive(Accounts)]) that auto-generate boilerplate for account validation, serialization, discriminators, and error handling. It includes a CLI (anchor init/build/test/deploy), IDL generation, and TypeScript client generation. Reduces program code by ~80% compared to native development.
An opinionated Rust framework for writing Solana programs built on top of solana-program, exposing macros, functions, and patterns for safe and expressive on-chain code. Steel provides granular access to Solana program primitives while maintaining readability. Unlike Anchor's all-or-none approach, developers can selectively use only the Steel components they need.
A code generation toolchain that takes a Solana program's IDL and generates fully-typed client SDKs in multiple languages. Codama processes IDLs produced by Shank or Anchor and emits TypeScript clients. It is the successor of the Kinobi project and is commonly used in the Pinocchio + Shank + Codama workflow for native Solana program development.
Essas entradas vivem ao lado do termo atual e ajudam a página a parecer parte de um grafo maior, não um beco sem saída.
The most popular framework for building Solana programs in Rust. Anchor provides macros (#[program], #[account], #[derive(Accounts)]) that auto-generate boilerplate for account validation, serialization, discriminators, and error handling. It includes a CLI (anchor init/build/test/deploy), IDL generation, and TypeScript client generation. Reduces program code by ~80% compared to native development.
The Anchor macro applied to structs to define on-chain account data layouts. `#[account]` auto-derives Borsh serialization, adds an 8-byte discriminator prefix (SHA-256 of 'account:<Name>'), and implements space calculation. Optional attributes: `#[account(zero_copy)]` for zero-copy deserialization of large accounts.
The Anchor macro that defines the accounts struct for an instruction. Each field specifies an account with validation constraints. Account types include: `Account<'info, T>` (deserialized), `Signer<'info>` (must sign), `Program<'info, T>` (program reference), `SystemAccount<'info>`, and `UncheckedAccount<'info>` (no validation, use carefully).
Declarative validation rules on Anchor account fields. Key constraints: `#[account(mut)]` (writable), `#[account(init, payer=x, space=n)]` (create), `#[account(seeds=[...], bump)]` (PDA validation), `#[account(has_one=field)]` (field equality), `#[account(constraint = expr)]` (custom boolean), `#[account(close=target)]` (close and reclaim rent).