Solana Block Reads Get a Safer Size Signal in SOL RPC v1.3.0

The latest tagged release of ICP’s SOL RPC canister, v1.3.0, makes a narrowly scoped but important correction to Solana block reads: it no longer ignores the response_size_estimate parameter for the getBlock endpoint. The release was published on January 12, 2026, and is marked as deployed to both production and staging.

That parameter matters because HTTPS outcalls on the Internet Computer are metered by response size. A canister making a Solana RPC request must attach enough cycles to cover the expected response, while the response itself must fit within the request’s configured limit. Block responses can vary substantially depending on the requested slot and the amount of transaction data returned.

The v1.3.0 change does not make Solana’s fast-changing APIs generally safe for replicated calls. The SOL RPC documentation still warns that getLatestBlockhash can be difficult to use through HTTPS outcalls because it changes roughly every 400 milliseconds, while replicas need time to obtain responses and reach consensus. The documented alternatives remain using a durable nonce or obtaining a recent slot and then retrieving the corresponding block.

For builders, the practical lesson is to treat response sizing as part of transaction and data-flow design. When calling getBlock, set an estimate that reflects the requested transaction detail and encoding, budget cycles accordingly, and test against production behavior. Do not assume that a successful local call proves that the same request will reach consensus on mainnet: local deployments use a single replica and can permit IPv4 behavior that mainnet does not.

One factual caveat is important: v1.3.0 is the latest tagged release shown on the release page, but the repository reports 50 commits to main since that release. Teams pinning a dependency should therefore inspect newer commits and verify the deployed Wasm hash before adopting a release as a production baseline.

The change is modest, but it improves the boundary between Solana’s variable-size data and ICP’s replicated, cycle-metered execution model. In Chain Fusion, those operational details are part of correctness—not merely tuning.