Follow the latest source updates available here, including fund filings, software releases and protocol developments. Open an update for its original reference and related guides.
When the source publication date is unavailable, we show the first acquisition time and original source link. Acquisition time is not the event date.
ZecWeekly #52 reports the launch of ZecHub Extras and links to an ECC Trailing Finality Layer proposal. This community digest is a historical resource, not a fresh announcement; the excerpt does not establish the proposal’s outcome.
ZecWeekly #38 linked to a report about a proposed Namada shielded airdrop for Zcash holders and a preview of a shielded Zcash transaction on Ledger. This is a historical community digest, not confirmation that the airdrop occurred or that Ledger support was released.
ZecHub’s community digest links to a Zcash Foundation notice about an August ZCAP NU7 poll deadline of September 14 at 19:00 UTC, as well as announcements about Zakura 1.4.0 and the Zcon7 program. This is a historical roundup of links, not independent confirmation of the linked claims or evidence that the NU7 vote led to an upgrade.
ZecWeekly 97 announced a Discord banner competition and linked to a video of Dismad's first FROST transaction. This is a historical community digest, not a current announcement; the excerpt does not establish whether the competition remains open or the demo remains available.
ZecWeekly Yoruba #63 collects links to a Zcash payment-store guide, a Zcashd release announcement and a planned DevFund town hall. It is a community digest of earlier material, not confirmation that the planned event took place or a fresh news report.
The digest lists a DevFund town hall planned for October 10 at 19:00 UTC.
A merged librustzcash change clarifies how bulk-read allocation is documented and migrates test-only string hashes to a shared byte reader. It preserves UTF-8 validation and the encoded format; it does not change the allocation algorithm or add a decoding contract.
The merged change corrects bulk-read allocation documentation to account for amortized spare capacity and a bounded read-ahead chunk.
This Zcash ecosystem digest points readers to community posts about Zodl 3.3.0 availability on iOS and Android and a new Zcash Visualizer module. The excerpt provides links rather than details of either change, so readers should consult the linked posts for specifics.
ZODL is gradually rolling out its own wallet infrastructure and says the new design prevents it from directly linking wallet requests to users’ IP addresses. The publisher identifies Zodl 3.20.0 as the update for this rollout; rollout and performance monitoring are still underway.
Zodl: Zcash Wallet for iOS 3.20.0 adds an OHTTP-based Private connection to help hide users’ IP addresses from Zcash servers. New wallets and wallets previously using Automatic server selection now use Private by default; manually chosen servers remain unchanged.
The librustzcash pull request merges the current `maint/equihash-0.3.x` contents and #3201, while dropping CI changes specific to the maintenance branch. This is a merged development change, not evidence of a released product.
A merged librustzcash change replaces per-byte writes for specified proof bytes, scripts and test encoding with bulk writes; a Zebra benchmark measured a faster first block template after an Orchard block. The description reports no public API, wire or stored-encoding change, but human review remains pending, so this is a development change rather than a released-product announcement.
Write Orchard/Ironwood proof bytes, transparent scripts and the `merkle_tree` test string encoding with one `CompactSize::write` and one `write_all`, instead of one `write_all` call per byte through `Vector::write`.
The librustzcash change reads transparent scripts and Orchard/Ironwood proof bytes in bounded chunks rather than byte by byte. An isolated Zebra parser benchmark measured 21.8 → 7.5 ms for a 9,019-transaction V4 block, but that prototype result does not measure this branch or full-node verification; human review is pending.
Draft ZIP 326 describes how Zcash wallets would handle Orchard and Ironwood funds under NU6.3. It specifies sending to the Ironwood pool for external Orchard-protocol receivers after activation and scanning with both use_qsk values when restoring from seed until the choice can be narrowed; the draft does not establish that NU6.3 has activated.
Proposed ZIP 2009 would lower ZIP 317’s marginal fee from 5,000 to 1,000 zatoshis per logical action and raise its weight ratio cap from 4 to 10. It specifies Mainnet block height 3590000 for the changes; the proposal is not evidence that they have taken effect.
This document provides a template and writing guidance for a Zcash Improvement Proposal (ZIP). Its placeholder sections do not describe a specific proposal or an implemented protocol change.
ZIP 317 Revision 2 proposes reducing the marginal fee from 5000 to 1000 zatoshis per logical action. The revision is Proposed, and the document specifies that it applies from FEE_REDUCTION_HEIGHT: 3590000 on Mainnet and 4465026 on Testnet.
ZIP 212 explains a Canopy note-encryption change: Sapling or Orchard note plaintext uses a 32-byte rseed field in place of rcm. During decryption, recipients derive the ephemeral secret and reject a note if the ephemeral public-key check fails. This is a historical protocol explanation, not a new upgrade announcement.
ZIP 233 proposes a way to voluntarily remove ZEC from circulation, with the intent that future block subsidies return those funds to circulation. The draft is not deployed in NU7.
ZIP 258 defines deployment of Zcash NU6.3, which introduces the Ironwood shielded pool, and sets activation heights of 4134000 blocks on Testnet and 3428143 blocks on Mainnet. These are specified heights, not evidence that activation has occurred.
ZIP 2006 restricts transfers into the Orchard pool after NU6.3 activation: transactions cannot increase its chain value pool balance, and Orchard-pool Actions cannot transfer value to an address other than that of the note they spend. The ZIP says it was deployed with NU6.3, which activated on Mainnet at block height 3428143; holders can still spend Orchard-pool notes, including into the Ironwood pool.
A Zebra security advisory says any connected peer can cause affected zebrad nodes to spend tens of seconds of CPU checking a single transaction. It lists zebrad 6.4.0, 6.4.1, 6.4.2 and 7.0.0-rc.0 as affected and identifies 7.0.0 as the patched version.
A Zebra security advisory reports that an invalid transaction can occupy verification workers for minutes on affected zebrad releases before 7.0.0. Nodes near the chain tip that accept transactions from peers or untrusted RPC callers are exposed; the advisory says to upgrade to zebrad 7.0.0 or later.
A Zebra security advisory rates a transparent script verification scoring issue High (7.5) and identifies zebrad versions from 2.3.0 as affected. It says Zebra 7.0.0 fixes the issue, though a forged block body can still cause one sync-round restart before the serving peer is banned.
A Zebra security advisory says a malicious peer can stall a syncing node in an affected checkpoint range; default configurations are affected, while nodes already past the final checkpoint are not. The issue is fixed in zebrad 7.0.0, and the advisory says there is no 6.4.x patch release.
A syncing node that is served the two blocks stops committing blocks at the forged height and makes no further sync progress.
A Zebra security advisory reports that a forged checkpoint block body can stall an affected node during initial sync or resync near the final checkpoint. The issue affects zebrad 6.4.2 or earlier and 7.0.0-rc.0 with default checkpoint sync enabled; a restart restores progress, and zebrad 7.0.0 fixes the issue.
A successful delivery stalls the affected node’s synchronization until restart; no invalid state is persisted and no funds are affected.
Zingo Mobile’s release-candidate notes list swaps and redesigned Home, Send and Receive screens. They also describe a sending screen that tracks a transaction through its last confirmation and sheets that scroll on smaller displays; the release-candidate designation should not be treated as confirmation of a final release.
Sheets scroll when their contents do not fit, while their actions remain pinned.
This Zingo Beta release updates the sending screen to follow a transaction through its last confirmation. It also makes oversized sheets scroll with actions pinned and adjusts small-phone layouts so buttons remain accessible; these are beta release notes, not a general-release announcement.
Sheets scroll when their content does not fit, while their actions remain pinned.
Zebra Ándale 7.1.0-alpha.0 is a performance release for miners, mining pools, and node operators; in the publisher’s benchmarks, it processed prepared mixed blocks 9.6× faster than Zebra 7.0.0. It also avoids repeating verification when a solved block matches a proposal already validated by a pool, but this is an alpha release being offered for testing rather than the stable release.
Zebra 7.1.0-alpha.0 is a pre-release from the `next` branch that puts verified transactions into the mempool without the previous timer wait, making it relevant to miners testing new work. It retains the 7.0.0 state format for switching back without resyncing, but remains an alpha for testing rather than a recommended update for other node operators.
This alpha keeps 7.0.0's v29 state format, so it starts on an existing 7.0.0 state without resyncing, and 7.0.0 can open that state again if you switch back.
Zebra reports that affected zebrad versions can ban an honest peer that is one block ahead when it relays a transaction at the lock-time boundary. The advisory says the issue does not affect consensus or funds and is fixed in zebrad 7.0.0; affected operators should upgrade.
The affected versions are zebrad 4.5.0 through 6.4.2 and 7.0.0-rc.0.
A security advisory rates a zebrad peer-disconnection issue Medium severity: under specific timing, a connected peer can cause the node process to abort. The confirmed trigger occurs while the node is syncing, although other paths were not ruled out. Affected operators should upgrade to zebrad 7.0.0 or later; the advisory reports no impact on consensus, funds, privacy, or persistent state.
Zingo Beta zingo-beta-3.0.0-344 lists fixes for the iOS scanner, back swipes and swap tracking. This is a beta release; the excerpt does not establish a stable release.
Zingo Beta zingo-beta-3.0.0-343 fixes iOS modal behavior involving the safe area, sheets, toasts, and back swipe. This is a beta release; the excerpt does not establish a stable release.
Zodl Android’s release adds support for the Zcash network upgrade (NU7). Private migration pauses until the upgrade; if the upgrade stops a migration, the app offers to migrate the remaining funds. The release note does not say the upgrade has activated.
ZecHub’s community digest links to posts about Zebra 7.0.0-rc.0 bringing NU7 to Testnet, Shielded Labs introducing Epoch, and Zcash going live on THORChain. These are brief, attributed entries in a community roundup; the excerpt does not establish NU7 Mainnet activation or independently verify the linked announcements.
ZecHub’s community digest points readers to a Zebra 7.0.0 release described as supporting NU7 on Mainnet. It also links to a Zcash post setting NU7 activation for block 3,543,405, around November 5; the digest does not establish that activation has occurred.
A proposed Zcash ZIP would change block-subsidy calculations while leaving the existing halving step function unchanged. It is proposed for NU7; the document does not establish that the change has activated.
The proposed ZIP changes how nodes calculate the block subsidy.
Zodl Android 3.18.0 (3206) adds view-only accounts for following balances and activity without spending access. Users can import a full viewing key by pasting it or scanning a QR code, then rename, recolor, or remove the account in the app.
ZIP 2008 proposes changing the FS_FPF_ZCG_H3 funding-stream address list as part of NU7. For recipients and node implementers, the proposed change would use the new address from the first funding period beginning after activation; the proposal is not evidence that NU7 has activated.
ZIP 207 Revision 2 changes how funding-stream address periods are calculated for NU7, extending subsequent periods to 105000 blocks as target block spacing changes. This matters to implementations that select funding-stream recipients by block height; Revision 2 is intended to activate with NU7, not presented here as already active.
Under Revision 2, each address period after the period containing NU7 activation lasts 105000 blocks.
ZIP 2003 proposes disallowing v4 transactions from NU7 onward, affecting every workflow that creates them. It would also prevent spending Sprout funds because Sprout transfers require v4 transactions; this is a proposal, not evidence that the rule has activated.
Zcash ZIP 235 proposes removing 60% of transaction fees from circulation while directing the remaining 40% as before. It is proposed for NU7; the proposal is not evidence that the rule has activated.
Proposed ZIP 214 Revision 3 specifies 6132390 as the new Mainnet end height for the FS_FPF_ZCG_H3 and FS_CCF_H3 funding streams. This is a proposed NU7 rule, not evidence that NU7 has activated.
The Equihash verifier optimizations were ported from the downstream `zakura-equihash` fork. They are behind a feature flag, so downstream users can choose whether to enable them; this merged development change is not a product release.
Zebra 7.0.0 supports NU7 on Mainnet at activation height 3,543,405. For node operators upgrading from Zebra 6.x, Zebra 7 moves existing v28 state to v29 without resyncing, but downgrading afterward requires a full resync.
ZIP 259 proposes a Zcash NU7 deployment that would shorten block target spacing from 75 seconds to 25 seconds and sets a proposed Mainnet activation height of 3543405 blocks. If NU7 activates, version 4 transactions would become invalid; the ZIP is still Proposed, so the stated height is not evidence that activation has occurred.
Zodl Android 3.17.2 (3157) changes how the app verifies secure server connections following a recently disclosed industry-wide security issue. The release notes recommend that users update to the latest version as soon as possible; they do not describe the issue or its impact in more detail.
A merged librustzcash development change updates ZIP 318 calculations for NU7’s block spacing change. It scales duration calculations and anchor grid boundaries from activation, but the merge does not establish that NU7 has activated or that a product release is available.
The change implements zcash/zips#1400, which updates ZIP 318 for the NU7 block spacing change in ZIP 218.
A merged ZIP 321 development change rejects Sprout recipients when parsing payment requests and when constructing payments programmatically, preventing requests that previously failed later at transaction proposal. Tests for zip321 and zcash_address passed; this development change is not a released product.
The change gives wallet builders a 120-block default expiry delta at NU7 activation while preserving explicit expiry heights. It is not a release announcement; full local workspace testing remains unreported.
A merged librustzcash change makes the default transaction expiry delta 120 blocks instead of 40 blocks when NU7 activates; this is a development change, not a released product or confirmation of Mainnet activation.
The merged development change lets greedy input selection continue when a balance calculation needs notes from another pool or excludes a dust note. It targets transactions that previously reported insufficient funds despite a viable selection; the excerpt does not establish that this change has reached a released product.
The greedy input-selection loop now measures progress against the selected notes trimmed to the pools used in the balance calculation.
This historical community digest points readers to reported Ledger support in Zodl 3.17.0, production Zakura nodes at Foundry and a ZCG grant approval for 0xramp. The entries are brief links to other posts, not independent confirmation of their claims.
The digest reports that Foundry’s first Zakura nodes are in production, producing 65% of pool blocks.
QEDIT reported that its Zcash Shielded Assets work has caught up to NU6.3, while Shielded Labs reported BFT finalization on a Crosslink featurenet; neither report establishes a mainnet launch. Participants also raised a possible 0.67 ZEC issuance discrepancy in the current NU7 specification, with the response still under discussion.
Marek said deploying NU7 as currently specified would leave 0.67 ZEC out of total issuance.
Zodl Android 3.17.0 (3149) adds Ledger support for receiving ZEC. Sending requires approval on the device, and only one Ledger account can be connected at a time.
The release candidate describes faster blocks, fee recycling and shielded limits. Its stated Testnet activation was a plan, not confirmation that activation occurred.
Zebra 7.0.0-rc.0 is the first release candidate for NU7, the next Zcash network upgrade.
Zebra 6.4.2 fixes a crash vulnerability affecting recalled versions 6.4.0 and 6.4.1. Operators running those versions are advised to upgrade immediately.
Zebra 6.4.2 fixes a high-severity vulnerability in Zebra 6.4.0 and 6.4.1 that allows any peer to crash a node with a single network message.
No updates match these filters. Clear filters to browse the full archive.
These original records remain available with their existing dates and links.
Existing source observations
3 source observations
SEC index records a ZCSH 8-K filing
Source event date: · filing index observation
The SEC metadata index lists this form and accession. This observation does not extract fund metrics or assert approval. Open the original document for its contents.
The upstream release text mentions security. This update links the original; it is not an independent security advisory or tested deployment recommendation.
Consult the original release and advisory documents.
Foundation reports September 2026 ZCAP NU7 scope results
Source event date: · advisory scope results
The primary Foundation summary reports 135 ZCAP members casting ballots out of 198 eligible participants (source-reported 68%). All five questions and every option are preserved in the NU7 tracker. September percentages include abstentions; question 3 totals 134 votes and the others 135. These advisory, non-binding ZCAP results are not ZEC-weighted coinholder results, final ZIP approval or mainnet activation.
Historical results published September 14, 2026; local image transcription subsequently visually verified. This is an evidence update, not a newly held poll or independent recount.
We use cookie-free Plausible for aggregate traffic statistics. With your permission, Microsoft Clarity uses cookies and records clicks, scrolling and masked page layouts to help improve this site. Privacy policy