<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Dr.-Ing. Fabian Schuh on Medium]]></title>
        <description><![CDATA[Stories by Dr.-Ing. Fabian Schuh on Medium]]></description>
        <link>https://medium.com/@xeroc?source=rss-7080275476dd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*lI0dxIjOreNv-DkX5OOKwA.png</url>
            <title>Stories by Dr.-Ing. Fabian Schuh on Medium</title>
            <link>https://medium.com/@xeroc?source=rss-7080275476dd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 03:33:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@xeroc/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Accepting Recurring Solana Payments in React Without Losing Your Mind]]></title>
            <link>https://medium.com/@xeroc/accepting-recurring-solana-payments-in-react-without-losing-your-mind-652583e8c91d?source=rss-7080275476dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/652583e8c91d</guid>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[payments]]></category>
            <category><![CDATA[subscription]]></category>
            <category><![CDATA[solana-network]]></category>
            <dc:creator><![CDATA[Dr.-Ing. Fabian Schuh]]></dc:creator>
            <pubDate>Tue, 21 Apr 2026 10:45:19 GMT</pubDate>
            <atom:updated>2026-04-21T10:45:19.785Z</atom:updated>
            <content:encoded><![CDATA[<p>We’ve all been there. You’re building a dApp, the UI is shaping up, and then someone says “we need subscriptions.” Suddenly you’re deep in token account delegation, PDA derivation, transaction construction, and error handling that makes your React components look like a graveyard of useEffect chains.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C3SA0yu5Uwpa3PqtGNLFtw.png" /></figure><p>It doesn’t have to be that way. We built @tributary-so/sdk-react — a collection of React hooks that wrap the Tributary payment protocol on Solana — so you can drop recurring payments into your app without hand-rolling transaction logic.</p><p>Let me walk through how it works, using our <a href="https://github.com/tributary-so/tributary/tree/main/apps/example-payments">example payments app</a> as the guide.</p><h3>The Problem We’re Solving</h3><p>Solana payments at the protocol level involve several moving parts: payment policies, delegate approvals, gateway accounts, fee distribution. If you’ve ever tried to wire up @solana/web3.js manually for a subscription flow, you know the drill — it’s dozens of lines just to build, sign, and confirm a single transaction.</p><p>We wanted to get from “I need a subscribe button” to “the subscription is live on-chain” in under 20 lines of component code.</p><h3>Two Paths: Checkout or Hooks</h3><p>Tributary gives you two integration paths:</p><ol><li><strong>Checkout Sessions</strong> — Redirect to a hosted payment page. Zero wallet connection needed in your app. Ideal when you just want to collect money.</li><li><strong>Direct Hooks</strong> — Full control. Build your own UI, manage the wallet connection yourself. For when checkout pages aren’t enough.</li></ol><p>Both approaches live in the same @tributary-so/sdk-react package. Let’s start with the simpler one.</p><h3>The Checkout Flow (No Wallet Required)</h3><p>This is the fastest path from zero to payments. You don’t even need @solana/wallet-adapter in your app — the checkout page handles wallet connection for you.</p><p>Here’s the entire payment initiation from our example app:</p><pre>import { useCheckoutSession } from &quot;@tributary-so/sdk-react&quot;;<br>export default function Home() {<br>  const { initiate } = useCheckoutSession(CHECKOUT_BASE_URL);<br>  const handlePaymentRequest = () =&gt; {<br>    initiate({<br>      mode: &quot;subscription&quot;,<br>      tokenMint: USDC_MINT,<br>      recipient,<br>      gateway: GATEWAY,<br>      amount: parseFloat(amount),<br>      trackingId,<br>      paymentFrequency: &quot;monthly&quot;,<br>      autoRenew: true,<br>    });<br>  };<br>  return &lt;button onClick={handlePaymentRequest}&gt;Proceed to Payment&lt;/button&gt;;<br>}</pre><p>That’s it. useCheckoutSession takes your checkout base URL and returns two functions:</p><ul><li><strong>generateUrl(opts)</strong> — Returns a checkout URL string. Use this for sharing payment links or rendering QR codes.</li><li><strong>initiate(opts)</strong> — Redirects the browser straight to the checkout page.</li></ul><p>Under the hood, useCheckoutSession creates a CheckoutSessionManager, encodes your payment parameters (amount, token, recipient, frequency), and builds the full URL with callback routes. The successUrl and cancelUrl are automatically derived from your current origin, so the user lands back on your site after paying.</p><p>One-time payments? Just set mode: &quot;payment&quot; and drop the frequency options.</p><pre>initiate({<br>  mode: &quot;payment&quot;,<br>  tokenMint: USDC_MINT,<br>  recipient,<br>  amount: 9.99,<br>  memo: &quot;One-time purchase&quot;,<br>});</pre><h3>Verifying the Payment on Return</h3><p>After a successful checkout, the user gets redirected back with a JWT token in the URL query string. The useTributaryToken hook handles verification:</p><pre>import { useTributaryToken } from &quot;@tributary-so/sdk-react&quot;;<br>export default function Success() {<br>  const { token, payload, loading } = useTributaryToken();<br>  if (loading) return &lt;p&gt;Verifying token...&lt;/p&gt;;<br>  if (!token || !payload) {<br>    return &lt;p&gt;No valid payment token found.&lt;/p&gt;;<br>  }<br>  return (<br>    &lt;div&gt;<br>      &lt;h1&gt;Payment Successful&lt;/h1&gt;<br>      &lt;p&gt;Status: {payload.status}&lt;/p&gt;<br>      &lt;p&gt;Tracking ID: {payload.trackingId}&lt;/p&gt;<br>    &lt;/div&gt;<br>  );<br></pre><p>The hook reads ?token= from the URL by default, sends it to the Tributary verifier API, and decodes the JWT payload. You get loading, error, and the decoded payload — standard React hook pattern, no surprises.</p><p>You can also pass a token explicitly if you’re getting it from somewhere other than the URL:</p><pre>const { payload } = useTributaryToken(myJwtToken);</pre><h3>The Full Example App</h3><p>Our <a href="https://github.com/tributary-so/tributary/tree/main/apps/example-payments">example-payments</a> app is a Vite + React project that demonstrates the complete checkout flow:</p><ul><li><strong>Home page</strong> — Collects recipient address, amount, and payment mode (one-time vs. monthly). Uses useCheckoutSession to redirect to the checkout page.</li><li><strong>Success page</strong> — Reads the JWT from the URL and verifies it with useTributaryToken.</li><li><strong>Cancel page</strong> — Simple “payment cancelled” state.</li></ul><h3>Getting Started</h3><pre>npm install @tributary-so/sdk-react @tributary-so/payments</pre><p>For direct hooks, you’ll also need the wallet adapter:</p><pre>npm install @solana/wallet-adapter-react @solana/wallet-adapter-react-ui</pre><p>Wrap your app with ConnectionProvider and WalletProvider, and the hooks pick up wallet + connection from context automatically.</p><p>We built Tributary because accepting recurring payments on Solana shouldn’t require a deep dive into CPI calls and PDA derivation. The hooks handle the protocol complexity — you focus on the product.</p><p>The example app runs on devnet out of the box. Clone it, pnpm install, pnpm dev, and you’re accepting payments in minutes.</p><p><a href="https://github.com/tributary-so/tributary/tree/main/apps/example-payments"><strong>Try the example app on GitHub</strong></a> | <a href="https://docs.tributary.so/"><strong>Read the full docs</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=652583e8c91d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Tributary Is Raising on Futarchy]]></title>
            <link>https://medium.com/@xeroc/why-tributary-is-raising-on-futarchy-5cf228b3c9e9?source=rss-7080275476dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/5cf228b3c9e9</guid>
            <category><![CDATA[payments]]></category>
            <category><![CDATA[solana-network]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[subscription]]></category>
            <dc:creator><![CDATA[Dr.-Ing. Fabian Schuh]]></dc:creator>
            <pubDate>Thu, 16 Apr 2026 08:39:59 GMT</pubDate>
            <atom:updated>2026-04-16T08:49:24.862Z</atom:updated>
            <content:encoded><![CDATA[<p>Recurring Payments on Solana Are Still Missing. We Built Them. Now We’re Raising Through a Market That Holds Us Accountable.</p><p>Most on-chain payments are optimized for the first transaction. The second one — and the 200th — is where products either become reliable infrastructure or quietly break.</p><p>Crypto is pretty good at one-off transfers. It is still weirdly bad at recurring payments.</p><p>Subscriptions. Repayments. Usage-based billing. Scheduled payouts. Milestone-based compensation. Agent-controlled spending. These aren’t edge cases. They’re the flows that define whether a product becomes an operation or stays an experiment.</p><p>That gap is why we built <strong>Tributary</strong> — recurring payment infrastructure for Solana.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8BF6HdxHBcQJUXO3jIgKSw.png" /></figure><h3>What Tributary Is</h3><p>Tributary is a live protocol on Solana mainnet that handles recurring payment logic: <strong>subscriptions</strong>, <strong>milestone payments</strong>, <em>pay-as-you-go billing</em>*, and (soon) <strong>controlled top-ups</strong>. Developers integrate a reusable payment layer instead of building custom rails from scratch every time.</p><p>The approach is non-custodial. Users authorize payment policies with explicit constraints:</p><ul><li>who gets paid</li><li>how much,</li><li>when, and</li><li>when it stops.</li></ul><p>Payments execute according to those rules. Users can pause, resume, or cancel anytime.</p><p>The protocol charges a 1% protocol fee on payment volume. That fee flows into a treasury soon to be owned by token holders. The value mechanism is straightforward: more payment volume, more fees, more treasury value.</p><h3>What’s Already Live</h3><p>Tributary has been live on Solana mainnet since October 2025. This isn’t a whitepaper or a roadmap promise.</p><ul><li><strong>The app</strong> is live at <a href="http://app.tributary.so/">app.tributary.so</a></li><li><strong>The docs</strong> are live at <a href="http://docs.tributary.so/">docs.tributary.so</a></li><li><strong>The SDK</strong> (@tributary-so/sdk) is on npm</li><li><strong>The checkout flow</strong> is live at <a href="http://checkout.tributary.so/">checkout.tributary.so</a></li></ul><p><strong>Yumi Finance</strong> is already using Tributary in production for cash loans with automatic repayments. That’s a serious use case. Repayments aren’t a marketing moment, they’re a reliability test. They’re the part of a product that has to work even when nobody is watching.</p><p>Additional proof points include <strong>Allowly</strong> (recurring subscription flows) and <a href="http://contribute.so/"><strong>Contribute.so</strong></a> (recurring crypto donations for GitHub developers). Each demonstrates a different surface area of the same underlying problem: money that needs to move repeatedly, predictably, and with clean UX.</p><h3>Why the Category Matters More Than People Think</h3><p>When most people hear “recurring payments,” they think “subscriptions.” That’s part of it, but the category is broader:</p><ul><li><strong>SaaS billing</strong> — monthly software licenses, API access</li><li><strong>Lending</strong> — automated repayments on fixed schedules</li><li><strong>Commerce</strong> — repeat merchant flows, checkout integrations</li><li><strong>Creator economy</strong> — memberships, recurring support, patronage</li><li><strong>Professional services</strong> — retainers, milestone-based project payments</li><li><strong>AI and agents</strong> — usage-based billing, controlled top-ups, spending limits</li></ul><p>The common thread: money that needs to move repeatedly, according to rules, without rebuilding the whole system every time.</p><p>If Solana is going to support real software businesses, real commerce, and real on-chain organizations, recurring payments can’t remain a bespoke workaround that every team reinvents alone.</p><h3>Why Raise on Futarchy</h3><p>We’re raising via <strong>MetaDAO’s </strong><a href="http://futard.io/"><strong>Futard.io</strong></a>! The choice is intentional, not just convenient.</p><p>In a traditional raise, valuation is negotiated in a small room. Narrative does a lot of work. Everyone’s incentives are to sound confident, simplify risk, and move fast.</p><p>Futarchy flips the posture:</p><ul><li>It’s harder to hide behind a deck</li><li>It’s next to impossible to outsource diligence to “smart money”</li><li>It rewards clarity, not charisma</li><li>It makes it obvious whether the market thinks the product is real enough to underwrite today</li></ul><p>For payments infrastructure specifically, this alignment matters. Payments isn’t a meme category. It’s the part of the stack where people care about reliability, edge cases, and whether integrations will keep working next month.</p><p>The MetaDAO community has seen what happens with hype-first raises: Ranger raised $8M on trading infrastructure promises and was liquidated by governance vote.</p><p>The community has also seen what succeeds: Omnipair raised $1.1M with working code and is up 100% from ICO. Umbra raised $3M with a working privacy protocol and is up 39% from ICO.</p><p>The pattern is consistent. Real product, specific use case, conservative target. That’s the pattern Tributary fits.</p><p><strong>The question the market needs to answer isn’t “will this product work?” It already works. The question is “will it grow?”</strong></p><p>Futarchy lets participants answer that question with real capital and real consequences. If the market says yes, the raise proceeds fund growth. If it says no, everyone gets their capital back. That’s not a hedge, but a feature.</p><p>The primary aspects for why we chose futard.io — in order of priority for us — are:</p><ul><li>futard.io let’s you raise from a wide audience without backdoor deals</li><li>futard.io let’s you hand over the contract to the DAO</li><li>futard.io get’s you attention about the product you build</li></ul><h3>What the Raise Funds</h3><p>The product is built. This isn’t about proving Tributary can exist. It already does.</p><p>The capital funds the next stage:</p><ul><li><strong>Audit</strong>: security and trust matter for infrastructure people build on</li><li><strong>Runway</strong>: roughly six months to execute without distraction</li><li><strong>Integrations</strong>: more live products running on Tributary</li><li><strong>Growth</strong>: developer onboarding, ecosystem awareness, clearer use-case packaging</li></ul><p>The risk investors are underwriting isn’t execution risk. It’s growth risk. That’s a fundamentally different bet, arguably a smaller one.</p><h3>Who’s Building This</h3><p><strong>Dr.-Ing. Fabian Schuh</strong> — 10+ years in web3, work across multiple top-10 L1 ecosystems, full-time on Solana for two years, Superteam Germany member, PhD in engineering.</p><p>Fabian hass built on BitShares, Steemit, Hive and in the last 2 years has worked on multiple projects (most of them stealth) on Solana. He also built web2 products that integrated with payment providers such as Adyen and Stripe, for instance <a href="http://relay.md/">relay.md</a>.</p><p>This giving him direct experience with the kind of product and crypto payment problems Tributary solves. He also built repo.trade, which clarified the need for simpler recurring support flows (repo.trade bebame <a href="http://contribute.so/">contribute.so</a>).</p><p>This isn’t a team chasing a narrative. It’s a protocol founder with real shipping history building infrastructure for an important category.</p><h4>🚨 AMA 🚨</h4><p>The founder will attend <a href="https://x.com/ownershipfm">ownershipfm radio</a> on Sunday 19th April 2026 to answer all your questions!</p><h3>The Honest Framing</h3><p>Tributary is early in adoption. PMF is not proven. We haven’t done a serious growth push yet.</p><p>But early is different from imaginary. The product is live, the SDK exists, the docs exist, multiple payment models exist, and there’s already live usage.</p><p>The honest framing is: important category, live product, real integrations, clear room to scale, raising through a mechanism that holds us accountable from day one.</p><p>If that’s the kind of bet you want to evaluate, start here:</p><ul><li><strong>App:</strong> <a href="https://app.tributary.so/">https://app.tributary.so</a></li><li><strong>Docs:</strong> <a href="https://docs.tributary.so/">https://docs.tributary.so</a></li><li><strong>SDK:</strong> npm install @tributary-so/sdk</li><li><strong>Checkout:</strong> <a href="https://checkout.tributary.so/">https://checkout.tributary.so</a></li><li><strong>Telegram:</strong> <a href="https://t.me/tributaryso">https://t.me/tributaryso</a></li></ul><p>Read the docs. Touch the app. Look at the integrations. Ask hard questions.</p><p>That’s the standard we’re building to.</p><p>Tributary: recurring payment infrastructure on Solana. Think Stripe billing, but on-chain, with any token. Live since October 2025. Raising to scale, not to build an MVP.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5cf228b3c9e9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Proving Payments Without a Backend: How Tributary Uses JWT]]></title>
            <link>https://medium.com/@xeroc/proving-payments-without-a-backend-how-tributary-uses-jwt-d3605b23add9?source=rss-7080275476dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/d3605b23add9</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[solana-network]]></category>
            <category><![CDATA[payments]]></category>
            <category><![CDATA[web3]]></category>
            <dc:creator><![CDATA[Dr.-Ing. Fabian Schuh]]></dc:creator>
            <pubDate>Tue, 31 Mar 2026 14:07:05 GMT</pubDate>
            <atom:updated>2026-03-31T14:07:05.235Z</atom:updated>
            <content:encoded><![CDATA[<p>Businesses accepting crypto subscriptions face a fundamental question: <strong>How do I verify a user has paid without running my own backend?</strong></p><p>Traditional Web2 solutions like Stripe provide webhooks and server-side session management. In Web3, the standard approach forces every business to run an RPC node or indexer, poll the blockchain, and maintain their own payment state. That’s infrastructure tax for something that should be simple.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cmSF0FcIbQwxet5LRXqo8w.png" /></figure><h3>The Tributary Answer: Signed JWTs from On-Chain State</h3><p>Tributary issues cryptographically signed JWTs that carry verifiable payment proofs — no backend required on the merchant side.</p><p>Here’s how it works:</p><pre>┌─────────────────────────────────────────────────────────────────┐<br>│                                                                 │<br>│  User clicks &quot;Subscribe&quot; on checkout.tributary.so               │<br>│       │                                                         │<br>│       ▼                                                         │<br>│  Wallet signs tx → On-chain: UserPayment + PaymentPolicy +      │<br>│  Delegate approval created                                      │<br>│       │                                                         │<br>│       ▼                                                         │<br>│  Tributary API reads on-chain policies                          │<br>│  → Signs JWT (ES256) with JWKS key                              │<br>│  → Redirects to merchant: successUrl?token=&lt;jwt&gt;                │<br>│       │                                                         │<br>│       ▼                                                         │<br>│  Merchant frontend validates JWT via public JWKS endpoint       │<br>│  → No backend needed                                            │<br>│  → Subscription claims are cryptographically verified           │<br>│  → Grant access immediately                                     │<br>│                                                                 │<br>└─────────────────────────────────────────────────────────────────┘</pre><h3>What’s Inside the JWT</h3><p>Every JWT contains the user’s active subscription claims, signed by Tributary’s ES256 key:</p><pre>{<br>  &quot;sub&quot;: &quot;7xKpV2BZQ3HfeRZFMfWVBpDCmCN8eYwGmCjL7m3mVqR&quot;,<br>  &quot;iss&quot;: &quot;https://api.tributary.so&quot;,<br>  &quot;aud&quot;: &quot;tributary-checkout&quot;,<br>  &quot;subscriptions&quot;: [<br>    {<br>      &quot;recipient&quot;: &quot;BxKp...9mVq&quot;,<br>      &quot;amount&quot;: &quot;10.00&quot;,<br>      &quot;tokenMint&quot;: &quot;EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v&quot;,<br>      &quot;paymentFrequency&quot;: &quot;monthly&quot;,<br>      &quot;status&quot;: &quot;paid&quot;,<br>      &quot;totalPayments&quot;: 3,<br>      &quot;nextPaymentDue&quot;: 1746057600<br>    }<br>  ]<br>}</pre><p>The merchant validates this with three lines of code:</p><pre>import { jwtVerify, createRemoteJWKSet } from &quot;jose&quot;;<br>const { payload } = await jwtVerify(<br>  token,<br>  createRemoteJWKSet(new URL(&quot;https://api.tributary.so/.well-known/jwks.json&quot;)),<br>  { issuer: &quot;https://api.tributary.so&quot;, audience: &quot;tributary-checkout&quot; }<br>);</pre><p>No database. No RPC polling. No webhook endpoints. The JWT is the proof.</p><h3>Why This Works</h3><ol><li><strong>The JWT is stateless.</strong> Tributary’s API reads on-chain state at issuance time, signs it, and hands it off. No server-side session storage. No token database.</li><li><strong>The JWT expires intelligently.</strong> Token TTL is tied to nextPaymentDue + 10min, capped at 30 days. This means the token naturally expires when the next payment is due — forcing a refresh that re-reads the blockchain.</li><li><strong>Refresh is a fresh read.</strong> When the token expires, the merchant calls POST /v1/tokens/refresh with the expired JWT. Tributary verifies the signature (expired is fine, forged is not), re-queries on-chain state, and issues a new JWT with current data. No sessions. No stored tokens.</li><li><strong>JWKS is publicly verifiable.</strong> The /.well-known/jwks.json endpoint serves public keys that anyone can cache and use for verification. Key rotation happens every 30 days with a 24-hour grace period — in-flight tokens never break.</li><li><strong>The data is public anyway.</strong> The JWT contains only on-chain subscription data — amounts, recipients, payment status, next due dates. No secrets. No balances. No private keys. This makes bearer-token semantics acceptable: the worst case is someone reads public payment info. All the backend services, indexer, database, api of Tributary are MIT license and can be operated by anyone freely as well.</li></ol><h3>Smart Expiration Design</h3><p>The expiration isn’t arbitrary. It’s derived from the actual subscription schedule:</p><pre>exp = min(<br>  earliest nextPaymentDue + 10 minutes,<br>  now + 30 days<br>)</pre><ul><li>Monthly subscription → JWT lives ~30 days (minus 10 min from next due date)</li><li>Weekly subscription → JWT lives ~7 days</li><li>Yearly subscription → JWT capped at 30 days</li></ul><p>This forces periodic refreshes aligned with payment cycles, ensuring merchants always have reasonably fresh data without manual polling.</p><p>We allow a 10min overlap for the facilitator to catch an overdue subscription and trigger its payment on-chain.</p><h3>When You Do Need a Backend</h3><p>JWTs handle the “prove you paid” use case; granting access, checking status, displaying subscription info. Pure frontend or rather, event driven by the users visiting your site.</p><p>But some businesses need <strong>background tasks</strong> that react to payment events:</p><ul><li>Automatically revoke access when a payment fails</li><li>Send “payment overdue” emails</li><li>Trigger provisioning when a new subscription is created</li><li>Maintain audit logs of all payment state changes</li></ul><p>For these cases, the business runs their own <strong>Facilitator</strong> (Gateway).</p><h3>The Facilitator Model</h3><p>In Tributary’s architecture, Facilitators are the entities that trigger execute_payment on-chain. They’re the “crank” that makes recurring payments happen. Any business can operate their own Facilitator.</p><p>Here’s the key insight: <strong>the Facilitator already knows whether a payment succeeded or failed because it’s the one executing it.</strong></p><pre>┌──────────────────────────────────────────────────────────┐<br>│                  FACILITATOR FLOW                        │<br>│                                                          │<br>│  Facilitator&#39;s cron job fires                            │<br>│       │                                                  │<br>│       ▼                                                  │<br>│  &quot;Is this policy&#39;s nextPaymentDue passed?&quot;               │<br>│       │                                                  │<br>│       ├── Yes → execute_payment() on-chain               │<br>│       │         │                                        │<br>│       │         ├── TX confirmed → payment made ✅       │<br>│       │         │   → Update local DB: status = &quot;paid&quot;   │<br>│       │         │   → Send confirmation email            │<br>│       │         │   → Extend access for another period   │<br>│       │         │                                        │<br>│       │         └── TX failed → payment failed ❌        │<br>│       │             → Update local DB: status = &quot;failed&quot; │<br>│       │             → Send overdue notification          │<br>│       │             → Schedule retry                     │<br>│       │                                                  │<br>│       └── No → skip, check next policy                   │<br>│                                                          │<br>└──────────────────────────────────────────────────────────┘</pre><p>The Facilitator doesn’t need to poll the blockchain to check if a payment happened. It already knows — because it was the one that submitted the transaction. Success or failure is immediate, local, and deterministic.</p><p>This means:</p><ul><li><strong>No indexing lag.</strong> The Facilitator knows payment state at transaction submission time, not whenever an indexer catches up.</li><li><strong>No webhook dependency.</strong> The Facilitator is the source of truth for its own payment executions.</li><li><strong>Direct access to payment state.</strong> The Facilitator’s local database has real-time payment status because it’s the entity triggering state transitions.</li></ul><h3>Backend vs. No-Backend Decision Tree</h3><pre>Do you need to react to payment events in the background?<br>│<br>├── No → JWT-only (pure frontend)<br>│   ├── User visits your site → validate JWT → grant/deny access<br>│   ├── JWT expired? → refresh via API → new JWT → continue<br>│   └── No backend, no database, no Facilitator needed<br>│<br>└── Yes → Run a Facilitator + optional backend<br>    ├── Facilitator executes payments on schedule<br>    ├── Facilitator knows success/failure immediately<br>    ├── Backend stores local payment state for business logic<br>    ├── Can still use JWTs for frontend access checks<br>    └── Full control: email triggers, provisioning, analytics</pre><h3>The Mental Model</h3><p>Think of Tributary’s JWT like a <strong>digitally signed receipt</strong> that a customer carries with them:</p><ul><li><strong>For access control</strong> (gated content, SaaS features, premium tiers): Check the receipt at the door. JWT validation on the frontend. No backend.</li><li><strong>For operational automation</strong> (billing emails, access revocation, provisioning): Be the cashier. Run a Facilitator. You see every transaction because you’re the one processing it.</li></ul><p>Both approaches can coexist. A business might use JWTs for fast frontend access checks while running a Facilitator for background operational tasks. The JWT provides the cryptographic proof; the Facilitator provides the operational control.</p><h3>Technical Details</h3><h3>JWKS Infrastructure</h3><ul><li><strong>Algorithm</strong>: ES256 (ECDSA P-256) — smaller tokens, faster verification than RS256</li><li><strong>Key Storage</strong>: Postgres + Drizzle ORM, encrypted at rest with AES-256-GCM</li><li><strong>Rotation</strong>: Automatic every 30 days, admin override available</li><li><strong>Grace Period</strong>: 24 hours after rotation — old key still validates in-flight tokens</li><li><strong>Endpoint</strong>: GET /.well-known/jwks.json — publicly cacheable for 1 hour</li></ul><h3>Token Lifecycle</h3><p>Phase Action Auth Required Issue POST /v1/tokens/issue with wallet pubkey None (public on-chain data) Validate Verify signature against JWKS None (client-side) Refresh POST /v1/tokens/refresh with expired JWT Bearer (valid signature, expired OK) Revoke N/A — tokens expire naturally —</p><h3>Rate Limits</h3><ul><li>/v1/tokens/issue: 10 req/min per wallet</li><li>/v1/tokens/refresh: 30 req/min per wallet</li></ul><h3>Refresh Mechanics</h3><ol><li>Accept expired JWT — must have valid signature (prevents forgery)</li><li>Must be within 7-day grace window past expiration</li><li>Extract wallet pubkey from sub claim</li><li>Re-query all subscription policies from blockchain</li><li>Build fresh JWT with current on-chain state</li><li>Return new token</li></ol><p>This is <strong>stateless re-issuance</strong> — no database storage of tokens or sessions required.</p><h3>Summary</h3><p>Tributary’s JWT system gives merchants cryptographic payment proofs without infrastructure:</p><ul><li><strong>No backend needed</strong> for access control — validate JWTs on the frontend</li><li><strong>No RPC polling</strong> — JWTs carry signed on-chain state</li><li><strong>No stale data</strong> — expiration is tied to payment cycles with automatic refresh</li><li><strong>When you need a backend</strong>, run a Facilitator. You get direct payment execution feedback without polling.</li></ul><p>The JWT is the bridge between Solana’s trustless on-chain state and Web2-style application logic. Signed by Tributary, verified by anyone, expired by design.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d3605b23add9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Add an AI developer to your Github in one click]]></title>
            <link>https://medium.com/@xeroc/add-an-ai-developer-to-your-github-in-one-click-eb00472cc8ab?source=rss-7080275476dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb00472cc8ab</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[backlog]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Dr.-Ing. Fabian Schuh]]></dc:creator>
            <pubDate>Wed, 25 Mar 2026 08:07:02 GMT</pubDate>
            <atom:updated>2026-03-25T08:07:02.951Z</atom:updated>
            <content:encoded><![CDATA[<p>What if adding an AI coding agent to your team was as simple as clicking “Install”?</p><p>Most AI coding tools today are black boxes. SaaS-only. Opaque. You hand over your codebase to a third party and hope for the best.</p><p><strong>We built Polycode differently.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yJvdonqihJ8GeF3akIg5dg.jpeg" /></figure><p>Polycode is a self-hosted GitHub App that brings AI agents directly into your GitHub workflow. No chat interface. No vendor lock-in. Just GitHub, your infrastructure, and workflows you control.</p><p><strong>How it works:</strong></p><ol><li>Install the GitHub App (one click)</li><li>Create an issue with a feature request</li><li>Add the label <em>polycode:implement</em></li><li>AI agents plan, implement, and open a pull request</li></ol><p>Behind the scenes, specialized AI crews handle everything:<br> • Plan Crew decomposes issues into user stories<br> • Implement Crew writes code, story by story<br> • Verify Crew runs tests and validates builds<br> • Full visibility in GitHub Projects</p><p>Why teams choose Polycode:<br> ✅ <strong>Self-hosted</strong>: Your code stays on your infrastructure<br> ✅ <strong>Extensible</strong>: Plugin architecture, custom workflows<br> ✅ <strong>Transparent</strong>: Full audit trail, per-story commits<br><strong> ✅ Integrated</strong>: No context switching, no Slack integrations, currently on Github, other Linear, Jira, Trello soon.</p><p>The result? Teams ship faster without sacrificing control or visibility.<br><strong>Currently in closed beta.</strong></p><p>Interested teams can:<br> • Join the waitlist: <a href="https://polycod.ing/">https://polycod.ing</a><br> • Message me: <a href="http://t.me/xeroc">t.me/xeroc</a></p><p>Thoughts? What’s your biggest frustration with current AI coding tools?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb00472cc8ab" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tributary Development Update: Referral Program, Custom Fees, and x402 v2]]></title>
            <link>https://medium.com/@xeroc/tributary-development-update-referral-program-custom-fees-and-x402-v2-1cdeb7a31baa?source=rss-7080275476dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/1cdeb7a31baa</guid>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[x402]]></category>
            <category><![CDATA[payments]]></category>
            <category><![CDATA[solana-network]]></category>
            <dc:creator><![CDATA[Dr.-Ing. Fabian Schuh]]></dc:creator>
            <pubDate>Mon, 19 Jan 2026 13:24:48 GMT</pubDate>
            <atom:updated>2026-01-19T13:24:48.183Z</atom:updated>
            <content:encoded><![CDATA[<h3>One Month of Building: A Technical Retrospective</h3><p>We’ve been heads-down shipping. <strong>86 commits</strong>, <strong>21K+ lines of code added</strong>, and <strong>three major features</strong> that fundamentally expand what Tributary can do on Solana. Here’s what we built and why it matters.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*--xibd7q6U9KgFw3" /><figcaption>Photo by <a href="https://unsplash.com/@florianolv?utm_source=medium&amp;utm_medium=referral">Florian Olivo</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>The Referral Program: Multi-Level Chain Architecture</h3><p>The referral system was the biggest undertaking since launch. We implemented a three-tier referral chain with a 60/30/10 reward split across levels — where the original referrer (L3) gets the largest cut, their referrer (L2) gets half that, and the immediate referrer (L1) gets the smallest slice.</p><p>This required rethinking how we stored referral accounts. Early implementations used simple mappings, but we pivoted to Anchor’s AccountLoader pattern for proper PDA derivation and validation. The referral account seed now includes the referral code itself, allowing a single user to have multiple referral codes across different gateways—a constraint that surfaced late but was critical for flexibility.</p><p>The trickiest part wasn’t the smart contract logic — it was the chain ordering. The SDK’s getReferralChain() returns accounts in bottom-up order [L1, L2, L3], but Rust’s assignment logic reverses this for fee distribution. We documented this explicitly in specs/referral-program.md after spending a full day debugging why rewards weren’t landing where expected.</p><p>The fix: level1_referrer = L3, level2_referrer = L2, level3_referrer = L1</p><h3>Custom Protocol Fees: Gateway-Level Fee Control</h3><p>Protocol fees are now configurable per gateway, not just globally. We added a feature flag (use_custom_protocol_fee, bit 2) to the PaymentGateway struct and an admin-only instruction update_gateway_protocol_fee that lets protocol administrators set gateway-specific rates.</p><p>The security model matters here. Gateways cannot toggle their own custom fee flag — that’s reserved exclusively for protocol admin control. We added masking in update_gateway_referral_settings to prevent gateway authority from modifying bit 2. This separation of concerns ensures gateways can optimize their fee structure but can’t bypass protocol oversight.</p><pre>// Feature flag restricted to protocol admin only<br>if ctx.accounts.gateway_authority.is_signer() &amp;&amp; use_custom_protocol_fee.is_some() {<br>return err!(ErrorCode::UnauthorizedFeatureFlagModification);<br>}<br>Tests verify three scenarios: custom fee at 0 bps (no protocol fee charged), disabled custom fee (reverts to global 100 bps default), and unauthorized gateway attempts—all properly rejected.</pre><h3>x402 v2: Subscription Support and Full Test Coverage</h3><p>The x402 middleware received a complete overhaul for v2. We migrated from X-Payment headers to the new Payment header format, added subscription support, and achieved 55 passing unit tests across metering utilities and middleware components.</p><p>The metering module now tracks usage across time windows with proper reset logic, while the middleware validates payment headers before allowing request processing. Coverage reports are generated in x402/coverage/ with full lcov output for CI integration.</p><p>Documentation followed implementation: three new docs files covering overview, getting started, and API reference. We also created a dedicated x402 server implementation in x402/server.ts that handles the full payment flow.</p><h3>Milestone Payments: User Experience Improvements</h3><p>Milestone-based payments are now significantly more usable. We replaced Unix timestamp inputs with native HTML5 datetime-local pickers in the payment policy form. The form now validates chronologically — each milestone must be later than the previous one, and all must be in the future.</p><p>The scheduler was extended to handle time-based milestones, not just subscriptions. This required threading next_payment_due through the execution path and adding proper timestamp comparisons in execute_payment.rs.</p><h3>CI/CD: Semantic Versioning for Monorepo</h3><p>Perhaps unsexy but essential: we implemented independent semantic versioning across all packages. SDK, SDK-React, and other packages now version independently based on commit message scopes (feat(sdk): triggers minor bumps, fix(sdk): triggers patches).</p><p>Five GitHub workflows now handle testing, SDK publishing, and release management. The release workflow creates GitHub releases automatically based on semantic release analysis. This enables npm publishing with proper version tags for downstream consumers.</p><h3>What We Learned</h3><ol><li>Referral chain ordering is counter-intuitive — document the contract-SDK interface explicitly</li><li>Feature flags need strict ownership — gateways can’t control their own fee flags</li><li>Datetime pickers beat Unix timestamps — user experience improvements pay dividends</li><li>Independent versioning works for monorepos — commit-based automation scales</li></ol><p>The referral program is almost merged and will be live soon, with full test coverage, custom protocol fees give gateway operators flexibility, and x402 v2 provides a production-ready payment middleware.</p><p>Next up: scaling the scheduler and deeper x402 integrations.</p><p>Ship it. 🚢</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1cdeb7a31baa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Squads vs Tributary: Right Tools for Different Jobs]]></title>
            <link>https://medium.com/@xeroc/squads-vs-tributary-right-tools-for-different-jobs-29b75c173a69?source=rss-7080275476dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/29b75c173a69</guid>
            <category><![CDATA[solana-network]]></category>
            <category><![CDATA[smart-contracts]]></category>
            <category><![CDATA[comparison]]></category>
            <category><![CDATA[payments]]></category>
            <dc:creator><![CDATA[Dr.-Ing. Fabian Schuh]]></dc:creator>
            <pubDate>Tue, 06 Jan 2026 13:34:34 GMT</pubDate>
            <atom:updated>2026-01-06T13:34:34.227Z</atom:updated>
            <content:encoded><![CDATA[<p>Two excellent Solana infrastructure projects. Both secure, both production-ready, both solving real problems. They’re not competitors; they’re specialized tools for different needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gscUxkfL_ozdvIUx" /><figcaption>Photo by <a href="https://unsplash.com/@theshubhamdhage?utm_source=medium&amp;utm_medium=referral">Shubham Dhage</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Core Philosophy Difference</h3><p><strong>Squads</strong> = Collective decision-making. Multi-signature wallets where teams approve actions together. Security through consensus.</p><p><strong>Tributary</strong> = Individual automation. Token delegation where users approve once, then payments run automatically. Convenience through delegation.</p><p>Both valid. Just different priorities.</p><h3>Squads: Multisig Security for Teams</h3><p><strong>What it does:</strong> Programmable smart accounts with configurable thresholds. Need 3-of-5 team members to approve? Squads handles it.</p><p><strong>Architecture:</strong> Multi-program system, MPL for multisig, Roles for permissions, Validator for execution. Complex but comprehensive.</p><p><strong>Real-world impact:</strong> $10B+ in assets secured, $3B+ in transactions processed. Proven battle-testing.</p><h3>Key Features in v5:</h3><p>The v5 upgrade is designed to take advantage of upcoming Solana runtime changes that will increase CPI (Cross-Program Invocation) limits, allowing smart accounts to function as first-class citizens on Solana. The protocol will be formally verified and is expected to launch on Solana mainnet later this year (2024/2025).</p><p><strong>Hooks</strong> — Individual programs that programmatically adjust smart account consensus requirements. This allows users to set spending limits, create dynamic approval requirements based on transaction type, or establish program whitelists that let specific members bypass consensus for designated applications.</p><p><strong>Synchronous Transaction Execution</strong> — Enables real-time execution of transactions through multiple synchronous top-level signatures, which is particularly useful for single-user scenarios and multi-factor authentication workflows. This significantly reduces transaction overhead.</p><p><strong>Advanced Permissions System</strong> — Allows assignment of advanced privileges to specific keys within smart accounts, enabling enterprises to implement granular admin roles and operational setups.</p><p><strong>Key-Tier Adaptive Timelocks</strong> — Provides enhanced security and account recovery capabilities with context-aware features.</p><p><strong>Who uses it:</strong></p><ul><li>DAO treasuries requiring collective fund management</li><li>DeFi protocols managing protocol upgrades</li><li>Institutional custody teams handling client assets</li><li>Development teams coordinating critical operations</li></ul><p><strong>Why teams choose Squads:</strong></p><ul><li><strong>Security:</strong> Multiple audits (OtterSec, Neodyme, Bramah Systems)</li><li><strong>Control:</strong> Configurable thresholds (1-of-N to N-of-N)</li><li><strong>Flexibility:</strong> Role-based permissions, time locks, voting integration</li><li><strong>Maturity:</strong> 4+ years in production, 300+ teams deployed</li></ul><p><strong>Trade-off:</strong> Complexity. Setting up multisig requires understanding authority indices, transaction states, and account management. Initial gas costs for account creation. Learning curve for non-technical users.</p><p><strong>Use case:</strong> Your DAO needs to approve treasury disbursements. Squads.</p><h3>Tributary: Automated Payments for Individuals</h3><p><strong>What it does:</strong> Token delegation enabling automated recurring payments. Users approve once, smart contracts handle the rest. No escrow, no lockup, full custody.</p><p><strong>Architecture:</strong> 5 accounts focused on payment flow — Program Config, Payment Gateway, User Payment, Payment Policy, Automatic Execution. Streamlined.</p><p><strong>Payment types:</strong> Subscriptions, Milestone Payments, Pay-as-you-go. Three distinct models for different billing patterns.</p><p><strong>Who uses it:</strong></p><ul><li>SaaS platforms needing automated subscription billing</li><li>API services with variable consumption pricing</li><li>Content creators monetizing recurring access</li><li>AI/LLM providers billing token usage</li></ul><p><strong>Why platforms choose Tributary:</strong></p><ul><li><strong>Simplicity:</strong> One approval enables ongoing payments</li><li><strong>Flexibility:</strong> Three payment models in one protocol</li><li><strong>Non-custodial:</strong> Funds stay in user wallets, not escrow</li><li><strong>Speed:</strong> Solana’s 400ms finality, &lt;$0.01 transaction costs</li></ul><p><strong>Trade-off:</strong> Payment-specific focus. Not a general-purpose custody solution. Limited to recurring payment use cases.</p><p><strong>Use case:</strong> Your SaaS wants automated Web3 subscriptions. Tributary.</p><h3>Comparison Summary</h3><pre>| Dimension            | Squads                    | Tributary               |<br>| -------------------- | ------------------------- | ----------------------- |<br>| **Primary Purpose**  | Multisig security         | Automated payments      |<br>| **Target User**      | Teams, DAOs, Institutions | Individuals, Platforms  |<br>| **Core Mechanism**   | Threshold approvals       | Token delegation        |<br>| **Setup Complexity** | Medium-High               | Low                     |<br>| **Custody Model**    | Shared multisig wallet    | Individual wallets      |<br>| **Best For**         | Treasury management       | Subscription billing    |<br>| **Security Focus**   | Multi-signature consensus | Delegation scope limits |<br>| **Maturity**         | 4+ years, $10B secured    | New, growing ecosystem  |</pre><h3>Real-World Examples</h3><p><strong>Scenario 1: DAO Treasury Management</strong></p><p>A 10-person DAO manages $5M treasury. Requires 7-of-10 approval for disbursements.</p><p><strong>Solution:</strong> Squads. Configurable thresholds, member management, audit trail. Exactly what multisig does well.</p><p><strong>Scenario 2: SaaS Subscription Billing</strong></p><p>AI API platform wants customers to pay $49/month automatically in USDC. Customers approve once, then forget about it.</p><p><strong>Solution:</strong> Tributary. Token delegation enables automated execution. No monthly approvals, no escrow disputes.</p><h3>Complementary, Not Competitive</h3><p>Both projects excel at their specific domains:</p><ul><li><strong>Squads</strong> = Governance infrastructure. Collective decision-making for group assets.</li><li><strong>Tributary</strong> = Payment infrastructure. Automated billing for individual relationships.</li></ul><p>You might even use both together: Squads manages your protocol treasury, Tributary handles your customer subscriptions.</p><h3>Choose Based on Your Need</h3><p><strong>Need multi-signature control for teams?</strong> Squads. Excellent security, proven track record, enterprise-grade features.</p><p><strong>Need automated payments for customers?</strong> Tributary. Simple UX, flexible billing models, non-custodial design.</p><p>Both products have excellent documentation, active communities, and committed teams. Both are production-ready with comprehensive SDKs.</p><p>The right tool depends on the problem you’re solving.</p><ul><li><strong>Squads:</strong> <a href="https://github.com/squads-protocol">github.com/squads-protocol</a></li><li><strong>Tributary:</strong> <a href="https://github.com/tributary-so">github.com/tributary-so</a></li></ul><p><em>This article compares two legitimate Solana infrastructure projects. Both serve different audiences. Both are well-engineered solutions to real problems.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29b75c173a69" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Web3 Subscriptions Without the Friction: How Tributary Transforms SaaS Billing]]></title>
            <link>https://medium.com/@xeroc/web3-subscriptions-without-the-friction-how-tributary-transforms-saas-billing-82fb2f588211?source=rss-7080275476dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/82fb2f588211</guid>
            <category><![CDATA[payments]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[web3]]></category>
            <dc:creator><![CDATA[Dr.-Ing. Fabian Schuh]]></dc:creator>
            <pubDate>Tue, 06 Jan 2026 12:47:26 GMT</pubDate>
            <atom:updated>2026-01-06T12:47:26.244Z</atom:updated>
            <content:encoded><![CDATA[<p>Meet <strong>PromptFlow</strong>, a fictional AI API platform that burned 40% of engineering time fighting subscription infrastructure. Last month they switched to Tributary. Here’s what happened.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9OTj_chUYysNwQza" /><figcaption>Photo by <a href="https://unsplash.com/@dtrinksrph?utm_source=medium&amp;utm_medium=referral">David Trinks</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>The Problem</h3><p>PromptFlow offered two pricing tiers: $49/month (subscription) and pay-per-token model. The team built a custom billing system in-house. It worked, but:</p><ul><li><strong>Manual payment collection</strong> — Tokens locked in escrow, users frustrated</li><li><strong>Complex reconciliation</strong> — 3 separate payment gateways to manage</li><li><strong>No native crypto support</strong> — Customers demanded Web3 payments</li><li><strong>Dev time waste</strong> — Billing bugs pulled engineers from core product</li></ul><p>“I spent half my Friday reconciling payments,” says their CTO. “Our product velocity tanked.”</p><h3>The Tributary Solution</h3><p>Tributary’s <strong>token delegation</strong> model changed everything. Users approve payments once, and smart contracts handle the rest automatically. <strong>No escrow, no lockup, full custody.</strong></p><p>Here’s how PromptFlow integrated Tributary for subscription billing:</p><pre>import { Tributary, PaymentInterval } from &quot;@tributary-so/sdk-react&quot;;</pre><pre>const subscription = (<br>  &lt;SubscriptionButton<br>    amount={new BN(&quot;49000000&quot;)} // $49 in USDC<br>    token={USDC_MINT}<br>    recipient={promptFlowWallet}<br>    gateway={promptFlowGateway}<br>    interval={PaymentInterval.Monthly}<br>    maxRenewals={12}<br>    label=&quot;Subscribe - Pro Plan ($49/mo)&quot;<br>    onSubscribe={(policyId) =&gt; handleActivation(policyId)}<br>  /&gt;<br>);</pre><p>For their pay-as-you-go model, they used Tributary’s <strong>PayAsYouGo</strong> policy type:</p><pre>const payAsYouGo = await sdk.createPaymentPolicy({<br>  type: &quot;PayAsYouGo&quot;,<br>  maxAmountPerPeriod: new BN(&quot;100000000&quot;), // $100 max/month<br>  maxChunkAmount: new BN(&quot;1000000&quot;), // Max $1 per claim<br>  periodLengthSeconds: 2592000, // 30-day billing cycle<br>  recipient: promptFlowWallet,<br>  gateway: promptFlowGateway,<br>});</pre><h3>The Results</h3><pre>| Metric                        | Before Tributary | After Tributary |<br>| ----------------------------- | ---------------- | --------------- |<br>| Engineering time on billing   | 40%              | 5%              |<br>| Payment success rate          | 87%              | 99.2%           |<br>| Support tickets (billing)     | 156/mo           | 12/mo           |<br>| Time to implement new pricing | 3 weeks          | 1 day           |</pre><p><strong>“We shipped tiered pricing in 4 hours,”</strong> the CTO reports. <strong>“Our developers focus on AI features now.”</strong></p><h3>Why Tributary Works for SaaS</h3><ol><li><strong>Non-custodial security</strong> — Users keep control of funds</li><li><strong>Automated execution</strong> — No manual intervention needed</li><li><strong>Flexible pricing</strong> — One platform for subscriptions, milestones, pay-as-you-go</li><li><strong>Sub-cent fees</strong> — Solana’s 400ms settlement, &lt;$0.01 tx costs</li><li><strong>Web3 native</strong> — Crypto customers love it</li></ol><h3>Integration Visual</h3><pre>User clicks &quot;Subscribe&quot; → Tributary SDK creates payment policy<br>      ↓<br>User approves delegation (one-time, in wallet)<br>      ↓<br>Smart contract verifies permission scope<br>      ↓<br>Monthly payment executes automatically (permissionless)<br>      ↓<br>Funds transfer → Provider receives money + protocol fee (1%)</pre><p>No complex reconciliation. No escrow disputes. Just clean, automated recurring payments.</p><h3>Get Started</h3><p>Ready to eliminate billing infrastructure overhead?</p><pre>npm install @tributary-so/sdk<br>npm install @tributary-so/sdk-react</pre><p>Documentation: <a href="https://docs.tributary.so/">docs.tributary.so</a><br> Demo: <a href="https://actioncode.app/">contribute</a>.so<br> GitHub: <a href="https://github.com/tributary-so">github.com/tributary-so</a></p><p><strong>Your customers are waiting. Tributary handles the rest.</strong></p><p><em>This case study is hypothetical but reflects real-world integration patterns. PromptFlow represents dozens of SaaS platforms currently exploring Tributary for Web3-native subscription billing.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=82fb2f588211" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rektoff Solana Rust Security Bootcamp Review ]]></title>
            <link>https://medium.com/@xeroc/rektoff-solana-rust-security-bootcamp-review-76eb7e812e73?source=rss-7080275476dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/76eb7e812e73</guid>
            <category><![CDATA[audit]]></category>
            <category><![CDATA[review]]></category>
            <category><![CDATA[solana-network]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Dr.-Ing. Fabian Schuh]]></dc:creator>
            <pubDate>Wed, 03 Dec 2025 15:15:54 GMT</pubDate>
            <atom:updated>2025-12-03T15:15:54.988Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0tq9KXcOD-2wk3LNeXBkaQ.png" /></figure><h3>A Personal Journey Through Intense Learning 😅</h3><p>You know, as someone juggling multiple projects, a full-time Solana gig, and raising two kids, I gotta say I approached the <a href="https://x.com/rektoff_xyz">Rektoff</a> Solana Rust Security Bootcamp with a mix of excitement and skepticism. Like, how could I possibly squeeze in time for yet another thing? But man, from the very first lecture, I was totally hooked. The instructors’ passion for the material was just infectious, and the “nice vibe” of the community made every session feel like the best part of my week. Despite my crazy packed schedule, I found myself desperately wanting to keep going; not just because the content was top-notch, but because it hit me how super important it is to really get what you’re doing when writing Solana contracts. In a world where security slip-ups can cost millions, this bootcamp didn’t just teach me Rust and Solana security; it gave me this whole new mindset of being careful and thoughtful in my dev work that I use every single day now, especially on my work on <a href="https://tributary.so/">Tributary.so</a> that takes token delegation for SPL tokens to the next level.</p><h3>An Outstanding Educational Experience 🌟</h3><p>The <a href="https://x.com/rektoff_xyz">Rektoff</a> bootcamp is honestly one of the coolest, most put-together programs I’ve seen in the blockchain world. It ran for six intense weeks, and they nailed the balance between theory and practice, so by the end, you don’t just know stuff; you feel ready to audit and lock down real Solana protocols.</p><p>The curriculum flowed so smoothly, kicking off with Rust basics like memory management, ownership, borrowing, and that tricky borrow checker; then zooming into Solana stuff like the SVM, sBPF bytecode, and smart contract security. The instructors, especially Daniel Cumming and m4rio.eth, are pros from formal verification and top security research. They made even the hardest concepts feel doable with their clear explanations and enthusiasm. Seriously, e/s/bBPF is just amazing! 😊</p><p>What really blew me away was how hands-on everything was. From live bug hunting to messing around with Anchor and Pinocchio, every part built on the theory with real stuff. The office hours and Slack chats were lifesavers, turning what could’ve been lonely into this awesome group adventure. My biggest regrets are that i couldn’t manage to attend them all🤝</p><h3>The Capstone Project: Pure Fun and Challenge 🎉</h3><p>If I had to pick the absolute best part, it’s gotta be the capstone project. As someone who loves a good challenge, this was a total blast! Getting to use everything we’d learned; from Rust’s memory safety tricks to deep Solana security patterns; in a real audit was so rewarding. The capstone wasn’t just about spotting bugs; it was about channeling your inner security researcher, figuring out the ins and outs of CPI calls, account checks, and sneaky attack paths. The crazy amount of fun I had came from that rush of solving puzzles and the excitement of finding stuff. It was tough, sure, but submitting my work felt amazing. 🏆</p><h3>Final Thoughts 💭</h3><p>The Rektoff Solana Rust Security Bootcamp is way more than just a class; it’s a solid investment in making blockchain dev safer. In a fast-moving spot like Solana, stuff like this is key to upping the security game. I left with better tech skills, a bunch of cool people to connect with, and this fresh fire for building secure systems.</p><p>If you’re thinking about joining, go for it! Just know you’ll be pushed, inspired, and changed as a dev. Rektoff nailed it; they don’t just show you how to code safely, but how to think securely.</p><p>Five stars, easy. ⭐⭐⭐⭐⭐</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=76eb7e812e73" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Things About Recurring Subscription Payments on Solana That Will Surprise You]]></title>
            <link>https://medium.com/@xeroc/3-things-about-recurring-subscription-payments-on-solana-that-will-surprise-you-59c4ad7ed4f3?source=rss-7080275476dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/59c4ad7ed4f3</guid>
            <dc:creator><![CDATA[Dr.-Ing. Fabian Schuh]]></dc:creator>
            <pubDate>Sat, 29 Nov 2025 22:02:10 GMT</pubDate>
            <atom:updated>2025-11-29T22:02:10.496Z</atom:updated>
            <content:encoded><![CDATA[<p>We live in a subscription economy. From streaming services and software-as-a-service (SaaS) platforms to creator content, the convenience of “set it and forget it” recurring payments is the backbone of the modern digital world. It’s a seamless experience we’ve all come to expect, powered by systems that automatically handle payments in the background.</p><p>In Web3, however, this experience has been frustratingly out of reach. The standard has been a clunky, repetitive process of connecting a wallet and approving every single transaction, every single time. This constant friction isn’t just annoying for users; it’s a fundamental roadblock for businesses trying to build sustainable, on-chain revenue models. But <a href="https://tributary.so/"><strong>Tributary</strong></a>, a new protocol born out of the <a href="https://colosseum.com/">Cypherpunk Hackathon</a>, is set to fundamentally change this dynamic, finally delivering a Web2 experience with the security and control that only Web3 can offer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zftRar8HGHw6FvrwrM596A.png" /></figure><h3>1. Automation Doesn’t Have to Mean Custody</h3><p>The biggest mental hurdle for automated payments in crypto has always been the fear of losing control. The idea of giving a protocol ongoing access to your funds often implies locking them in a smart contract or, worse, handing over custody. This is where Tributary’s first major innovation lies: a truly non-custodial approach where your funds always remain in your own wallet.</p><p>Instead of transferring assets to a third party, Tributary’s model works through token delegation. Users grant the protocol <em>limited and revocable</em> authority to pull a specific amount for a specific purpose, according to a pre-approved schedule. You aren’t giving away control of your wallet; you’re just providing a narrow, explicit permission slip for a single subscription payment that you can cancel at any time. This is a massive leap for user security and trust, providing on-chain transparency for every transaction. This model is a significant security upgrade over both locking funds in a rigid smart contract and the risky practice of storing ‘hot’ private keys on a server for payment execution.</p><h3>2. The Annoying “Approve” Pop-up is a Solved Problem</h3><p>The most visible pain point of Web3 payments is the user experience (UX). The need to manually sign every recurring transaction is a significant barrier preventing decentralized applications from feeling as smooth and intuitive as their centralized counterparts. Tributary’s solution directly solves this with a “sign once” flow.</p><p>This has always been the central tension for on-chain services: the trade-off between the security of user-signed transactions and the convenience of automation. Tributary resolves this by creating a secure, on-chain policy that a user signs just once. A user connects their wallet and signs a transaction that creates a <strong>Payment Policy</strong> on-chain. This policy is a set of rules — defining the amount, token, frequency, and recipient — that governs the subscription. From that point on, the protocol handles all subsequent payments automatically. This model is best captured by the simple yet powerful concept it enables:</p><p>“Sign Once, Pay Forever”</p><p>This UX improvement is transformative. It removes the most significant point of friction for recurring on-chain payments, making Web3 services as seamless to use as their Web2 counterparts. Critically, this convenience doesn’t come at the cost of control. Users retain the ability to pause, resume, or cancel their subscription at any time, directly from their wallet.</p><h3>3. Web2 Business Models Can Now Go Fully On-Chain</h3><p>While the user benefits are clear, the implications for businesses and developers are even more profound. The lack of a practical, automated payments primitive has made it nearly impossible to implement proven Web2 business models on-chain. Tributary’s technology changes that, acting as an economic enabler for the entire ecosystem.</p><p>With automated recurring payments, entire categories of businesses are now not just possible, but practical on Solana. This includes key sectors like <strong>SaaS, Creators, and Gaming</strong>, which can finally build the sustainable, <strong>predictable revenue streams</strong> that are the bedrock of Web2’s success, but have been notoriously difficult to implement on-chain. By leveraging Solana’s infrastructure, businesses benefit from sub-cent transaction fees and near-instant settlement (around 400ms), creating a highly efficient financial backend. Moreover, the protocol supports a wide range of SPL tokens, allowing businesses to accept subscriptions in stablecoins like USDC or their own native project tokens. Furthermore, a developer-first approach with available SDKs and React components makes integrating this functionality straightforward, lowering the barrier for builders to innovate.</p><h3>Conclusion: What Will We Build Next?</h3><p>The arrival of a non-custodial, automated subscription protocol on Solana marks a pivotal moment. It solves three core challenges at once: giving users complete control over automated payments, delivering a seamless “sign once” user experience, and unlocking the proven business models that have been missing from the Web3 economy. This isn’t just an incremental improvement; it’s foundational infrastructure.</p><p>Now that the friction of recurring payments is gone, what new kinds of decentralized businesses and creator platforms will be built on this foundation?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59c4ad7ed4f3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding Token Delegation: The Magic Behind Tributary’s Automatic Payments]]></title>
            <link>https://medium.com/@xeroc/understanding-token-delegation-the-magic-behind-tributarys-automatic-payments-aaac32a0e4af?source=rss-7080275476dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/aaac32a0e4af</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[subscription]]></category>
            <category><![CDATA[solana-network]]></category>
            <dc:creator><![CDATA[Dr.-Ing. Fabian Schuh]]></dc:creator>
            <pubDate>Sat, 29 Nov 2025 14:20:55 GMT</pubDate>
            <atom:updated>2025-11-29T14:20:55.784Z</atom:updated>
            <content:encoded><![CDATA[<p>Recurring payments are a core part of our digital lives, but the experience is often frustrating. Traditional online subscriptions can feel like a black box, where you hand over your payment details and hope for the best, with little day-to-day control. Meanwhile, many Web3 payments go to the other extreme, forcing you to manually approve every single transaction, which quickly becomes tedious. Built specifically for the Solana ecosystem, Tributary introduces a powerful and user-friendly solution called Token Delegation that finally offers the best of both worlds: automated convenience combined with true user control.</p><h3>1. The Two Familiar Problems with Recurring Payments</h3><p>To understand Tributary’s solution, it’s helpful to first look at the two common challenges it solves. Both the traditional Web2 model and the standard Web3 approach present significant drawbacks for users.</p><p><strong>How it Works</strong></p><ul><li><strong>Traditional Web2 Subscriptions</strong>: You give a company your credit card details for ongoing charges.</li><li><strong>Standard Web3 Payments:</strong> You must manually approve every single transaction from your crypto wallet.</li></ul><p><strong>The Main Problem for You</strong></p><ul><li><strong>Traditional Web2 Subscriptions</strong>: <strong>Opaque custody</strong> means your funds are handled by others, with limited control and often high fees.</li><li><strong>Standard Web3 Payments:</strong> It’s repetitive and creates a clunky user experience (“approve every time”).</li></ul><p>Tributary’s approach is designed to provide the <strong>convenience of the Web2 </strong>model while upholding the <strong>security and self-custody</strong> principles of Web3.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YM4Nkdm8p60-BzNcv2nHew.png" /></figure><h3>2. Introducing the Solution: Token Delegation</h3><p>At its core, Token Delegation is a simple but powerful concept that can be summed up as: <strong>“Sign Once, Pay Forever.”</strong> It allows you to grant a protocol limited and specific permission to move funds on your behalf according to a set of rules you define, without ever giving up custody of your assets.</p><p>Think of it like giving a house sitter a key to your mailbox, but not the master key to your entire house. You are granting very specific, limited permission for one task, and you can take that key back whenever you want.</p><h3>The Three Rules of Tributary’s Token Delegation</h3><p>This system is built on a foundation of safety and user control, guided by three unbreakable rules:</p><ul><li><strong>Limited Authority:</strong> You aren’t giving the protocol a blank check. You authorize a specific amount for a specific duration, and the protocol can <em>never</em> exceed those limits.</li><li><strong>Always Non-Custodial:</strong> Your funds <strong>always</strong> remain in your own wallet until a payment is due. Unlike other methods that require you to lock up assets in a contract, Tributary ensures you never lose custody. This adheres to a core principle of Web3: “not your keys, not your crypto.”</li><li><strong>Completely Revocable:</strong> You are always in charge. You maintain the power to pause, resume, or completely cancel this permission at any time, instantly, with no questions asked.</li></ul><p>Now that we understand <em>what</em> token delegation is, let’s look at how Tributary puts it into practice.</p><h3>3. How Tributary Puts it into Action: A Simple 4-Step Flow</h3><p>The user experience with Tributary is designed to be incredibly straightforward. It transforms the clunky, repetitive process of Web3 payments into a smooth, one-time setup.</p><ol><li><strong>You Sign Once</strong> You connect your wallet and approve the delegation one single time. This single signature is all that’s needed to establish the rules for your automated subscription.</li><li><strong>A “Payment Policy” is Created</strong> This signature creates a “Payment Policy” within the Tributary protocol. Think of this as the digital contract that contains the rules you agreed to, such as the payment amount, the frequency (e.g., monthly), and whether it should <strong>auto-renew</strong>.</li><li><strong>Payments are Automated</strong> With the policy in place, the Tributary protocol now has the limited permission it needs to pull the specific funds from your wallet when they are due. It happens automatically in the background, without requiring any more approvals from you.</li><li><strong>You Remain in Full Control</strong> At any point, you can visit the application’s dashboard to manage your subscription. You have the power to instantly pause or cancel the payment policy, stopping all future automated payments.</li></ol><p>This simple flow demonstrates how the system works, but its true power lies in the benefits it delivers directly to you.</p><h3>4. Why This is a Game-Changer for You</h3><p>Tributary’s use of token delegation isn’t just a technical improvement; it fundamentally changes the user experience for recurring payments in Web3 for the better.</p><ul><li><strong>Total Control &amp; Security</strong> You have peace of mind because your funds never leave your wallet until a payment is due, and you can cancel anytime.</li><li><strong>Complete Transparency</strong> Every payment is recorded on the <strong>Solana blockchain</strong>, so you have a clear, unchangeable history of every transaction.</li><li><strong>A Seamless Experience</strong> You get the convenience of a Web2 subscription without having to approve every single payment.</li></ul><p>By elegantly solving the core issues of both traditional and early Web3 payment models on the Solana network, Tributary delivers a superior experience that combines the ease of Web2 with the transparency and control of Web3. Furthermore, Tributary works not just with SOL, but with a wide variety of tokens on the Solana network (SPL tokens), giving you flexibility in how you pay.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aaac32a0e4af" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>