<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Applied PQC</title>
  <link href="https://appliedpqc.io/"/>
  <link rel="self" href="https://appliedpqc.io/feed.xml"/>
  <id>https://appliedpqc.io/</id>
  <updated>2026-08-28T00:00:00Z</updated>
  <subtitle>Where post-quantum cryptography actually stands: what has shipped, what is still a draft, and what breaks when you deploy it. Byte-exact implementations of all four standards.</subtitle>
  <entry>
    <title>The construction of SHRINCS, a semi-stateful hash-based signature scheme</title>
    <link href="https://appliedpqc.io/blog-shrincs-construction.html"/>
    <id>https://appliedpqc.io/blog-shrincs-construction.html</id>
    <updated>2026-08-28T00:00:00Z</updated>
    <summary>SHRINCS demotes SLH-DSA to a fallback path and puts a 548-byte stateful signature on the primary one. What the draft reuses from FIPS 205, what it only reparameterises, what it constructs anew, and what it gives up.</summary>
  </entry>
  <entry>
    <title>Post-quantum migration for Bitcoin layer 2s</title>
    <link href="https://appliedpqc.io/blog-bitcoin-l2-post-quantum.html"/>
    <id>https://appliedpqc.io/blog-bitcoin-l2-post-quantum.html</id>
    <updated>2026-07-31T00:00:00Z</updated>
    <summary>A Bitcoin layer 2 settles to a base layer it cannot change, borrows consensus from a third ecosystem, and runs a bridge whose trust root is cryptography of its own choosing. Where the post-quantum exposure actually sits, and who can fix each part.</summary>
  </entry>
</feed>
