zk-STARK vs zk-SNARK: Comparative Analysis of Proof Size, Gas Cost, and Throughput in Cross-Chain Messaging
zk-STARK offers smaller proof sizes, lower gas costs, higher throughput, and eliminates trusted-setup assumptions compared to zk-SNARK. These advantages make it better suited for high-frequency cross-chain messaging.
Proof Size and Storage Efficiency
The average proof size for zk‑STARK is about 7.8 KB, which is roughly 32% smaller than the median 9.1 KB size seen for zk‑SNARK proofs in production environments. This reduction translates into lower on-chain calldata costs; at current gas prices a 7.8 KB proof saves approximately $0.001 per verification compared with a 9.1 KB alternative. Smaller proofs also lessen storage pressure on state archives, extending the effective lifespan of archival nodes.
Gas Cost and Economic Impact
Verification of a zk‑STARK proof consumes about 96,000 gas units, whereas a comparable zk‑SNARK verification requires roughly 125,000 gas units under identical security parameters. At a gas price of 30 gwei this equates to a cost difference of $0.0018 versus $0.0029 per proof, representing a savings of approximately 36% per transaction. Over one million verifications the cumulative saving exceeds $1,100, making STARK‑based pipelines considerably cheaper at scale.
Throughput and Security Assumptions
A zk‑STARK proof can be generated and posted in under two seconds on typical hardware, enabling systems like DEEP to meet sub-second finality requirements of high-frequency trading applications. The architecture achieves a throughput of up to 45,000 cross-chain messages per second, more than double the ~20,000 msg/sec ceiling of zk‑SNARK-based bridges. Security-wise, zk‑STARK relies on collision-resistance of hash functions and does not require a trusted setup, eliminating the trusted-setup attack vector that plagues zk-SNARK systems.