
$ZEC news
Every $ZEC story, instantly, with how the price moved after each one.
Top stories
- Security Incident | Update #3: 90% of Stolen Assets Replenished; Proof of Reserves Snapshot Provided Fellow Binancians, Our last update explained that Binance had set aside more than $6.34B in company funds to cover hacked losses, and we had already covered approximately 80% of the impacted amount of the hacked loss at that time. That covered amount is now up to 90%. All BTC, ETH, USDT, BNB, SOL, USDC, XRP, USD1, RLUSD, and ZEC are fully backed 100%. We will continue to buy the remaining relevant token assets through market and OTC channels until the covered amount reaches 100% for all tokens. Binance will absorb the financial impact of these stolen funds, not our users. The replenishment employed: A partial deployment of the Secure Asset Fund for Users (SAFU). This is expected to happen over the next 24 hours; users can view the updated balance here. A portion of our Futures insurance fund. The remaining balance of the Futures insurance fund is a regulatory requirement. Users can check the updated balance of the fund here. Binance's own corporate treasury. We continue purchasing the remaining affected stolen assets through market and OTC channels. The outstanding 10% consists of tokens outside the top ten listed above. These assets are less liquid, which means they may take longer to source in the required amounts. We are working with industry partners to complete the remaining acquisitions and will provide further updates as progress continues. Separately, we have taken a new Proof of Reserve (PoR) snapshot at 2026-10-31 00:00 (UTC), and this has already been updated on the PoR website. The snapshot provides an updated view of assets that are fully accounted for and is part of our ongoing commitment to transparency. The full zero-knowledge proof takes approximately 40 to 50 hours to generate due to the computational workload, so users holding any of these ten tokens can independently verify that their assets are at a minimum 1:1 backed once the full proof is generated, estimated to be by Tuesday, 2026-11-03 (UTC). Our commitment remains the same: Binance will fully cover the financial impact of the funds stolen in this incident. We will continue to demonstrate this commitment through measurable progress, transparent reporting, and concrete actions. Our next milestone in focus is resuming the withdrawal services for users. We remain on track to reopen withdrawals within our previously stated timeframe (on Sunday, 2026-11-01) and will provide a further update as soon as details are confirmed. FAQs What is the Secure Asset Fund for Users (SAFU)? SAFU is an emergency reserve fund established by Binance in July 2018 to protect user assets in extreme cases, such as security breaches or platform-level incidents. Binance allocated a percentage of trading fees to grow the fund to a substantial level over time. The SAFU fund is held and managed by Nest Clearing and Custody Limited, a Recognized Clearing House regulated by the Abu Dhabi Global Market (ADGM) Financial Services Regulatory Authority. A portion of the funds serves as capital reserves as part of Binance regulatory obligations in the ADGM. Will Binance replenish the SAFU fund? Binance is committing to replenishing the SAFU to return the fund size to approximately US$1 billion. We are replenishing SAFU to ensure it remains fully resourced and ready to protect users, consistent with its purpose as an emergency user-protection reserve. If BTC is already 100% covered (as shown in the latest PoR snapshot), why are you still deploying the SAFU fund? We are utilizing part of the SAFU fund to acquire the remaining 10% of outstanding assets in order to reach 100% coverage for all tokens. Can a user view the SAFU Fund? The SAFU wallet address is at: BTC: 1BAuq7Vho2CEkVkUxbfU26LhwQjbCmWQkD It can be publicly viewed with blockchain explorers, such as: What are Futures Insurance Funds? Futures Insurance Funds are safety nets provided by Binance that limit the impact of liquidations. Their primary purpose is to reduce the occurrence of counterparty liquidations (commonly referred to as ADL), protect futures traders from deficit losses resulting from bankrupt positions, and help ensure profitable positions are paid out in full. Futures are funded by Binance, including Liquidation Clearance Fees collected by the platform, and are not part of user assets. Binance has rebalanced its Futures Insurance Funds to move a portion of the balance to cover the affected assets. Is there a higher risk of Auto-Deleveraging (ADL)? The Futures Insurance Funds remain above the coverage level required under Binance’s established risk-management framework, helping ensure the fund remains available to support users during extreme market conditions. We monitor fund size continuously against historical stress scenarios reflecting extreme but plausible market conditions, and top it up when required. Due to volatility, no exchange can completely avoid auto-deleveraging, but we always strive to keep occurrences to a minimum. Will Binance replenish the Futures Insurance Funds? The funds are maintained above their required size. When the balance falls below the level our framework requires, Binance tops them up from company funds, as we have done previously. What was released was excess above that level, which is why it could be reallocated without affecting coverage. Can a user view the Futures Insurance Funds on Proof of Reserves (PoR)? No, not on PoR. The fund itself is publicly viewable here and refreshes daily at 00:00 (UTC). PoR serves a different purpose: each user verifies that their own assets are fully backed. The Futures Insurance Funds are Binance’s own reserve and users can only view their own assets on PoR. Can a user verify their assets are fully backed on Binance? Yes. Users can verify their assets are fully backed on Binance. Learn more here. Note: There may be discrepancies between this original content in English and any translated versions. Please refer to the original English version for the most accurate information, in case any discrepancies arise. Thank you for your support! Binance Team 2026-10-31 Binance
- It's time to turn off the ZCG funding stream. ZCG has over $125M in funding, and will receive millions more before the spigot is turned off. The program was never designed to handle this amount of funding. Draft ZIP: Sean Bowe
- Zcash must remain pure. Free markets. Free speech. It's time to end the Zcash Dev Fund. Josh Swihart 🛡
- Zcash is about to freeze $16 million in its oldest privacy pool COINDESK
- Grayscale Launches Zcash Invest and Commits $1 Million to Support the Zcash Ecosystem - GNW GlobeNewswire
- Zcash's NU7 is scheduled to activate on November 5 at approximately 7:50 PM EST (00:50 UTC November 6). 25-second blocks for faster confirmations, retirement of legacy v4 transactions, and more. Read the full ZIP here: Zcash Open Development Lab
- Grayscale Expands Access to In-Kind Transfers Across Its Digital Asset Investment Platform - GNW GlobeNewswire
- Tachyon Group (led by Sean Bowe) and Shielded Labs just posted a proposal to end future funding of the Zcash Community Grants program and reduce its treasury. ⤵️ zooko🛡🦓🦓🦓 ⓩ
- Zcash holders to vote on pulling 50,000 ZEC from grants treasury COINDESK
- 𝗝𝗨𝗦𝗧 𝗜𝗡: 🚨 UNSHIELDING ALERT 🚨 📉 A wallet just unshielded 50,002.00 ZEC ($45.57M) from the Ironwood pool 🔗 Txn Hash: 🛡 Total shielded ZEC across all pools: 4,931,682.38 ZEC ($4.49B) Shielded Flow🛡️ⓩ
Latest
- THORNODE ❗ MAINNET ❗ MIMIR VOTE: ALLOWNOVAULT ZEC UNTIL 28,731,350 NETWORK: MAINNET TYPE: Coordinated (mimir vote) URGENCY: ASAP The BTC and BCH migrates have gone through. Three retiring vaults still carry ZEC books slightly above their on-chain balance, so Bifrost keeps refusing their migrates. We'll top up those 3 gaps with NOOP:NOVAULT deposits, which only work while ALLOWNOVAULT-ZEC is set, and the 28,729,650 window expired before the ZEC sends landed. The value is a block height, so the gate closes on its own at 28,731,350 (approx. 23:30–23:40 UTC Wed). The migrates then sign at the next re-issue. A NOVAULT deposit can only debit the depositor's own coins, so no vault funds are at risk. MIMIR_KEY=ALLOWNOVAULT-ZEC MIMIR_VALUE=28731350 make mimir key: ALLOWNOVAULT-ZEC value: 28731350 Operational mimir: takes effect with 3 matching node votes. THORChain
- THORNODE ❗ MAINNET ❗ MIMIR VOTE: ALLOWNOVAULT BTC/BCH/ZEC UNTIL 28,729,650 NETWORK: MAINNET TYPE: Coordinated (mimir vote) URGENCY: ASAP The churn migration is stuck on the 6 retiring vaults. Each vault's book is slightly above its on-chain BTC, BCH and ZEC balance (about $56 across 14 vault/chain pairs), so Bifrost refuses the migrates before TSS, and the reschedules keep the same sizing. We'll top up the gaps with NOOP:NOVAULT deposits, which only work while ALLOWNOVAULT-<CHAIN> is set. The value is a block height, so the gate closes on its own at 28,729,650 (approx. 20:40–20:50 UTC Wed). While it's open, a NOVAULT deposit can only debit the depositor's own coins, so no vault funds are at risk. for c in BTC BCH ZEC; do MIMIR_KEY=ALLOWNOVAULT-$c MIMIR_VALUE=28729650 make mimir; done key: ALLOWNOVAULT-BTC value: 28729650 key: ALLOWNOVAULT-BCH value: 28729650 key: ALLOWNOVAULT-ZEC value: 28729650 Operational mimir: takes effect with 3 matching node votes. THORChain
- ## ZecHub Updates | November 17, 2026 :: If you missed our meeting yesterday, here's the summary with all the topics we covered, plus the recording with timestamps. :: :: Key Highlights :: - ZecHub Wiki 3.0 is Live - New Privacy Tools - DAO Governance Updates - New Wiki Learning Paths - Zec Bounties Expansion - NSM Dashboard Support - Q3 2026 Treasury Report - Treasury Transparency :: :: Links :: - | Substack ( - | Free2Z ( - | Youtube ( | :: :: Zcash 🛡️
- Anoma DOS turns one year old today! 🥳 🎉 Time flies when you're shipping non-stop. The first Anoma Protocol Adapter launched on Ethereum 1 year ago. Since then, Anoma landed on 6 more chains, bringing Zcash-grade privacy to over 20 assets with @AnomaPay and @zillions_app. AnomaPay has grown from a private payments app to support private swaps, yield, tokenized stocks, and payroll, becoming a full-suite onchain privacy hub. With Anoma V2 just around the corner, things are just getting started. Cheers to the next 10 years fam 🍻 Anoma
- Bitwise seeks Texas Stock Exchange listing for Zcash ETF COINTELEGRAPH
- From Private Money to Programmable Privacy: Starknet’s Entire Financial Ecosystem Goes Private Zcash pioneered private money. Tornado Cash brought privacy to specific transactions. Starknet is taking the next step: programmable privacy across an entire financial ecosystem, without fragmenting liquidity or forcing users into new applications. For years, privacy has been one of crypto’s most important promises, yet one of its hardest features to use. Every swap, balance, transaction, and financial position recorded on a public blockchain can reveal information about its users. And while several projects have made significant progress toward solving this problem, privacy has often come with trade-offs: limited assets, isolated applications, fragmented liquidity, high costs, or complicated user experiences. What if privacy could simply become a feature of every financial application? That’s what Starknet is building. And with the rollout of STRK20 and Shadow Accounts across its ecosystem, much of that vision is already here. The evolution of privacy in crypto The history of onchain privacy can be understood through three major stages. 1. Private money: Zcash and Monero The first major breakthrough was making cryptocurrency transactions private. Projects like Zcash and Monero pioneered technologies that allow users to transfer and hold value without publicly exposing sensitive transaction information. They established an essential principle: financial privacy is possible on a public blockchain. But as crypto evolved beyond payments into lending, borrowing, trading, staking, and other financial applications, a new challenge emerged. Protecting transfers of a particular cryptocurrency was no longer enough. Users needed privacy across the entire financial system and for all assets. 2. Private transactions: Tornado Cash The next stage brought privacy tools to existing programmable blockchains. Tornado Cash demonstrated how users could use zero-knowledge proofs to break the publicly observable link between deposits and withdrawals on Ethereum. This was an important advancement: privacy no longer needed to exist exclusively within a dedicated privacy-focused blockchain. However, these solutions primarily addressed specific activities rather than providing an integrated privacy experience across DeFi. Users could make a transfer more private, but their subsequent interactions with lending markets, exchanges, liquidity pools, and other applications could still expose their activity. Privacy remained something users accessed separately from most of their financial interactions. Users also faced regulatory risks. For example, the U.S. sanctions imposed on Tornado Cash in August 2022 generally prohibited U.S. persons from transacting with the service. Even those who had deposited funds before the designation needed OFAC authorization to withdraw them. Although these sanctions were lifted in March 2025, the episode illustrated how regulatory action against a privacy tool could create barriers to accessing funds, including for users with legitimate privacy needs. 3. Programmable privacy: Starknet The next step is making privacy programmable. An entire financial ecosystem where users can choose to interact privately with the applications they already know. On Starknet, that means swapping, providing liquidity, trading options, staking, lending, borrowing, earning yield, and making payments with privacy capabilities integrated into existing applications. Importantly, this doesn’t require creating separate private versions of every protocol or splitting liquidity between public and private markets. Same applications. Same liquidity. Public or private modes. The design also addresses a key compliance challenge highlighted by Tornado Cash through deposit screening and strictly targeted disclosure. Regulatory disclosure is permitted only in response to a lawful request, and only for the specific users or transactions it covers. The wider privacy pool is never exposed: everyone else’s private activity remains confidential. This is what makes programmable privacy different. And STRK20 provides the infrastructure that makes it possible. STRK20: One privacy pool for an entire ecosystem STRK20 is Starknet’s privacy framework, enabling shielded balances, private transfers, and private DeFi for ERC-20 assets on Starknet. Its architecture addresses several limitations that have historically made onchain privacy difficult to adopt. One privacy pool, multiple assets; instead of requiring an isolated privacy pool for every token, STRK20 uses a shared, multi-asset privacy pool that supports every ERC-20 tokens on Starknet. Users can shield assets, hold private balances, and transfer them without publicly revealing the sender, receiver, or amount. Privacy without fragmented liquidity; STRK20 works with the DeFi infrastructure already deployed on Starknet. A private swap, for example, can execute against the same public liquidity used by regular traders. Low, predictable fees; privacy needs to be economically accessible if it is to become widely adopted. STRK20 uses a low, flat protocol fee for privacy actions of ~$0.12, rather than charging a percentage of the amount being protected. Privacy accessible from existing wallets; through supported wallets such as Bramble, Xverse, and Ready X, users can shield and unshield assets in just a few clicks, with near-instantaneous shielding flows. From there, they can access applications offering private modes. Privacy with targeted compliance; deposits are screened before entering the pool, and regulatory disclosure is restricted to the specific users or transactions covered by a lawful request. Everyone else’s private activity remains confidential. Shadow Accounts: Making DeFi programmable and private STRK20 introduced the foundation for private balances and transfers. Shadow Accounts extend that foundation to applications requiring persistent user identities, including staking, lending, liquidity provision, and trading. Each application can interact with a separate pseudonymous account whose connection to the user’s main wallet is not publicly exposed. This allows users to maintain positions and interact with protocols over time without directly linking those activities to their main wallet. Shadow Accounts don’t make every detail invisible: the pseudonymous account’s transactions and positions remain publicly observable. Their key privacy property is breaking the public link to the user’s primary identity. Together, STRK20 and Shadow Accounts enable privacy features to be integrated into existing DeFi applications. And the Starknet ecosystem has already put them to work. Introducing Starknet’s programmable privacy ecosystem In just a couple of months, privacy integrations have expanded across the entire Starknet ecosystem, bringing privacy capabilities to virtually every major category of onchain finance. Here’s what users can now do. Shield and unshield assets Bramble, Ready, and Xverse: Shield and unshield crypto assets directly from your wallet, providing an easy entry point into Starknet’s private financial ecosystem. Private trading and liquidity provision avnu; Private swaps: Swap assets privately while accessing existing public liquidity and routing infrastructure, without needing separate private liquidity pools. Ekubo; Private swaps and LPing: Swap tokens, provide liquidity, earn trading fees, and manage LP positions without publicly linking these activities to your wallet. SuperVega; Private options trading: Trade options and manage exposure through Shadow Accounts, bringing privacy to more advanced financial instruments. ArcX; Private points trading and yield generation: Trade points and access yield-generating strategies without publicly linking your activity to your main wallet. Private staking, lending, and yield Endur; Private staking and unstaking: Stake STRK and BTC, earn staking rewards, and unstake through privacy-enabled flows. Troves; Private yield generation: Access automated vaults and yield strategies, including strategies built on Ekubo, without publicly linking positions to you. Vesu; Private lending and borrowing: Lend and borrow assets through Shadow Accounts while maintaining access to Vesu’s existing lending markets. Opus; Private borrowing and stablecoin minting: Borrow and mint CASH, a Starknet-native stablecoin, without publicly linking the activity to your main wallet. Private everyday finance DashX; Private payroll: Enable businesses and organizations to pay contributors without publicly linking those payments to recipients’ identities. Haven; Private neobanking: Bring programmable privacy into everyday financial activities, including holding, transferring, and spending crypto through supported services. Taken together, these integrations represent something much bigger than a collection of privacy features. Users can now access a growing range of financial services with privacy built into the applications they already use, without fragmenting liquidity. They don’t need a separate blockchain for private money, another environment for private trading, and an isolated protocol for private yield. The infrastructure is shared, the applications are familiar, and liquidity can continue flowing through existing markets. This is the transition from isolated privacy solutions to programmable privacy across an entire ecosystem. For users, getting started is straightforward: Choose a supported wallet: Bramble, Ready, or Xverse. Shield your assets: Move tokens into the STRK20 privacy pool. Explore private DeFi: Swap, stake, trade, borrow, lend, and earn yield through the applications offering privacy-enabled flows. For developers, Starkzap has integrated STRK20 and Shadow Accounts, making it easier to add shielded balances, private transfers, and private DeFi to applications through a single TypeScript SDK, alongside its existing wallet and financial tools. Explore the Starknet Privacy Ecosystem → Build with STRK20 → For years, crypto has demonstrated that private money is possible. Now, Starknet is demonstrating that privacy can extend to an entire programmable financial ecosystem. Encrypt your life on Starknet. StarkWare
- Ten years of $ZEC. Why is financial privacy having a moment again? Join Zcash Founder @zooko and our Head of Research @LowBeta for answers in a livestream this Thursday, Nov 19 at 1 PM ET. Grayscale
- The NU7.1 polls are now open! 🗳️ Zcash Coinholders and the Zcash Community Advisory Panel can now weigh in on proposals with the aim of achieving rough consensus on future allocation of Development Funding. 📅Polls close December 1st 02:59 UTC. Zcash 🛡️
- $AVAX, $BTC, $LINK, $ETH, $DOGE, $HYPE, $SOL, $SUI, $XRP, and $ZEC are available for in-kind investing. Exchange your crypto tokens for an ETF and leave self-custody behind. Unlock access to financial advisors, portfolio support, and estate planning. More here: Grayscale
- We've begun reviewing applications and confirming attendees for this January's ZODL Summit in Punta Cana. If you're interested in attending, we encourage you to apply soon. Details below ↓ ZODL | Zcash Open Development Lab
- ZEC: Zcash proposal to delay NSM reserve reissuance from Feb 2031 to the 7th halving (~2044), keeping fees out of circulation longer Proposals
- ## Zebra 7.1.0 Released | Security Update :: The Zcash Foundation ( has released Zebra 7.1.0, addressing 10 security advisories and introducing improvements to node stability, synchronization, and memory management. :: :: Key Highlights :: :: 🔸 10 Security Fixes: Addresses vulnerabilities that could stall synchronization, exhaust node memory, or disrupt transaction processing. 🔸 Improved Sync Reliability: Stronger protection against malicious peers, forged blocks, and stalled block downloads. 🔸 Memory Optimizations: New limits on block queues and shared recent-block data to prevent excessive memory consumption. 🔸 Automatic Peer Recovery: Nodes can reconnect to saved peers and DNS seeders without requiring a restart. 🔸 Enhanced Diagnostics: New sync and memory metrics, improved error reporting, and clearer RPC responses. 🔸 Seamless Upgrade: Operators running Zebra 7.0.0 can upgrade without resyncing or migrating their database. :: Action Required: Node operators, miners, mining pools, exchanges, and wallet infrastructure providers should upgrade immediately. Regular ZEC holders do not need to take action. :: Support Window: Zebra 7.1.0 is supported until approximately December 10, 2026. :: - Read the full release notes ( | :: Zcash 🛡️
- ## Zcash Governance Polls Are Now Open :: Coinholder and community polling is underway to gather feedback on the future of Zcash Community Grants (ZCG), its share of the Development Fund, and proposed protocol changes. :: :: Polls & Announcements: :: 🔸 ZCAP Poll ( 🔸 ZODL Coinholder Poll ( 🔸 Shielded Labs | Governance Announcement ( :: Polling results will help assess whether sufficient consensus exists to move forward with proposed changes through NU7.1. :: Voting Period: November 16–30, 2026 :: - Learn more ( | :: Zcash 🛡️
- Zebra 7.1.0: Security Fixes for Sync and Memory Exhaustion ZEC
- Zcash Update: current=v7.1.0-alpha.0 latest=v7.1.0 THORChain
- ZEC: Zcash ZCAP poll opens on NU7.1: wind down or redirect Community Grants' 8% stream, 50k ZEC to NSM, 20s block time Proposals
- ZCAP Poll Now Open: NU7.1 ZEC
- Winklevoss-backed Cypherpunk buys Zcash dip as mining debut delivers $2.6 million operating profit THE BLOCK
- ## ZF Engineering Update | November 3–16, 2026 :: The Zcash Foundation ( shared its latest engineering update, covering NU7 activation, Zebra performance improvements, infrastructure upgrades, and development across its ecosystem tools. :: :: Key Highlights: :: - NU7 Mainnet Activation: Successfully activated on November 6 at block height 3,543,405. :: - Zebra Ándale: Continued work on faster block templates, block propagation, and verification, with improvements planned for upcoming releases. :: - Node Reliability: Improved peer reconnection, database error reporting, and handling of incomplete block data. :: - CI & Monitoring: Expanded Sentry diagnostics and reduced merge queue unit test times from approximately 14 to 4.5 minutes. :: - Cryptographic Performance: Optimizations across reddsa, pasta_curves, halo2, bellman, and librustzcash. Large-block parsing improved from 21.8 ms to 7.5 ms in benchmarks. :: - Zeal: Zebra Launcher has been rebuilt and renamed Zeal, featuring a local block explorer, experimental light client server, and multiple release channels. :: - Zinder v0.15.1: Added NU7 block support and compatibility testing with Zebra 7 Regtest. :: - Zeeder: Continued migration to the zfnd/zeeder image name. :: *Note: The Zebra improvements described in this update have been merged into the main branch but are not yet included in a published release.* :: 🔸 Read the full update ( | :: Zcash 🛡️
- THE BLOCK: The Winklevoss-backed Zcash treasury firm Cypherpunk reported a $306 million Q3 profit, driven largely by unrealized gains tied to ZEC’s price rise. $CYPH The company now holds 341,859 ZEC, which is about 2% of the circulating supply. $ZEC fell nearly 3% to $869 this morning, extending a monthly decline to more than 25%. The Block
Loading the $ZEC page…