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.
Empieza por la explicación más corta y útil antes de profundizar.
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.
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 un bloque de construcción que conecta una definición aislada con el sistema mayor donde vive.
Ubica el término dentro de la capa de Solana en la que vive para razonar mejor sobre él.
Clusters, nodos, actores de MEV, routing y entornos operativos.
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.
Thin Client (thin-client) Categoría: Red Definición: 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 (Llamada a Procedimiento Remoto), Nodo RPC
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 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.
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.
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.
Las entradas del glosario se vuelven útiles cuando están conectadas. Estos enlaces son el camino más corto hacia ideas adyacentes.
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.
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.
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.