hodler

3 Jun 2026, 12:15

Zcash Completes Emergency Hard Fork to Patch Critical Double-Spend Vulnerability

BitcoinWorld Zcash Completes Emergency Hard Fork to Patch Critical Double-Spend Vulnerability Zcash has successfully completed an emergency hard fork, designated NU 6.2, to address a critical flaw in its zero-knowledge proof circuit that could have allowed attackers to double-spend the privacy-focused cryptocurrency. The upgrade, executed five days after the vulnerability was discovered, reactivates the temporarily suspended Orchard privacy pool with a fully patched circuit, permanently eliminating the risk. Timeline and Technical Details The vulnerability was identified by the Zcash development team during routine internal security audits. Upon discovery, the team immediately suspended the Orchard pool—the network’s most advanced privacy protocol—to prevent potential exploitation. The emergency hard fork was deployed within five days, a notably fast response for a blockchain network requiring widespread node coordination. The flaw resided in the zero-knowledge proof circuit that underpins the Orchard pool. Zero-knowledge proofs allow transactions to be verified without revealing sender, receiver, or amount. A bug in this circuit could have enabled a malicious actor to create valid proofs for spending the same funds multiple times—a classic double-spend attack that undermines the entire value proposition of a cryptocurrency. Why This Matters For Zcash users, the double-spend vulnerability posed a direct threat to the network’s core promise: private, secure, and sound digital cash. Had the flaw been exploited, it could have led to significant financial losses and eroded trust in the protocol’s privacy guarantees. The incident also highlights the broader challenges facing privacy-focused cryptocurrencies. Zcash’s zero-knowledge proof technology is among the most sophisticated in the industry, but it also introduces complexity that can harbor subtle bugs. The rapid response demonstrates the maturity of the Zcash development community, but it also serves as a reminder that even battle-tested cryptographic systems require continuous vigilance. Impact on the Orchard Pool The Orchard pool, introduced in the NU5 upgrade in 2022, represented a major leap forward for Zcash privacy. It unified the network’s two previous privacy pools (Sprout and Sapling) and introduced a more efficient zero-knowledge proof system. The temporary suspension of Orchard during the fix meant that users could not create new Orchard-shielded transactions, though Sapling and transparent transactions remained unaffected. With NU 6.2, the Orchard pool is now fully operational with the patched circuit. Market and Community Reaction The Zcash community has largely praised the development team for its transparency and speed. The vulnerability was disclosed responsibly, and the hard fork was executed without major disruption. Zcash’s native token, ZEC, experienced minor volatility during the suspension but has since stabilized, indicating that the market views the incident as a contained security event rather than a systemic failure. Industry observers note that the incident underscores the importance of rigorous security audits for privacy protocols, which are often subject to heightened scrutiny from regulators and users alike. Zcash’s handling of the situation may reinforce confidence in its development process, but it also invites comparisons to other privacy coins that have faced similar challenges. Conclusion The Zcash NU 6.2 emergency hard fork effectively neutralized a critical double-spend vulnerability, restoring full functionality to the Orchard privacy pool. The event demonstrates the resilience of the Zcash network and the dedication of its development team, while also serving as a cautionary tale about the inherent risks in cutting-edge cryptographic systems. For users and investors, the key takeaway is that Zcash remains committed to security and transparency, even when faced with high-stakes technical challenges. FAQs Q1: What was the vulnerability in Zcash’s Orchard pool? The vulnerability was a bug in the zero-knowledge proof circuit that could have allowed an attacker to create valid proofs for spending the same funds multiple times, enabling a double-spend attack. Q2: How quickly did Zcash respond to the bug? The Zcash team discovered the flaw, suspended the Orchard pool, and deployed the NU 6.2 emergency hard fork within five days, which is considered a rapid response for a blockchain network. Q3: Is my Zcash safe after the hard fork? Yes. The vulnerability has been permanently patched with the NU 6.2 upgrade. Users can now use the Orchard pool normally, and no funds were lost or exploited during the incident. This post Zcash Completes Emergency Hard Fork to Patch Critical Double-Spend Vulnerability first appeared on BitcoinWorld .

3 Jun 2026, 01:13

Bnb transaction fees fall below $0.01 after four upgrades

🚀 BNB Chain transaction fees fell below $0.01 after four protocol upgrades. Block time is now down to 0.45 seconds, boosting daily activity to record highs at 31 million transactions. 🔥 Over $1 billion worth of BNB was burned in Q1 2026 through the BEP-95 system. 💡 Real world assets and stablecoins like $BNB are fueling ecosystem growth. Continue Reading: Bnb transaction fees fall below $0.01 after four upgrades The post Bnb transaction fees fall below $0.01 after four upgrades appeared first on COINTURK NEWS .

2 Jun 2026, 17:15

