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.
Empieza por la explicación más corta y útil antes de profundizar.
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.
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 herramienta o abstracción que reduce fricción en el workflow de desarrollo en Solana.
Ubica el término dentro de la capa de Solana en la que vive para razonar mejor sobre él.
Anchor, validators locales, explorers, SDKs y flujos de testing.
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.
Codama (codama) Categoría: Herramientas de Dev Definición: 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 (Lenguaje de Definición de Interfaz), Pinocchio
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 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.
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.
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.
Las entradas del glosario se vuelven útiles cuando están conectadas. Estos enlaces son el camino más corto hacia ideas adyacentes.
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.
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 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).