A fast Solana testing framework (solana-bankrun for TypeScript, bankrun for Rust) that runs tests against an in-process Bank without starting a full validator. Bankrun processes transactions ~100x faster than solana-test-validator, supports time warping (advance slots/time), and can load accounts from fixtures or mainnet snapshots.
Start with the shortest useful explanation before going deeper.
A fast Solana testing framework (solana-bankrun for TypeScript, bankrun for Rust) that runs tests against an in-process Bank without starting a full validator. Bankrun processes transactions ~100x faster than solana-test-validator, supports time warping (advance slots/time), and can load accounts from fixtures or mainnet snapshots.
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.
Bankrun (solana-bankrun) (bankrun) Category: Developer Tools Definition: A fast Solana testing framework (solana-bankrun for TypeScript, bankrun for Rust) that runs tests against an in-process Bank without starting a full validator. Bankrun processes transactions ~100x faster than solana-test-validator, supports time warping (advance slots/time), and can load accounts from fixtures or mainnet snapshots. Related: Testing (Solana Programs), Local Development (Localnet), LiteSVM
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 process of validating Solana programs through unit tests, integration tests, and fuzz testing. Common approaches: Rust tests with solana-program-test or LiteSVM (fast, in-process), TypeScript tests with Bankrun or solana-test-validator (end-to-end), and fuzz testing with Trident. Best practice is testing both happy paths and attack vectors (missing signers, wrong owners).
The practice of developing and testing Solana programs against a local validator (solana-test-validator) or in-process test harness (Bankrun, LiteSVM). Local development allows instant transaction confirmation, free airdrops, account cloning from mainnet, and rapid debugging. Programs are deployed locally before moving to devnet for integration testing.
A lightweight Solana VM for testing Rust programs. LiteSVM provides a minimal SVM environment that executes transactions without the overhead of a full validator. It supports account setup, program deployment, and transaction execution. Faster than solana-program-test and suitable for unit testing individual program instructions.
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.
The official command-line tool for interacting with Solana clusters. Key commands: `solana balance`, `solana transfer`, `solana program deploy`, `solana config set --url`, `solana airdrop` (devnet). Configuration in `~/.config/solana/cli/config.yml` sets the default cluster URL and keypair path.
The next-generation Solana TypeScript SDK (@solana/kit, formerly @solana/web3.js v2) featuring a modular, functional API. Unlike v1's monolithic classes, v2 uses composable functions and tree-shaking for smaller bundles. Key changes: pipe-based transaction building, codec-based serialization, and native support for versioned transactions. Significantly smaller bundle size than v1.
Glossary entries become useful when they are connected. These links are the shortest path to adjacent ideas.
The process of validating Solana programs through unit tests, integration tests, and fuzz testing. Common approaches: Rust tests with solana-program-test or LiteSVM (fast, in-process), TypeScript tests with Bankrun or solana-test-validator (end-to-end), and fuzz testing with Trident. Best practice is testing both happy paths and attack vectors (missing signers, wrong owners).
The practice of developing and testing Solana programs against a local validator (solana-test-validator) or in-process test harness (Bankrun, LiteSVM). Local development allows instant transaction confirmation, free airdrops, account cloning from mainnet, and rapid debugging. Programs are deployed locally before moving to devnet for integration testing.
A lightweight Solana VM for testing Rust programs. LiteSVM provides a minimal SVM environment that executes transactions without the overhead of a full validator. It supports account setup, program deployment, and transaction execution. Faster than solana-program-test and suitable for unit testing individual program instructions.
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).