Ethereum Researchers Propose Quantum-Resistant Key Registry to Secure Network

BitcoinWorld Ethereum Researchers Propose Quantum-Resistant Key Registry to Secure Network Ethereum researchers, including prominent contributors Thomas Coratger and Justin Drake, have proposed a new design for a key registry that could serve as the first concrete step toward making the Ethereum network resistant to attacks from quantum computers. The proposal, reported by The Defiant, addresses a growing concern in the blockchain industry: the eventual ability of quantum computers to break the cryptographic keys that currently secure billions of dollars in digital assets. Why Quantum Resistance Matters for Ethereum Quantum computers, once sufficiently advanced, could theoretically break the Elliptic Curve Digital Signature Algorithm (ECDSA) and BLS (Boneh-Lynn-Shacham) signature schemes that underpin Ethereum’s security. This would allow an attacker to derive private keys from public ones, potentially stealing funds or disrupting validator operations. While large-scale, fault-tolerant quantum computers are likely years away, the Ethereum research community has begun proactive planning to ensure the network can transition smoothly before such a threat materializes. The Proposed Solution: A Post-Quantum Key Registry The research team’s proposal introduces a ‘PQ key registry’ (post-quantum key registry) that would allow validators to register new, quantum-resistant public keys while continuing to use their existing BLS-based keys for current operations. This dual-key approach is conceptually similar to issuing a more secure form of identification that is held in reserve until it is needed. The registry would be a smart contract on Ethereum that stores these new keys, ensuring transparency and decentralization. Two-Phase Transition Plan The transition is designed to occur in two distinct phases. In the first phase, validators voluntarily register their quantum-resistant keys. This phase imposes no immediate change to network operations. The second phase would be triggered once a supermajority of validators have registered their new keys. At that point, the Ethereum protocol would switch to using the registered quantum-resistant keys for signature verification, effectively upgrading the network’s cryptographic backbone without requiring a hard fork that forces all participants to upgrade simultaneously. Implications for Validators and the Ecosystem For validators, the proposal offers a non-disruptive path to enhanced security. They can generate and register their new keys at their own pace, using their existing infrastructure. For the broader Ethereum ecosystem, this proactive approach signals a commitment to long-term security and stability, which could bolster institutional confidence. The research is still in its early stages, and the team has not announced a formal Ethereum Improvement Proposal (EIP) or timeline for implementation. Conclusion The proposal by Coratger, Drake, and their colleagues represents a significant forward-looking effort to safeguard Ethereum against a future quantum threat. By introducing a voluntary key registry and a gradual transition plan, the researchers aim to minimize disruption while ensuring the network remains secure for decades to come. The crypto community will be watching closely for further technical details and a potential formal proposal. FAQs Q1: What is a quantum-resistant key? A quantum-resistant key uses cryptographic algorithms that are believed to be secure against attacks from both classical and quantum computers. Unlike current ECDSA or BLS keys, they are designed to withstand the mathematical problems that quantum computers could solve efficiently. Q2: When will quantum computers be able to break Ethereum’s encryption? Most experts agree that large-scale, fault-tolerant quantum computers capable of breaking current encryption are at least a decade away. However, the Ethereum research community is acting proactively to ensure a smooth transition well before the threat becomes imminent. Q3: Will validators be forced to upgrade? No. The proposed design is voluntary in its first phase. Validators can register new keys at their own pace. The second phase, which would switch the network to use the new keys, would only activate after a supermajority of validators have registered. This post Ethereum Researchers Propose Quantum-Resistant Key Registry to Secure Network first appeared on BitcoinWorld .

2 Jun 2026, 13:52

Zcash validators adopt emergency hard fork-style upgrade after Orchard vulnerability discovery

Developers said no funds were lost and privacy remains intact, but Orchard transactions were temporarily suspended during the upgrade rollout.

2 Jun 2026, 03:20

Blockworks Steps Down as Arbitrum DAO Delegate, Citing Business Priorities

