Tag archive
JSON-RPC is a four-field request and a two-field response, and Solana's entire node API is built on it. This explainer covers the protocol, Solana's HTTP and WebSocket methods, commitment levels, encodings, common errors, and where gRPC and shreds ta
Why Resource Loading Matters in Distributed Query Systems In distributed systems like...
Why 5,197 bRPC servers cover only half the affected population, and how the keep-alive authentication bypass changes the mitigation.
From 12.8 seconds to approximately 150 milliseconds: How Alpenglow is reshaping transaction finality,...
Alpenglow replaces TowerBFT and Proof of History on 21 October 2026. Here is how Votor finalizes in 150 ms, what 20+20 resilience really means, how the one-slot migration works, and the exact list of things that change for RPC, gRPC, and shred consum
We rebuilt Solana RPC on Chainstack. We spent the last few months on two things: methods hitting...
Say you're building a multi-chain wallet backend. It needs Ethereum, a couple of L2s, and — because...
gRPC resuelve la comunicación entre microservicios con code generation y HTTP/2. Es rápido, es tipado, y la curva de aprendizaje te va a doler un poco. Spoiler: vale la pena.
Every custom Solana JSON-RPC error from -32001 to -32021: the message the node sends, the data it attaches, and the client action each calls for. From source.
If you're a Web3 developer, you've definitely run into these situations: Transaction stuck pending...
Check all Chains in 3 Seconds Tired of switching between Ethereum, BSC, Polygon, Arbitrum,...
I've been using Triport recently, and somewhat unexpectedly, the thing I like most about it isn't...