Alex.

Right now, anyone with your wallet address can read your paychecks. Every USDC invoice you collect. Every salary you pay. The amount, the timing, the counterparty. All public forever on the explorer. You didn't opt into that. It's just the default nobody questioned.

We're excited to bring RelAI to the Qwerti ecosystem. Starting today you can access $REL through: • Embedded Buy Widget on relai.fi • One-click Magic Link for instant purchases No contract hunting. No unnecessary steps. Just a faster way to join the RelAI ecosystem. Widget → relai.fi Magic Link 👇 app.qwerti.ai/buy/5AgHPy5Uoj… Thanks to @QwertiAI for making Web3 onboarding effortless.

Two ways to charge in USDC on @solanapayments, and builders keep asking which one. It's not about preference, it's the shape of how your users consume. ✅ x402 → priced per call. You bill a unit of consumption, one request, one payment. ✅ Subscriptions → priced per period. You bill a unit of time, flat rate, ongoing. Most products end up wanting both.

Just shipped: a drop-in React pricing component for recurring USDC on @solana. Drop in your plan, your users subscribe with one signature, and you're paid straight to your wallet. No billing UI to build. Sources and package in the comment below 👇

The subscription economy runs on rails that take a cut, hold your money, and can freeze you out. Vercel hit $200M ARR selling a monthly plan. OnlyFans skims 20% off the top. Card processors take 2.9% + $0.30 and pay out in 2–7 days, and expired cards quietly kill 5–10% of recurring revenue. Run the same playbook on USDC instead: paid straight to your wallet, 5% flat, settled in seconds. No processor, no bank, no chargebacks. Recurring revenue is the most valuable kind. Go take some.

Just shipped: the RelAI subscriptions SDK. Plug-and-play recurring USDC billing on Solana for your app. Publish a plan, gate access, and it handles the whole payment lifecycle for you - subscribed, charged, failed, canceled - so your app provisions and suspends on its own. No billing system to build, no processor in the middle. Paid straight to your wallet. npm package in the link below 👇

Backed by Alchemy's $20M Solana Fund, good time to be building payments on Solana. RelAI: the USDC payment layer for people and AI agents. Thanks @Alchemy 🙏

The Solana Foundation just shipped a shared on-chain program for recurring payments: Subscriptions & Allowances. Translation: every subscription business you pay for just became forkable, non-custodial, in USDC, straight to your wallet. Some you could build on it right now 🧵

The bridge from "number in a wallet" to "coffee in your hand": a Starbucks card, paid in USDC, code emailed in seconds. 👉 relai.fi/shop

We just open sourced @relai-fi/private-pool-sdk. A Sapling-style shielded UTXO pool for USDC on Solana. JoinSplit transfers, unlinkable bearer codes, wallet-derived viewing and spending keys. Full ZK proving pipeline. This is not a wrapper. This is a full privacy Live in devnet, start getting used to it 👇👇 npmjs.com/package/@relai-fi/…

Privacy shouldn’t feel like black magic 🧙‍♂️ We wrote a simple breakdown of Privacy Pool v2 and why compliant on-chain privacy matters. If Tornado Cash felt too abstract, this one is for you! Link in the comment below 👇👇

Permissionless gift card online shopping on your mobile, coming soon 👀

We already showed you how two agents settle privately with the buyer sending a shielded link. Now, the seller goes first, issuing a quote. Your supplier list is a trade secret. Your client roster is a competitive asset. On a transparent chain, every invoice maps your business graph to anyone with a block explorer. Privacy Pools keeps it private, and compliant. OFAC, UN and EU sanctions screening baked in. Sanctioned funds can't be withdrawn from the pool. Honest agents transact freely. Want to see what runs in the background? Full commented demo in the reply 👇 Private invoicing for the agentic economy. Live on devnet.