BitcoinWorld Blockworks Steps Down as Arbitrum DAO Delegate, Citing Business Priorities Blockworks, a media and events company focused on digital assets, has announced it is phasing out its role as a delegate within the Arbitrum DAO. The decision, shared via the company’s official X account, was framed as a strategic move aligned with its evolving business objectives. Strategic Shift, Not a Vote of No Confidence In its announcement, Blockworks emphasized that the move does not reflect a negative outlook on the future of the Arbitrum DAO or its governance model. The company stated it remains committed to collaborating with key ecosystem players, including the Arbitrum Foundation and Offchain Labs, the development firm behind the Arbitrum network. This departure comes several months after Blockworks revealed it was shutting down its news division late last year, a restructuring that redirected the company’s focus toward events, research, and other commercial offerings. The decision to exit the delegate role appears to be a continuation of that broader operational realignment. Context and Implications for DAO Governance Blockworks had been an active delegate in the Arbitrum DAO, participating in governance votes and helping shape proposals for the Layer 2 scaling network. Delegates in DAOs play a critical role in ensuring decentralized decision-making, often representing the interests of token holders who may not have the time or expertise to vote on every proposal. The departure of a well-known media entity like Blockworks raises questions about the sustainability of delegate participation from organizations outside the core development ecosystem. However, Blockworks’ assurance of continued collaboration suggests the relationship is shifting rather than ending. What This Means for the Arbitrum Ecosystem Arbitrum remains one of the largest and most active Layer 2 networks by total value locked and daily transactions. The DAO oversees a substantial treasury and coordinates protocol upgrades, grant programs, and community initiatives. While any delegate exit can temporarily reduce governance bandwidth, the Arbitrum DAO has a diverse set of delegates, including foundations, investment firms, and community members, which may absorb the change without major disruption. For Blockworks, stepping away from delegate duties allows the company to concentrate resources on its core revenue-generating activities. The company’s ongoing ties with the Arbitrum Foundation and Offchain Labs indicate that the decision is operational rather than ideological. Conclusion Blockworks’ exit as an Arbitrum DAO delegate marks a notable but not unexpected development, given its recent pivot away from news publishing. The move underscores the evolving relationship between media entities and the DAOs they cover, as companies increasingly weigh governance participation against business priorities. The Arbitrum DAO continues to operate with a broad delegate base, and Blockworks’ decision appears unlikely to materially affect governance outcomes. FAQs Q1: Why did Blockworks leave the Arbitrum DAO delegate role? A1: Blockworks stated the decision aligns with its current business objectives. It was not a reflection of any negative view on the Arbitrum DAO’s future. Q2: Will Blockworks still work with Arbitrum-related projects? A2: Yes. Blockworks confirmed it will continue collaborating with the Arbitrum Foundation and Offchain Labs. Q3: Does this affect the Arbitrum DAO’s governance? A3: The Arbitrum DAO has a diverse set of delegates, so the departure of one delegate is unlikely to have a significant impact on governance operations. This post Blockworks Steps Down as Arbitrum DAO Delegate, Citing Business Priorities first appeared on BitcoinWorld .

1 Jun 2026, 11:30

Base’s state update system went down and nobody noticed

A bug inside Coinbase’s Base froze a critical part of the network’s infrastructure. It has raised fresh questions around the resilience of Ethereum’s growing Layer-2 ecosystem. However, the issue did not stop users from sending transactions or interacting with applications on Base. Blocks reportedly continued to be produced and the network appeared to function normally. But behind the scenes, a key component which aws responsible for updating Base’s state on Ether stalled for more than 30 hours. This event came to notice after developers flagged that the state updates and withdrawals to Ether were stopped. Base’s 30-hour glitch raised layer-2 concerns Developer donnoh.eth addressed the issue in an X post. He noted that the outage went unnoticed because Base withdrawals already require a seven-day challenge period. He stated that “It’s kind of crazy that Base state updates have been down for over 30 hours now because of some bug related to the recent upgrade and no one even noticed just because withdrawals take seven days anyway.” According to Base’s status page , the problem was traced to the network’s Trusted Execution Environment (TEE) enclave. The malfunction prevented the proposal system from generating the state updates needed to anchor Base’s activity back to Ethereum. The chain kept itself processing and was moving transactions normally. Meanwhile, Base’s state effectively stopped updating until the issue was resolved. In the case of rollup like Base, transitions are executed on L2 before compressed state commitments are periodically posted back to Ether. The TEE helps to generate cryptographic attestations. This helps in proving that state transitions were computed correctly. This suggests that when that system stops working, users can continue transacting on Layer 2. Meanwhile, the settlement pipeline connecting the network back to Ethereum can grind to a halt. No funds were lost and the outage did not expose user assets to theft. But still, it did temporarily freeze one of the most important pieces of infrastructure supporting the rollup. It stands crucial that, as it happened just a few days after Base deployed its Azul upgrade. It was designed to improve scalability and reportedly increase throughput to as much as 5,000 transactions per second. Despite this, the network found itself struggling. Base and Sui face different failure modes Earlier this year, Base saw periods of transaction delays during heavy network activity. However, those issues never halted settlements. Yet, they exposed capacity constraints as usage continued growing. Base is not alone that faced this problem. Sui reported a consensus failure that disrupted transaction processing for roughly six hours in January. The network experienced multiple outages tied to software bugs introduced during protocol upgrades. It temporarily freezes transfers, DeFi activity, and NFT transactions. The tech involved behind those incidents are very different. Base saw outage that involved a TEE-assisted proving mechanism. On the other side, Sui’s problems emerged from validator consensus and gas-accounting logic. The smartest crypto minds already read our newsletter. Want in? Join them .