Summary
Please consider standardizing compressed JSON-RPC HTTP responses (e.g. gzip / zstd via Accept-Encoding / Content-Encoding) for RPCv2.
Motivation
Transaction v1 / SIMD-0296 increases max transaction size from 1232 → 4096 bytes. That especially blows up getBlock (and similar) payloads.
As far as we can tell, neither Agave nor Firedancer honors Accept-Encoding on the RPC HTTP path today, so compression has to live in a proxy in front of the node. Response compression in the RPC stack would reduce bandwidth and improve client latency without changing method schemas.
Notes
This is a cross-cutting HTTP transport concern rather than a per-method change. If accepted, it can be followed by an RFC proposal as described in GOVERNANCE.md.
Context from discussion with Solana / Anza: current RPC is in maintenance mode; Tim Garcia suggested filing this against the specs repo for RPCv2.
Summary
Please consider standardizing compressed JSON-RPC HTTP responses (e.g. gzip / zstd via
Accept-Encoding/Content-Encoding) for RPCv2.Motivation
Transaction v1 / SIMD-0296 increases max transaction size from 1232 → 4096 bytes. That especially blows up
getBlock(and similar) payloads.As far as we can tell, neither Agave nor Firedancer honors
Accept-Encodingon the RPC HTTP path today, so compression has to live in a proxy in front of the node. Response compression in the RPC stack would reduce bandwidth and improve client latency without changing method schemas.Notes
This is a cross-cutting HTTP transport concern rather than a per-method change. If accepted, it can be followed by an RFC proposal as described in GOVERNANCE.md.
Context from discussion with Solana / Anza: current RPC is in maintenance mode; Tim Garcia suggested filing this against the specs repo for RPCv2.