Merkle Tree Certificates Proposed to Enable Lightweight Post-Quantum HTTPS in Chrome
Google Chrome developers, working with colleagues from other companies and experts from the IETF PLANTS working group, are preparing the first HTTPS change aimed at solving performance problems expected from post-quantum cryptography. The solution is Merkle Tree Certificates (MTC), compact TLS certificates built on Merkle trees that replace heavy signature chains with lightweight inclusion proofs.
Why post-quantum cryptography needs smaller certificates
Post-quantum cryptographic algorithms typically produce larger keys and signatures than classical schemes, increasing both network traffic and computational load during TLS handshakes. Merkle Tree Certificates address this by having a certificate authority sign only the root of a Merkle tree; each individual MTC then serves as a compact proof that a particular certificate is included in that tree.
In the new model, the amount of authentication data sent to the browser shrinks dramatically compared with conventional X.509 chains, allowing strong post-quantum algorithms to be deployed without slowing down web connections. An additional security benefit is built-in transparency: because every certificate must be recorded in the public Merkle tree, the properties of today’s Certificate Transparency ecosystem become mandatory by default.
How Merkle Tree Certificates work
A Merkle tree is constructed by hashing individual records and then repeatedly hashing pairs of hashes until a single root hash remains. To prove that a specific record belongs to the tree, only the hashes along the path from the record to the root are required. The scheme has been extended to support trees of arbitrary size (not just powers of two) and to allow efficient proofs that one log is a prefix of another.
These properties make MTC suitable for real-world certificate issuance at internet scale while maintaining the auditability required by modern public-key infrastructure.
Chrome deployment timeline
Performance testing of TLS connections using MTC is already being conducted in collaboration with Cloudflare. After validation of the core technology in early 2027, operators of existing Certificate Transparency logs that are trusted by Chrome will be invited to run the first public MTC logs. By the third quarter of 2027, requirements for additional certificate authorities to join a dedicated post-quantum Chrome Root Store supporting only MTC are expected to be finalized. This new root store will operate alongside the current Chrome Root Store.
The field is evolving rapidly, and the outlined schedule may be adjusted as implementation experience grows.
Related articles
Peter Levashov Accused of FBI Collaboration and Running XSS Honeypot Forum After Kelihos Sentence
Russian spammer and botnet operator Petr Levashov, known online as Petr Severa, was arrested in Barcelona in 2017 and later pleaded guilty to running the Storm, Waledac and Kelihos botnets. He received a lenient sentence of under three years despite prosecutors seeking 14.5 years, which experts attribute to possible cooperation with the FBI. After release, Levashov remained in the United States while remaining wanted in Russia. Forum users bratva and stallman on XSS.mx and Exploit.in have been linked to Levashov through stylistic analysis and shared references to the Telegram channel Dark News admin nicknamed golub. Stallman, identified as the final administrator of the RAMP4u forum, openly purchased access to U.S. critical infrastructure including power grids, water systems and hospitals while moderators allegedly suppressed competing posts. Observers including researcher Olga Kuprina suggest these accounts operated under agreements with U.S. authorities, allowing forums to function as intelligence-gathering platforms rather than purely criminal marketplaces.
Russian Cybersecurity Market Set to Hit 455 Billion Rubles by 2026 as Talent Shortage Persists
MWS Cloud forecasts that the Russian information security market will grow 20.8 percent to reach 455.4 billion rubles in 2026. The largest segment will be software at 216.5 billion rubles, followed by services at 167 billion and hardware at 71.9 billion rubles. Demand is increasingly driven by sophisticated attacks, regulatory requirements and fines rather than import substitution alone. BI.ZONE offers a more conservative estimate of 10-15 percent annual growth. Managed security services such as monitoring, incident response and vulnerability management are leading the services segment because few organizations can maintain 24/7 in-house teams. Director Artem Gribkov of Angara MTDR estimates the personnel deficit at approximately 40 percent, especially at middle and senior levels.
Russian Internet Users Report Growing Access Restrictions as Certificate Revocations Affect 39 Percent of Respondents
A recent telephone survey conducted by Russian Field between September 23 and 30, 2026, among 1,600 participants representative by gender, age, federal districts, and settlement types shows that 39 percent of Russian internet users have noticed restrictions or complications when trying to access websites. When sites fail to open due to certificate problems, 26 percent of respondents said they would simply stop visiting the resource. The findings, published by Kod.ru, also indicate that 57 percent of users are aware that Russian websites may not load in certain browsers because of revoked foreign certificates. In response to certificate errors, 55 percent would switch browsers, 22 percent would install the required certificates, and 21 percent would try accessing the site from a mobile device. Younger users are more inclined to use VPNs or proxies, while older respondents more often choose to abandon the site. Overall, 77 percent of those surveyed expect further changes to the Russian internet segment, with only 9 percent believing it will remain unchanged.
CISA and NSA Urge Shift to Memory-Safe Languages Like Rust to Eliminate Memory Vulnerabilities
Official reports from CISA, NSA, FBI and partners highlight that decades of safe coding practices and code analysis tools have failed to resolve memory safety issues in languages such as C and C++. Government documents cite statistics showing that 70-75% of exploited vulnerabilities and zero-days stem from memory errors, including data from Microsoft, Google Chromium, Mozilla and Project Zero. Google reports that Rust adoption in Android reduced memory-related vulnerabilities below 20% in 2025, with a 1000-fold lower vulnerability density compared to C++. The analysis details Rust's ownership, borrowing and move semantics that provide compile-time guarantees unavailable in C++, enabling stronger compiler optimizations. Reports also acknowledge migration challenges including learning curves, interop issues and ecosystem gaps, while noting ongoing C++ safety improvements targeted for C++26 and C++29. Major organizations including Microsoft, Amazon and Google are already committing to Rust for critical new code.