The API interface for interacting with a blockchain node. Clients send JSON-RPC requests to read account state, submit transactions, and subscribe to events. Solana RPC methods include getAccountInfo, getBalance, sendTransaction, and simulateTransaction. Public RPCs have rate limits; production dApps use dedicated providers (Helius, Triton, QuickNode).
Start with the shortest useful explanation before going deeper.
The API interface for interacting with a blockchain node. Clients send JSON-RPC requests to read account state, submit transactions, and subscribe to events. Solana RPC methods include getAccountInfo, getBalance, sendTransaction, and simulateTransaction. Public RPCs have rate limits; production dApps use dedicated providers (Helius, Triton, QuickNode).
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 building block that connects one definition to the larger Solana system around it.
Place the term inside its Solana layer so the definition is easier to reason about.
Wallets, signing flows, dApps, and key management concepts.
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.
RPC (Remote Procedure Call) (rpc-general) Category: Web3 Definition: The API interface for interacting with a blockchain node. Clients send JSON-RPC requests to read account state, submit transactions, and subscribe to events. Solana RPC methods include getAccountInfo, getBalance, sendTransaction, and simulateTransaction. Public RPCs have rate limits; production dApps use dedicated providers (Helius, Triton, QuickNode). Related: RPC (Remote Procedure Call), Node
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 JSON-RPC 2.0 protocol interface through which clients communicate with Solana nodes to query chain state, submit transactions, and subscribe to events. Solana exposes a rich set of HTTP and WebSocket endpoints (e.g., getAccountInfo, sendTransaction) that abstract direct peer-to-peer network participation, making RPC the primary integration point for wallets, dApps, and indexers.
A computer running blockchain client software that maintains a copy of the ledger and participates in the network. Node types: full node (validates all transactions, stores full state), archive node (stores complete history), light node (verifies headers only). On Solana, validator nodes require high-end hardware (256+ GB RAM for RPC nodes).
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.
A decentralized exchange allowing peer-to-peer token trading without a centralized order book or custodian. Users trade directly from their wallets. DEXs use automated market makers (AMMs) or on-chain order books. Advantages: no KYC, self-custody, censorship-resistant. Disadvantages: potential for higher slippage, smart contract risk, and MEV extraction.
A unique, non-interchangeable digital token representing ownership of a specific asset—artwork, collectibles, music, game items, domain names, or real-world assets. NFTs are verified on-chain and can be traded on marketplaces. Unlike fungible tokens (where each unit is identical), each NFT has distinct properties. Major Solana NFT marketplaces: Magic Eden, Tensor.
Glossary entries become useful when they are connected. These links are the shortest path to adjacent ideas.
The JSON-RPC 2.0 protocol interface through which clients communicate with Solana nodes to query chain state, submit transactions, and subscribe to events. Solana exposes a rich set of HTTP and WebSocket endpoints (e.g., getAccountInfo, sendTransaction) that abstract direct peer-to-peer network participation, making RPC the primary integration point for wallets, dApps, and indexers.
A computer running blockchain client software that maintains a copy of the ledger and participates in the network. Node types: full node (validates all transactions, stores full state), archive node (stores complete history), light node (verifies headers only). On Solana, validator nodes require high-end hardware (256+ GB RAM for RPC nodes).
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 vision of a decentralized internet built on blockchain technology, where users own their data, identity, and digital assets. Web1 was read-only (static pages), Web2 is read-write (platforms like social media), Web3 is read-write-own (permissionless, user-sovereign). Web3 applications use wallets instead of logins and smart contracts instead of centralized servers.
An application with its backend logic running on a blockchain as smart contracts rather than centralized servers. dApps typically have a traditional web frontend that interacts with on-chain programs via RPC. Users authenticate with wallets instead of username/password. Examples: Uniswap (Ethereum DEX), Jupiter (Solana DEX), Magic Eden (NFT marketplace).
Software or hardware that manages cryptographic keys and enables users to sign transactions, view balances, and interact with dApps. Hot wallets (Phantom, Solflare, Backpack) are internet-connected for convenience. Cold wallets (Ledger, Trezor) store keys offline for security. Wallets don't actually 'hold' tokens—they hold the private keys that control on-chain accounts.
A 12 or 24-word human-readable backup of a wallet's master private key, generated using BIP-39 standard. The seed phrase can deterministically regenerate all derived keypairs (BIP-44 derivation paths). Losing the seed phrase means permanently losing access to all associated accounts. Never share, photograph, or store seed phrases digitally in plain text.