A blockchain client that trusts the cluster's communication without independently verifying transaction validity, relying on RPC responses from validators for all state queries. Thin clients are the simplest integration method — most dApp frontends and wallet interfaces operate as thin clients by trusting their configured RPC provider to return accurate data.
Comece pela explicação mais curta e útil antes de aprofundar.
A blockchain client that trusts the cluster's communication without independently verifying transaction validity, relying on RPC responses from validators for all state queries. Thin clients are the simplest integration method — most dApp frontends and wallet interfaces operate as thin clients by trusting their configured RPC provider to return accurate data.
Use primeiro a analogia curta para raciocinar melhor sobre o termo quando ele aparecer em código, docs ou prompts.
Pense nisso como um bloco de construção que ajuda a ligar uma definição isolada ao sistema maior onde ela vive.
Coloque o termo dentro da camada de Solana em que ele vive para raciocinar melhor sobre ele.
Clusters, nós, atores de MEV, roteamento e ambientes operacionais.
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.
Thin Client (thin-client) Categoria: Rede Definição: A blockchain client that trusts the cluster's communication without independently verifying transaction validity, relying on RPC responses from validators for all state queries. Thin clients are the simplest integration method — most dApp frontends and wallet interfaces operate as thin clients by trusting their configured RPC provider to return accurate data. Relacionados: Light Client, RPC (Chamada de Procedimento Remoto), Nó RPC
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 blockchain client that verifies a moderate amount of cluster data to confirm transaction validity without replaying the full ledger or maintaining complete account state. Light clients download block headers and use Merkle proofs or validator attestations to verify specific transactions or account states, trading full trustlessness for dramatically reduced resource requirements.
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 Solana full node that stores ledger state and serves JSON-RPC and WebSocket requests from clients without participating in consensus or voting. RPC nodes must replay every transaction to maintain an accurate account state database, and high-throughput deployments typically run dedicated RPC nodes with large SSDs, high RAM (256 GB+), and high-bandwidth network connections to handle concurrent client load without impacting validator performance.
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.
A client library that sends transactions directly to the current leader validator's Transaction Processing Unit (TPU) port over QUIC, bypassing the standard RPC sendTransaction relay for lower latency and higher landing probability. The Solana SDK's TpuClient resolves the current leader from the leader schedule, establishes a QUIC connection, and forwards signed transactions directly. This approach is used by MEV searchers, high-frequency traders, and latency-sensitive applications that need the fastest possible path to block inclusion.
A blockchain client that verifies a moderate amount of cluster data to confirm transaction validity without replaying the full ledger or maintaining complete account state. Light clients download block headers and use Merkle proofs or validator attestations to verify specific transactions or account states, trading full trustlessness for dramatically reduced resource requirements.
Entradas de glossário só ficam úteis quando estão conectadas. Esses links são o caminho mais curto para ideias adjacentes.
A blockchain client that verifies a moderate amount of cluster data to confirm transaction validity without replaying the full ledger or maintaining complete account state. Light clients download block headers and use Merkle proofs or validator attestations to verify specific transactions or account states, trading full trustlessness for dramatically reduced resource requirements.
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 Solana full node that stores ledger state and serves JSON-RPC and WebSocket requests from clients without participating in consensus or voting. RPC nodes must replay every transaction to maintain an accurate account state database, and high-throughput deployments typically run dedicated RPC nodes with large SSDs, high RAM (256 GB+), and high-bandwidth network connections to handle concurrent client load without impacting validator performance.
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.
Solana's primary production cluster where real SOL and real economic activity occur; the "beta" designation reflects the network's ongoing protocol development despite being fully live since March 2020. It uses the same architecture as other clusters but with real validator stakes, live staking rewards, and permanent on-chain state. All production dApps, tokens, and NFTs exist on Mainnet Beta.
A persistent public Solana cluster intended for application development and testing, running the same software version as Mainnet Beta but with no real economic value. Devnet SOL can be freely airdropped via the CLI or faucet APIs, and the ledger may be reset periodically by Solana Labs. Developers use Devnet to test programs and integrations before deploying to Mainnet Beta.
A public Solana cluster used primarily by the Solana core team and validators to test new software releases, performance benchmarks, and network upgrades under real network conditions before they reach Mainnet Beta. Testnet SOL has no monetary value, and the ledger is reset more frequently than Devnet; it is less suitable for application development and more suited for validator operators validating their infrastructure.
The rate at which a Solana cluster processes and commits transactions; Solana's theoretical maximum exceeds 65,000 TPS due to its parallel execution model, though real-world sustained throughput on Mainnet Beta typically ranges from 2,000–5,000 non-vote TPS under normal load. Vote transactions (used for consensus) make up a significant portion of all on-chain activity and are counted separately. High TPS is enabled by Proof of History timestamps, Sealevel parallel execution, and Gulf Stream mempool-less forwarding.