ChainCatcher reported that Zakura, a node implementation for Zcash, has released an experimental network layer called P2Pv2 to replace the legacy protocol inherited from Bitcoin.
Zakura said the layer combines high-throughput networking, resource controls, and a consensus engine that has undergone property testing. It also allows developers to add services without permission.
Throughput targets and current limits
Zakura said that at roughly 50,000 transactions per second, each full node would need to continuously receive about 100 MB/s of block data. By comparison, NU7 blocks can carry at most 2 MB every 25 seconds, leaving the current network throughput more than 1,000 times below that rate.
The team added that Tachyon can shrink proofs after they enter a block, but the network still has to propagate a large volume of individual transactions.
Protocol stack and transport design
P2Pv2 replaces a protocol stack dating back about 10 years with protocols that can be optimized separately for latency, throughput, or robustness. A single secure connection can carry multiple independent services.
Its transport layer is zakura-quic, built on quinn-proto and using QUIC with TLS 1.3. Peer authentication is handled through Ed25519 node identities.
Zakura said the changes remove the dependency on Iroh. Nodes can configure socket buffers, flow-control windows, timers, and connection admission before the TLS handshake.
The new transport connects directly to peer addresses and does not use relays, external address lookup, automatic port mapping, or QUIC NAT traversal. Nodes sign their identity, address, protocol scope, and service ID, and clients can discover peers by specific service.
Header validation and block sync
A separate component, zakura-header-chain, validates block headers, keeps competing branches in a directed acyclic graph, and selects the best valid chain.
For block synchronization, requests are scheduled according to measured delivery rates from each peer. Previously verified commitment trees are then used to skip rebuilding the Sapling, Orchard, and Ironwood trees for every block.
Deployment status and remaining risks
Mainnet still uses the old P2P stack by default. Testnet and Regtest run in dual-stack mode by default, with the native protocol version listed as p2p-v2/3.
Zakura said P2Pv2 still carries known denial-of-service risks and has not yet become a hardened trust boundary. Production hardening, resource controls, and the block relay protocol are still under development.


