Draft: Let's Encrypt Picks Merkle Tree Certificates as Its Post-Quantum Issuance Path#32
Draft
krakenhavoc wants to merge 1 commit into
Draft
Draft: Let's Encrypt Picks Merkle Tree Certificates as Its Post-Quantum Issuance Path#32krakenhavoc wants to merge 1 commit into
krakenhavoc wants to merge 1 commit into
Conversation
Let's Encrypt announced June 3 that MTCs, not ML-DSA X.509, are their planned PQ issuance architecture. Covers the sizing math, MTC batch signing, operational dependencies that break (chain inspection, OCSP, intermediate pinning), and the immediate action: X25519MLKEM768 key exchange.
Deploying web with
|
| Latest commit: |
70c5c6f
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://ec7aba07.web-f5e.pages.dev |
| Branch Preview URL: | https://claude-confident-tesla-9px33.web-f5e.pages.dev |
This was referenced Jun 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
New blog post for 2026-06-10. Covers Let's Encrypt's June 3 announcement that Merkle Tree Certificates, not traditional ML-DSA X.509, are their planned post-quantum issuance path.
Sources
Uniqueness check
Three most recent existing posts reviewed:
public-ca-eku-separation-june-2026.md(2026-05-27) - clientAuth EKU removal from public TLS intermediates. No overlap.lets-encrypt-generation-y-transition.md(2026-05-13) - Generation Y intermediate rollout and May 8 issuance incident. No overlap.post-quantum-tls-certificate-readiness.md(2026-04-19) - NIST PQC standards, ML-DSA algorithm sizes, operational planning for the 2030-2035 deprecation timeline. This post is thematically adjacent but covers a different subject: the April post is about NIST deadlines and operational planning; this post is about a specific architectural departure from ML-DSA-in-X.509 and what it means for tooling that assumes the conventional cert chain model.Why this topic this week
Let's Encrypt's June 3 post is the first public commitment to MTCs as their production path with a concrete timeline (staging late 2026, production 2027), and the MTC architecture breaks several widely-held assumptions about what post-quantum certificate tooling will look like.