Upgrading a blockchain to post-quantum cryptography usually comes with a bill: severe network congestion, gas fees that spike hard, and state bloat from signature and zero-knowledge proof sizes that are orders of magnitude larger than what today's chains carry. A proposed technique called Compact Shielded client-side validation, or CSV, argues the fix is to stop putting signatures on the blockchain at all.
Under the proposal, data storage and verification move to end-user devices. Strip the signatures out and a transaction's on-chain footprint comes to 96 bytes.
Where the bloat comes from
Post-quantum signatures and the zero-knowledge proofs that often accompany them are big. That's not a bug in any one implementation — it's the tradeoff the cryptography itself imposes. Push them on-chain at scale and blocks fill faster than validators can keep up, fees climb, and the chain's state keeps growing. The congestion isn't incidental. It's a direct consequence of what post-quantum security costs when you write it into the ledger.
CSV's answer is to move the heavy material somewhere else. Verification happens on the user's device, not on every node in the network. The chain only records the result.
Ninety-six bytes
That's the number the proposal hangs on. By eliminating signatures from the on-chain record entirely, CSV claims a footprint of 96 bytes per transaction. It's a striking figure next to what post-quantum signatures would otherwise demand, and it's the core of the pitch: you keep the security upgrade without handing the network a scaling crisis.
The catch is that client-side validation is only as good as the clients doing it. Moving verification to end-user devices changes the trust model, and the proposal's success will depend on whether wallets and other software can shoulder that work reliably. The facts on hand don't detail how that's handled.
The trade the proposal asks for
Every architectural shift trades one set of problems for another. CSV trades on-chain verification for device-side verification, and it trades the simplicity of a self-contained ledger for a lighter one that depends on clients doing their part. Whether that's a good deal for a given network is a question its operators will have to answer, not the proposal's authors.
What CSV does establish is that the post-quantum migration doesn't have to be a choice between security and usability. There's at least one design on the table that claims both. The next step is for the proposal to move from concept to implementation — and for the wallets and node operators who'd carry it to say whether 96 bytes is worth the change.
