A Solid Intel alert claimed Zcash had not produced a block in more than four hours, adding fresh pressure just after the network completed its Orchard security upgrade.
The claim was not supported by live infrastructure checked afterward. A Trezor Zcash Blockbook instance showed the backend synchronized, mempool in sync and last block 3,364,603 updated minutes earlier. Blockchair’s Zcash explorer also showed recent chain activity rather than a confirmed four-hour halt.
Zcash faced an explorer and infrastructure-data scare, not a confirmed chain-wide shutdown at check time.
Kraken ZEC Maintenance Adds To Confusion
Kraken’s Zcash funding status showed ZEC deposits and withdrawals moving through maintenance on June 3. Deposits resumed first, while withdrawals were temporarily unavailable. A later update said new ZEC withdrawals had resumed and were processing normally, although a subset of earlier submitted transactions still needed an additional fix.
That exchange-side maintenance likely added to the confusion around network status. A funding gateway issue can stop users from depositing or withdrawing through an exchange without proving that the blockchain itself has stopped producing blocks.
The timing made the claim more explosive because Zcash had just completed a high-pressure Orchard remediation. Zcash Open Development Lab said the Orchard vulnerability was fixed through a soft fork followed by a hard-fork network upgrade, with Orchard transactions re-enabled after roughly 24 hours.
Orchard Fix Completed, No Exploit Found
The Orchard issue was a soundness vulnerability affecting Zcash’s latest shielded pool. ZODL said there was no evidence of exploitation, no unauthorized value creation and no detected impact to the total ZEC supply. User funds remained safe, privacy was not affected, and Sapling plus transparent Zcash transactions continued during the Orchard suspension.
The Orchard remediation remains the main confirmed network event. The later block-halt claim was separate and, based on live checks, did not show a confirmed full network outage.
The facts now point to a narrower story. Zcash completed a serious Orchard security upgrade. Kraken temporarily limited ZEC funding during maintenance. Some public data views triggered a viral halt claim. Synced infrastructure still showed recent blocks. Unless developers or core infrastructure operators confirm otherwise, the June 3 scare should be treated as a block-data discrepancy, not a verified Zcash shutdown.
Be the first to comment