<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Quantor blog</title>
    <link>https://quantorsaas.app/blog</link>
    <description>Long-form on signed builds, regime-aware trading, and self-custody. Engineering, not marketing.</description>
    <language>en</language>
    <lastBuildDate>Sun, 11 May 2026 20:30:00 +0000</lastBuildDate>
    <atom:link href="https://quantorsaas.app/blog/feed.xml" rel="self" type="application/rss+xml"/>

    <item>
      <title>Why we don't promise yield (and why every bot that does should worry you)</title>
      <link>https://quantorsaas.app/blog/no-yield-promise</link>
      <guid isPermaLink="true">https://quantorsaas.app/blog/no-yield-promise</guid>
      <pubDate>Sun, 11 May 2026 20:30:00 +0000</pubDate>
      <description>Most crypto bot landing pages lead with a yield number. The compounding math makes those claims physically implausible; the regulatory landscape makes them illegal where it applies; the historical pattern of how the yield-promising bots end shows the failure mode. Walks the math, the regulation, the three terminal states, and a five-question buying checklist for any bot — including ours.</description>
      <category>Industry</category>
      <category>Trading bot scam</category>
    </item>

    <item>
      <title>The 14 risk gates we run before a LIVE bot starts trading your money</title>
      <link>https://quantorsaas.app/blog/14-risk-gates</link>
      <guid isPermaLink="true">https://quantorsaas.app/blog/14-risk-gates</guid>
      <pubDate>Sun, 11 May 2026 20:00:00 +0000</pubDate>
      <description>Before a single real order leaves the api, fourteen independent checks fire — symbol allowlist, regime classifier, kill switch, beta allowlist, notional sanity, subscription, bot count, plan permissions, Telegram link, strategy compatibility, exchange-key verification, and the final risk evaluator. Walks each gate with the exact reason code the api emits.</description>
      <category>Risk</category>
      <category>Live trading safety</category>
    </item>

    <item>
      <title>Self-custody by construction — why your trading bot shouldn't hold your funds</title>
      <link>https://quantorsaas.app/blog/self-custody-by-construction</link>
      <guid isPermaLink="true">https://quantorsaas.app/blog/self-custody-by-construction</guid>
      <pubDate>Sun, 11 May 2026 19:30:00 +0000</pubDate>
      <description>Quantor never touches your funds, by construction. The exchange API key has trade-only scope, the database stores only an AES-GCM blob, the master key lives in a separately-administered Secret Manager, and the exchange itself refuses withdrawal. Even if the entire company disappeared tomorrow, your money sits in your exchange account untouched.</description>
      <category>Security</category>
      <category>Self-custody</category>
    </item>

    <item>
      <title>The regime detector — what we kill live trades on, and why</title>
      <link>https://quantorsaas.app/blog/regime-detector</link>
      <guid isPermaLink="true">https://quantorsaas.app/blog/regime-detector</guid>
      <pubDate>Sun, 11 May 2026 19:00:00 +0000</pubDate>
      <description>A 50-line classifier — realized daily volatility plus drawdown from peak — decides when Quantor refuses to start LIVE bots. Walks through the algorithm, the four thresholds, the historical windows (2020-03-12, Luna, FTX, 2024 yen unwind) where it would have fired, and the upside we accept giving up in exchange.</description>
      <category>Risk</category>
      <category>Market regime</category>
    </item>

    <item>
      <title>How we sign every prod deploy with Ed25519 — and why your bot doesn't</title>
      <link>https://quantorsaas.app/blog/signed-builds-ed25519</link>
      <guid isPermaLink="true">https://quantorsaas.app/blog/signed-builds-ed25519</guid>
      <pubDate>Sun, 11 May 2026 15:30:00 +0000</pubDate>
      <description>Most crypto-bot SaaS ask you to trust them. Quantor signs every production deploy with an offline Ed25519 key and publishes the public key. Walks through the exact mechanism, threat model, and three verification recipes.</description>
      <category>Security</category>
      <category>Ed25519</category>
    </item>

  </channel>
</rss>
