<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>RFWIN Blog</title>
    <link>https://rfwin.uk/blog/</link>
    <description>Verifiable winner selection in practice: how RFWIN draws work, on-air giveaways for radio, and how AI assistants check who won.</description>
    <language>en</language>
    <atom:link href="https://rfwin.uk/blog/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>RFWIN for Radio: Run On-Air Giveaways Listeners Can Check</title>
      <link>https://rfwin.uk/blog/rfwin-for-radio-on-air-giveaways/</link>
      <guid isPermaLink="true">https://rfwin.uk/blog/rfwin-for-radio-on-air-giveaways/</guid>
      <pubDate>Sat, 14 Nov 2026 12:00:00 GMT</pubDate>
      <category>How-to guides</category>
      <description>A practical guide for stations, podcasters and DJs: run a listener draw with backup winners, put your station and show on the proof page, read it on air and share the link.</description>
    </item>
    <item>
      <title>How RFWIN Picks a Winner You Can Check</title>
      <link>https://rfwin.uk/blog/how-rfwin-picks-a-winner/</link>
      <guid isPermaLink="true">https://rfwin.uk/blog/how-rfwin-picks-a-winner/</guid>
      <pubDate>Sat, 14 Nov 2026 12:00:00 GMT</pubDate>
      <category>Product</category>
      <description>RFWIN combines a committed server seed, the drand public randomness beacon and a hash of the entry list, then publishes a proof page that anyone, or any AI assistant, can re-check.</description>
    </item>
    <item>
      <title>Ask Your AI Who Won: Verifying RFWIN Draws with MCP and REST</title>
      <link>https://rfwin.uk/blog/ask-your-ai-who-won-rfwin-verify/</link>
      <guid isPermaLink="true">https://rfwin.uk/blog/ask-your-ai-who-won-rfwin-verify/</guid>
      <pubDate>Sat, 14 Nov 2026 12:00:00 GMT</pubDate>
      <category>AI agents &amp; MCP</category>
      <description>RFWIN proof pages are written for people and machines. Here is how AI assistants and agents read a draw, run the fairness check with verify_draw or the REST verify endpoint, and run draws of their own.</description>
    </item>
  </channel>
</rss>
