<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Tom</title>
    <description>The latest articles on DEV Community by Tom (@human2001).</description>
    <link>https://dev.to/human2001</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3877711%2F254efe6e-2a59-4512-a02a-ce2b091f9b43.png</url>
      <title>DEV Community: Tom</title>
      <link>https://dev.to/human2001</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/human2001"/>
    <language>en</language>
    <item>
      <title>Server builds, wallet signs, webhooks confirm — a non-custodial Web3 checkout pattern with Solana</title>
      <dc:creator>Tom</dc:creator>
      <pubDate>Sun, 19 Apr 2026 15:19:24 +0000</pubDate>
      <link>https://dev.to/human2001/server-builds-wallet-signs-webhooks-confirm-a-non-custodial-web3-checkout-pattern-with-solana-29ah</link>
      <guid>https://dev.to/human2001/server-builds-wallet-signs-webhooks-confirm-a-non-custodial-web3-checkout-pattern-with-solana-29ah</guid>
      <description>&lt;p&gt;I've been building a Solana checkout flow. The core challenge: the server needs to control the terms of every payment — the amount, the recipient, the audit trail — without ever holding a private key.&lt;/p&gt;

&lt;p&gt;This post documents the pattern I landed on:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Checkout session with TTL and CSRF protection&lt;/li&gt;
&lt;li&gt;Atomic token invalidation to prevent TOCTOU race conditions&lt;/li&gt;
&lt;li&gt;A server-side pending record (similar to Stripe's Payment Intent) written before the wallet is ever involved&lt;/li&gt;
&lt;li&gt;Webhook authentication and idempotent confirmation&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The server constructs the unsigned transaction, the wallet signs it, and confirmation happens via webhook rather than client reporting. Solana-specific in implementation but the architecture applies to any chain.&lt;/p&gt;

&lt;p&gt;Already got a good question in the HN thread about meta-transactions and commit-reveal schemes.&lt;/p&gt;

&lt;p&gt;Full post: &lt;a href="https://blauenlabs.com/blog/web3-checkout-pattern/" rel="noopener noreferrer"&gt;https://blauenlabs.com/blog/web3-checkout-pattern/&lt;/a&gt;&lt;br&gt;
HN discussion: &lt;a href="https://news.ycombinator.com/item?id=47821168" rel="noopener noreferrer"&gt;https://news.ycombinator.com/item?id=47821168&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Happy to discuss the tradeoffs.&lt;/p&gt;

</description>
      <category>web3</category>
      <category>solana</category>
      <category>webdev</category>
      <category>security</category>
    </item>
    <item>
      <title>Web App Security: A Developer's Guide to Content Security Policy (CSP)</title>
      <dc:creator>Tom</dc:creator>
      <pubDate>Tue, 14 Apr 2026 03:56:02 +0000</pubDate>
      <link>https://dev.to/human2001/web-app-security-a-developers-guide-to-content-security-policy-csp-4mmc</link>
      <guid>https://dev.to/human2001/web-app-security-a-developers-guide-to-content-security-policy-csp-4mmc</guid>
      <description>&lt;p&gt;What a CSP is, why you need one, and how to audit yours — including a real example of a violation we caught in the wild.&lt;/p&gt;


&lt;div class="crayons-card c-embed text-styles text-styles--secondary"&gt;
    &lt;div class="c-embed__content"&gt;
      &lt;div class="c-embed__body flex items-center justify-between"&gt;
        &lt;a href="https://blauenlabs.com/blog/content-security-policy/" rel="noopener noreferrer" class="c-link fw-bold flex items-center"&gt;
          &lt;span class="mr-2"&gt;blauenlabs.com&lt;/span&gt;
          

        &lt;/a&gt;
      &lt;/div&gt;
    &lt;/div&gt;
&lt;/div&gt;


</description>
      <category>webdev</category>
      <category>security</category>
      <category>cybersecurity</category>
    </item>
  </channel>
</rss>
