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.
Comece pela explicação mais curta e útil antes de aprofundar.
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.
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.
Codama (codama) Categoria: Ferramentas de Dev Definição: 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. Aliases: Codama SDK Generator Relacionados: Kinobi, Shank, IDL (Linguagem de Definição de Interface), Pinocchio
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.
A superset of the Solana IDL specification that enables automatic generation of program clients with full serialization and deserialization of instructions, accounts, and types. Kinobi reduces runtime errors from misaligned client-program logic by generating strongly-typed SDKs. The underlying libraries have been reorganized under the Codama project.
A Rust macro-based tool for generating IDL files from native Solana programs that do not use Anchor. Shank provides attribute macros like #[derive(ShankAccount)] and #[derive(ShankInstruction)] that annotate program code to produce IDL output compatible with Codama/Kinobi for client generation. A key component of the Pinocchio + Shank + Codama workflow.
Interface Definition Language—a JSON specification that describes a program's instructions, accounts, types, and error codes. Anchor auto-generates the IDL from the program source code. Client libraries (TypeScript, Python) use the IDL to serialize/deserialize instruction data and accounts, enabling type-safe interaction without manual encoding.
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.
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.
Essas entradas são fáceis de misturar quando você lê rápido, faz prompting em um LLM ou está entrando em uma nova camada de Solana.
The Rust crate (solana-sdk) providing types and utilities for building Solana clients and programs. For on-chain programs, use `solana-program` (no-std compatible subset). For off-chain clients, use `solana-sdk` (full features including keypair generation, transaction signing). The SDK includes types like Pubkey, Instruction, Transaction, and Account.
A C# SDK integrating the Unity game engine with Solana, enabling game developers to interact with on-chain programs, manage wallets, and sign transactions from within Unity. Supports WebGL, mobile, and desktop builds. Features include: wallet adapter, transaction building, account deserialization, and NFT display.
Entradas de glossário só ficam úteis quando estão conectadas. Esses links são o caminho mais curto para ideias adjacentes.
A superset of the Solana IDL specification that enables automatic generation of program clients with full serialization and deserialization of instructions, accounts, and types. Kinobi reduces runtime errors from misaligned client-program logic by generating strongly-typed SDKs. The underlying libraries have been reorganized under the Codama project.
A Rust macro-based tool for generating IDL files from native Solana programs that do not use Anchor. Shank provides attribute macros like #[derive(ShankAccount)] and #[derive(ShankInstruction)] that annotate program code to produce IDL output compatible with Codama/Kinobi for client generation. A key component of the Pinocchio + Shank + Codama workflow.
Interface Definition Language—a JSON specification that describes a program's instructions, accounts, types, and error codes. Anchor auto-generates the IDL from the program source code. Client libraries (TypeScript, Python) use the IDL to serialize/deserialize instruction data and accounts, enabling type-safe interaction without manual encoding.
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.
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).