Client libraries for interacting with Metaplex programs. Umi is the current framework-agnostic TypeScript SDK with plugins for each Metaplex program (Token Metadata, Bubblegum, Core). The older @metaplex-foundation/js SDK is deprecated in favor of Umi. Umi provides a unified interface for serialization, signing, and RPC across all Metaplex operations.
Start with the shortest useful explanation before going deeper.
Client libraries for interacting with Metaplex programs. Umi is the current framework-agnostic TypeScript SDK with plugins for each Metaplex program (Token Metadata, Bubblegum, Core). The older @metaplex-foundation/js SDK is deprecated in favor of Umi. Umi provides a unified interface for serialization, signing, and RPC across all Metaplex operations.
Use the quick analogy first so the term is easier to reason about when you meet it in code, docs, or prompts.
Think of it as a tool or abstraction that removes friction from shipping on Solana.
Place the term inside its Solana layer so the definition is easier to reason about.
Anchor, local validators, explorers, SDKs, and testing workflows.
Turn the term from vocabulary into something operational for product and engineering work.
This term unlocks adjacent concepts quickly, so it works best when you treat it as a junction instead of an isolated definition.
Use this compact block when you want to give an agent or assistant grounded context without dumping the entire page.
Metaplex SDKs (Umi, JS SDK) (metaplex-sdks) Category: Developer Tools Definition: Client libraries for interacting with Metaplex programs. Umi is the current framework-agnostic TypeScript SDK with plugins for each Metaplex program (Token Metadata, Bubblegum, Core). The older @metaplex-foundation/js SDK is deprecated in favor of Umi. Umi provides a unified interface for serialization, signing, and RPC across all Metaplex operations. Aliases: Umi Related: Metaplex Token Metadata, NFT (Non-Fungible Token)
Use glossary context, relationships, mental models, and builder paths to get structured answers instead of generic chat output.
Optional: paste Anchor, Solana, or Rust code so the Copilot can map primitives back to glossary terms.
The Copilot will answer using the current term, related concepts, mental models, and the surrounding glossary graph.
These branches show which concepts this term touches directly and what sits one layer beyond them.
The Metaplex Token Metadata program (metaqbxxUerdq28cj1RbAWkYQm3ybzjb6a8bt518x1s) that attaches rich metadata to any SPL token or NFT. It creates a PDA-derived metadata account storing: name, symbol, URI (pointing to off-chain JSON), creators array, seller fee basis points, and collection info. The de facto standard for NFT metadata on Solana.
A non-fungible token on Solana—an SPL token with 0 decimals, supply of 1, and revoked mint authority. The NFT's metadata (image, attributes) is stored off-chain (Arweave/IPFS) linked via the Metaplex metadata account's URI field. NFTs can be standard, compressed (cNFT), programmable (pNFT), or Core assets, each with different trade-offs.
These are the next concepts worth opening if you want this term to make more sense inside a real Solana workflow.
These entries are easy to mix up when you are reading quickly, prompting an LLM, or onboarding into a new layer of 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.
Glossary entries become useful when they are connected. These links are the shortest path to adjacent ideas.
The Metaplex Token Metadata program (metaqbxxUerdq28cj1RbAWkYQm3ybzjb6a8bt518x1s) that attaches rich metadata to any SPL token or NFT. It creates a PDA-derived metadata account storing: name, symbol, URI (pointing to off-chain JSON), creators array, seller fee basis points, and collection info. The de facto standard for NFT metadata on Solana.
A non-fungible token on Solana—an SPL token with 0 decimals, supply of 1, and revoked mint authority. The NFT's metadata (image, attributes) is stored off-chain (Arweave/IPFS) linked via the Metaplex metadata account's URI field. NFTs can be standard, compressed (cNFT), programmable (pNFT), or Core assets, each with different trade-offs.
These entries live beside the current term and help the page feel like part of a larger knowledge graph instead of a dead end.
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).