Zakura 1.3.x Adds the Experimental P2Pv2 Stack
Last week’s issue covered Zakura Common’s cryptographic speedups. The new operator story is Zakura 1.3.x: 1.3.0 was the first node release built on Common, and the official download page now lists 1.3.2, released September 5. The release adds an experimental P2Pv2 consensus engine with verified-header-chain and bounded-DAG validation, alongside peer discovery, RPC visibility, and lightwalletd integration.
The operator detail matters: the experimental engine is disabled by default on mainnet. This is not a consensus change that has activated everywhere; it is a new validation path for operators to evaluate. Mainnet operators should read the release notes and use the current download rather than treating this as a routine wallet update. Zakura 1.3.0 release notes · Current downloads
Zakura 1.3.0 release notes →Vizor Demonstrates a Shielded Ledger Transaction
Vizor published a development-build demonstration of a shielded ZEC transaction signed on a Ledger. The wallet says it intends to be the first wallet supported when the Ledger app goes live, but the demo is not a claim that general Ledger support is already released.
That distinction aside, hardware signing is an important usability milestone: shielded ZEC needs to work with the custody and signing habits people already trust, not only inside software wallets. Vizor’s demonstration · Follow-up on the Ledger app
Vizor’s demonstration →Coinbase-Wrapped ZEC Arrives on Base
cbZEC, a Coinbase-custodied wrapped representation of ZEC, appeared on Base this week and began showing up in Base ecosystem integrations. It creates a new route into Base liquidity and DeFi, but it is not a shielded-pool asset: the token is a transparent wrapped representation backed by ZEC held in custody.
That makes this an access and liquidity story, not a privacy upgrade. Users should understand which side of the bridge they are using and where the privacy boundary ends. Ecosystem digest · cbZEC contract and market data
Ecosystem digest →