← All insights
RESEARCHZcash Forum · ValarDragon

ZIP proposal to cut block spacing from 25 to 20 seconds

ValarDragon and others proposed, as a follow-up to ZIP 218, cutting the target block spacing to 20 seconds, and asked for it to be included in NU7.1 and the next polling.

Following ZIP 218, which cut block time from 75 to 25 seconds in NU7, a follow-up ZIP draft (zcash/zips PR #1437) that lowers the target spacing further to 20 seconds was posted on the forum. The authors asked for it to be put to the next polling and included in NU7.1.

The motivation is the same as for ZIP 218. Every transaction must wait for inclusion in a block, so the delay until the first confirmation is friction in merchant payments, exchange deposits and cross-chain swaps such as NEAR Intents. The authors described the change as complementary to Crosslink.

As safety evidence, they tested maximum-load 2MB blocks at 20-second spacing on a network of 80 mining nodes spread across 12 regions worldwide. They compared the orphan block rate of 1.9% with Zakura alone and 3.3% with a 50/50 mix of Zakura and Zebra-Andele against 4.68% in the earlier experiment that supported the 25-second proposal.

The detailed proposal reduces the shielded action limits to 4/5. The total shielded budget and Orchard/Ironwood actions drop from 330 to 264 per block, and Sapling inputs and outputs from 300 to 240, while the 2MB block size limit stays. Daily issuance, the NSM reissuance rate, the difficulty averaging window (102 to 128 blocks) and the default transaction expiry (120 to 150 blocks) are adjusted so that their real-time values stay the same.

They added that raising throughput must come from work that actually lowers the wallet's per-action cost, such as PIR-based sync, and that once Tachyon arrives the action limit can be raised independently of block time.

This summary is based on the original; check the original for exact details.