Starknet Sets 2027 Deadline for Post-Quantum Security
Starknet Sets 2027 Deadline for Post-Quantum Security
⏰ Quantum deadline set
Starknet has announced a concrete timeline to achieve full post-quantum security by 2027, addressing the looming threat of quantum computers breaking current cryptographic systems.
Key developments:
- Eli Ben-Sasson outlined the implementation roadmap in a brief video explanation
- The network already has foundational advantages: hash-based STARKs and Native Account Abstraction
- Post-quantum wallets are deployable on Starknet today
The urgency stems from "Q Day" - when quantum computers will be powerful enough to break existing crypto security. Starknet's Native AA architecture allows security protocols to evolve without requiring protocol-level changes, providing flexibility as quantum threats develop.
This positions Starknet as an early mover in quantum-resistant blockchain infrastructure.
Starknet will be post-quantum secure by 2027. Watch @EliBenSasson explain the roadmap in under two minutes.
1/ Starknet is a bet on post-quantum security. Today, we’re publishing the roadmap to make that bet real. The goal? An end-to-end post-quantum secure Starknet before Q-day 🧵
Q Day is coming. The cryptography securing crypto today has an expiry date. Starknet has a head start: hash-based STARKs, Native AA that lets security evolve without protocol changes, and post-quantum wallets already deployable today. Starknet's Post-Quantum roadmap is here:
1/ Starknet is a bet on post-quantum security. Today, we’re publishing the roadmap to make that bet real. The goal? An end-to-end post-quantum secure Starknet before Q-day 🧵
Starknet Surpasses $500K in Shielded Assets with One-Click Privacy
**Starknet has crossed a significant milestone** with over $500,000 now shielded on its network, according to analytics from StarkscanCo. **Key developments:** - One-click privacy functionality is gaining traction across multiple assets - The platform continues its mission to deliver privacy at scale for various use cases - Adoption is accelerating as users embrace simplified privacy tools This milestone represents growing demand for **accessible privacy solutions** in the blockchain ecosystem. The one-click approach removes technical barriers that previously limited privacy adoption. Starknet's privacy infrastructure aims to make shielded transactions as simple as standard transfers, potentially reshaping how users interact with blockchain assets.
🔧 STRK20 Shielding Temporarily Disrupted After Contract Upgrade
**Issue and Resolution** A STRK20 contract upgrade on July 9, 2026 caused temporary disruption to new shielding deposits. The problem stemmed from a verification issue with screening signatures. **What Was Affected** - New shielding deposits were temporarily unavailable - Existing shielded assets remained accessible for unshielding - Private transfers continued functioning normally - User assets were never at risk during the downtime The issue has been resolved and shielding functionality is now fully operational again.
Starknet v0.14.3 Goes Live with 1.5s Blocks and Dynamic Gas Fees
Starknet v0.14.3 is now live on Mainnet, bringing several technical improvements to the network. **Key upgrades include:** - **Dynamic L2 gas base fee** - Automatic algorithm adjusts minimum gas fees based on STRK price for more stable real-world costs - **1.5 second block times** - Reduced from previous intervals for lower transaction latency - **Enhanced prover/verifier capabilities** - New support for privacy-related transaction flows - **BLAKE-based SNOS hash** - Part of long-term security infrastructure improvements **Developer considerations:** Projects building fee estimation, sponsored transactions, paymasters, wallets, or account abstraction should review fee assumptions and consider larger buffers during price-adjustment periods. Full technical documentation and compatibility details are available through the governance proposal and community forums.
🚨 RPC 0.8 Support Ends: Migration Required
**Breaking Change Alert** Starting with v0.14.3, RPC 0.8 is officially deprecated. Full nodes and SDKs will no longer release versions supporting it. **Action Required:** - Migrate to RPC 0.9 or RPC 0.10.1/0.10.2 immediately - Review your infrastructure if you rely on candidate transaction timing **Key Change:** Candidate transaction latency will now match preconfirmed transactions - no performance advantage. Apps depending on faster candidate transaction speeds need to reassess UX and infrastructure assumptions. This follows the earlier deprecation of RPC versions below 0.7, which was announced with Starknet v0.13.4. The ecosystem continues moving toward newer RPC versions for improved features like storage proofs and L2 gas support.