<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>QERYX Guides</title>
    <link>https://qeryx.com/guides</link>
    <atom:link href="https://qeryx.com/guides/rss.xml" rel="self" type="application/rss+xml"/>
    <description>Verification-first guides: check a safety number, read a handshake, verify a Bell binding — instruments you run yourself.</description>
    <language>en</language>
    <item>
      <title>Understand the Handshake</title>
      <link>https://qeryx.com/guides/understand-the-handshake</link>
      <guid isPermaLink="false">qeryx:understand-the-handshake:v1.0</guid>
      <pubDate>Fri, 17 Jul 2026 00:00:00 +0000</pubDate>
      <category>tutorial</category>
      <description>What actually happens in the second before your first message sends: two key exchanges run side by side — X25519 and ML-KEM-1024 — both peers contribute quantum-sourced entropy, and each leg is signed under its own FIPS 204 context. A plain-language walk through Entangled Session v1.</description>
    </item>
    <item>
      <title>Verify a Bell Binding</title>
      <link>https://qeryx.com/guides/verify-a-bell-binding</link>
      <guid isPermaLink="false">qeryx:verify-a-bell-binding:v1.1</guid>
      <pubDate>Fri, 17 Jul 2026 00:00:00 +0000</pubDate>
      <category>how-to</category>
      <description>How a third party — an auditor, a journalist, a counterparty — checks that a session claiming a Bell binding really consumed a CHSH-verified transcript: fetch the transparency leaf, verify the Merkle inclusion proof, recompute S from the measurement counts, and confirm it sits in the accepted window. No trust in QERYX required.</description>
    </item>
    <item>
      <title>Verify Your Safety Number</title>
      <link>https://qeryx.com/guides/verify-your-safety-number</link>
      <guid isPermaLink="false">qeryx:verify-your-safety-number:v1.0</guid>
      <pubDate>Fri, 17 Jul 2026 00:00:00 +0000</pubDate>
      <category>how-to</category>
      <description>The one manual step that closes the machine-in-the-middle door. What the safety number is, why the Key Transparency log cannot replace an out-of-band check, and the exact steps to run one — in person, over a call, or by QR. Five minutes, once per contact.</description>
    </item>
    <item>
      <title>What a Subpoena Yields</title>
      <link>https://qeryx.com/guides/what-a-subpoena-yields</link>
      <guid isPermaLink="false">qeryx:what-a-subpoena-yields:v1.0</guid>
      <pubDate>Fri, 17 Jul 2026 00:00:00 +0000</pubDate>
      <category>tutorial</category>
      <description>The honest inventory of what a legal order against the QERYX relay can and cannot produce: ciphertext the order-holder cannot decrypt, blinded participant hashes, connection-level metadata — and, for destroyed conversations, envelope-locked bytes under a key that no longer exists. No dramatization; the table is the answer.</description>
    </item>
    <item>
      <title>The Reviewer FAQ</title>
      <link>https://qeryx.com/guides/reviewer-faq</link>
      <guid isPermaLink="false">qeryx:reviewer-faq:v1.0</guid>
      <pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate>
      <category>tutorial</category>
      <description>State-actor-tier reviewer questions, anticipated and answered: why Level 5 parameter sets, why hybrid rather than pure post-quantum, where formal verification stands, how side-channel classes are foreclosed, what happens when operator keys are compromised, and where to find a wire trace you can verify yourself.</description>
    </item>
  </channel>
</rss>
