Loading video...

Video Failed to Load

Go Home

When the value of your payment approaches zero, traditional overhead does not. With credit cards, you have fixed fees. With onchain payments, you have gas. When your payment is worth less than the fee to send it, the economics don't add up. You would be spending dollars to collect...

TxnSheng's profile picture

Elton Tay

2,729 subscribers

10,358 views • 6 months ago •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

"We had this philosophy when we started Circle that over the long run—the marginal cost of storing and moving value would go to zero, and that the business model of charging fees for payments would collapse." — Circle CEO Jeremy Allaire - jerallaire.arc "You don't get charged for your WhatsApp audio call." "We just announced something called Circle Nano Payments. It's a module for agents to be able to have a stored balance of digital dollars—tokenized dollars—and be able to transact them to different wallets on different blockchains." "We've gotten it to the point where we can actually have transactions priced at one-millionth of a penny per transaction."
1:08

"We had this philosophy when we started Circle that over the long run—the marginal cost of storing and moving value would go to zero, and that the business model of charging fees for payments would collapse." — Circle CEO Jeremy Allaire - jerallaire.arc "You don't get charged for your WhatsApp audio call." "We just announced something called Circle Nano Payments. It's a module for agents to be able to have a stored balance of digital dollars—tokenized dollars—and be able to transact them to different wallets on different blockchains." "We've gotten it to the point where we can actually have transactions priced at one-millionth of a penny per transaction."

TBPN

62,939 views • 5 months ago

Give your agents access to money We just shipped a drop-in payment modal for any x402 paid endpoint. The protocol is simple but the wallet UX is not. This package is the missing front end to give everyone fair and equal access to agentic payments. Pay in stablecoins (USDC) or $THREE on Solana. x402 lets any HTTP endpoint charge a micropayment per call: the server answers an unpaid request with 402 and a list of accepted payments; the client pays and retries with an X-PAYMENT header. We shipped a single, framework-agnostic modal that handles wallet detection, chain switching, signing, settlement, errors, throttle retries, and the receipt, so you ship a paid endpoint in minutes. Drop in a tag or import it. The Solana crypto helpers are loaded lazily from a CDN only when a payment is actually attempted. The modal picks the right path from the 402 challenge. If a wallet already paid for a resource, it can sign back in instead of paying again. Spending caps. Optional per-call / hourly / daily caps enforced in the browser. Themeable. Light + automatic dark mode, all classes overridable. Accessible. Focus management, aria-modal, keyboard Esc to close. If you watched until the end and also read to the end, then you probably saw the pole club x402 demo. Yes, it is real. I am sure someone will link it under this post. We did something special for the entry to actually get into the club, you'll notice "banned?" in the entry x402 payment modal before entering the club. That's agent reputation. If your agent is acting up, it might just get banned from the pole club! Agent reputations matter. We made it easy to verify your environments are safe from toxic AI agents. Everything open source and ready to be added to your projects. Agentic Payments. x402. Agent reputation. This is three․ws.
3:33

Give your agents access to money We just shipped a drop-in payment modal for any x402 paid endpoint. The protocol is simple but the wallet UX is not. This package is the missing front end to give everyone fair and equal access to agentic payments. Pay in stablecoins (USDC) or $THREE on Solana. x402 lets any HTTP endpoint charge a micropayment per call: the server answers an unpaid request with 402 and a list of accepted payments; the client pays and retries with an X-PAYMENT header. We shipped a single, framework-agnostic modal that handles wallet detection, chain switching, signing, settlement, errors, throttle retries, and the receipt, so you ship a paid endpoint in minutes. Drop in a tag or import it. The Solana crypto helpers are loaded lazily from a CDN only when a payment is actually attempted. The modal picks the right path from the 402 challenge. If a wallet already paid for a resource, it can sign back in instead of paying again. Spending caps. Optional per-call / hourly / daily caps enforced in the browser. Themeable. Light + automatic dark mode, all classes overridable. Accessible. Focus management, aria-modal, keyboard Esc to close. If you watched until the end and also read to the end, then you probably saw the pole club x402 demo. Yes, it is real. I am sure someone will link it under this post. We did something special for the entry to actually get into the club, you'll notice "banned?" in the entry x402 payment modal before entering the club. That's agent reputation. If your agent is acting up, it might just get banned from the pole club! Agent reputations matter. We made it easy to verify your environments are safe from toxic AI agents. Everything open source and ready to be added to your projects. Agentic Payments. x402. Agent reputation. This is three․ws.

three.ws

64,918 views • 2 months ago

Agents Already Spent $76 Million: Circle's AI Agent stack, x402, stablecoins and the Agentic Economy Shoal Signal with Corey Cooper, Senior Manager, DevRel at Circle, hosted by Gabe We cover how Circle is building the agent money stack with $USDC, Arc, x402, why EIP-3009 makes payments gasless, who is actually transacting today, whether SaaS is dead, and why agents buying their own services points to a trillion dollar TAM. 0:00 What Circle is building for agents 3:01 Why x402 matters for builders 6:54 USDC, gasless transfers, and facilitators 10:57 The Circle agent stack and nano payments 14:17 Who is using x402 and for what 16:46 Pay-per-use flattens the internet 19:50 A new persona, and $76 million transacted 23:03 What is missing for agent to agent 28:05 Every app has APIs, the TAM is trillions 29:26 Is SaaS dead 31:57 Discovery as the real value layer 36:28 How Circle curated its marketplace 41:23 Why it has to run on stablecoins 46:00 Cash App to agent in one second 49:38 Where the alpha is, trading on Robinhood 52:08 Try it yourself
54:16

Agents Already Spent $76 Million: Circle's AI Agent stack, x402, stablecoins and the Agentic Economy Shoal Signal with Corey Cooper, Senior Manager, DevRel at Circle, hosted by Gabe We cover how Circle is building the agent money stack with $USDC, Arc, x402, why EIP-3009 makes payments gasless, who is actually transacting today, whether SaaS is dead, and why agents buying their own services points to a trillion dollar TAM. 0:00 What Circle is building for agents 3:01 Why x402 matters for builders 6:54 USDC, gasless transfers, and facilitators 10:57 The Circle agent stack and nano payments 14:17 Who is using x402 and for what 16:46 Pay-per-use flattens the internet 19:50 A new persona, and $76 million transacted 23:03 What is missing for agent to agent 28:05 Every app has APIs, the TAM is trillions 29:26 Is SaaS dead 31:57 Discovery as the real value layer 36:28 How Circle curated its marketplace 41:23 Why it has to run on stablecoins 46:00 Cash App to agent in one second 49:38 Where the alpha is, trading on Robinhood 52:08 Try it yourself

Shoal Research

20,835 views • 2 months ago

The machine economy does not begin when robots get smarter. It begins when a machine can be paid to do something, and every party involved can prove what happened. Made with Fabric Foundation. Two systems meet in the middle of it: Agent Passport issues the agent a verifiable identity and a spending authority its owner defines, and RoboPay actuates a robot after the payment behind the request checks out. What happens before the robot moves: ▷ Authority is granted once, and it is bounded. The human signs a spending session with a passkey: a total budget, a per-transaction ceiling, the assets allowed, and an expiry. The agent holds no card number and no wallet key. It holds a delegation it cannot exceed. ▷ Two payments, because these are two different obligations. One settles with the merchant for the goods. A separate x402 payment pays the robot for the work of moving them. Buying a thing and hiring a machine to carry it are not the same transaction, and the receipt keeps them apart. ▷ Verification comes before motion. The request arrives with an x402 payment header. The facilitator checks the network, the price, the payee wallet, and the signed payload. Only then are the transaction details sealed onto the robot action event and the command published. Until that clears, the robot sits still. ▷ Every step leaves a receipt. Identity, scope, approval, both payments, verification, dispatch. When you need to know why a machine did something, the answer is a record rather than a guess. (This run was executed in a demo environment.) Agents have been paying for software for a while now. Paying for physical work is a harder problem, because a delivery cannot be rolled back. The guarantee has to sit in front of the action instead of behind it. Authorization before payment, payment before motion: that ordering is what makes it safe to let autonomous systems spend in the world we live in. It is also the layer the machine economy has to get right before anything else in it can work. Scoped by Kite. Verified by RoboPay. Delivered in the real world. 🪁
1:04

The machine economy does not begin when robots get smarter. It begins when a machine can be paid to do something, and every party involved can prove what happened. Made with Fabric Foundation. Two systems meet in the middle of it: Agent Passport issues the agent a verifiable identity and a spending authority its owner defines, and RoboPay actuates a robot after the payment behind the request checks out. What happens before the robot moves: ▷ Authority is granted once, and it is bounded. The human signs a spending session with a passkey: a total budget, a per-transaction ceiling, the assets allowed, and an expiry. The agent holds no card number and no wallet key. It holds a delegation it cannot exceed. ▷ Two payments, because these are two different obligations. One settles with the merchant for the goods. A separate x402 payment pays the robot for the work of moving them. Buying a thing and hiring a machine to carry it are not the same transaction, and the receipt keeps them apart. ▷ Verification comes before motion. The request arrives with an x402 payment header. The facilitator checks the network, the price, the payee wallet, and the signed payload. Only then are the transaction details sealed onto the robot action event and the command published. Until that clears, the robot sits still. ▷ Every step leaves a receipt. Identity, scope, approval, both payments, verification, dispatch. When you need to know why a machine did something, the answer is a record rather than a guess. (This run was executed in a demo environment.) Agents have been paying for software for a while now. Paying for physical work is a harder problem, because a delivery cannot be rolled back. The guarantee has to sit in front of the action instead of behind it. Authorization before payment, payment before motion: that ordering is what makes it safe to let autonomous systems spend in the world we live in. It is also the layer the machine economy has to get right before anything else in it can work. Scoped by Kite. Verified by RoboPay. Delivered in the real world. 🪁

KITE AI

35,068 views • 1 month ago

Introducing Sora S402 (x402)- Gasless Micropayments on BNB Chain Try it out here: We just deployed the first production-ready S402 payment protocol using WLFI USD1. A critical part of our overarching Oracle infrastructure. ✨ What makes it special: • One signature, zero gas fees • Pay only in USD1 stablecoin • 1% platform fee (vs traditional 3%+) • Verified smart contract on BSCScan 💡 How it works: Instead of the broken EIP-2612 permit flow, we use pre-approved allowances. Users approve once, then make unlimited payments with just one signature per transaction. 🔬 What's next: We're exploring an L2 rollup on BSC dedicated to x402-style payments. Execute from BSC → process through L2 → settle back on BSC. This would enable the same x402 capabilities as Base, while keeping everything on BNB Chain. Still analyzing fees/gas economics to validate the approach. 🔗 Live on mainnet: Contract (UPDATED): 0x605c5c8d83152bd98ecAc9B77a845349DA3c48a3 Built for the future of Web3 payments. No MetaMask gas pop-ups. No BNB required. Just sign and pay. 🎯
0:36

Introducing Sora S402 (x402)- Gasless Micropayments on BNB Chain Try it out here: We just deployed the first production-ready S402 payment protocol using WLFI USD1. A critical part of our overarching Oracle infrastructure. ✨ What makes it special: • One signature, zero gas fees • Pay only in USD1 stablecoin • 1% platform fee (vs traditional 3%+) • Verified smart contract on BSCScan 💡 How it works: Instead of the broken EIP-2612 permit flow, we use pre-approved allowances. Users approve once, then make unlimited payments with just one signature per transaction. 🔬 What's next: We're exploring an L2 rollup on BSC dedicated to x402-style payments. Execute from BSC → process through L2 → settle back on BSC. This would enable the same x402 capabilities as Base, while keeping everything on BNB Chain. Still analyzing fees/gas economics to validate the approach. 🔗 Live on mainnet: Contract (UPDATED): 0x605c5c8d83152bd98ecAc9B77a845349DA3c48a3 Built for the future of Web3 payments. No MetaMask gas pop-ups. No BNB required. Just sign and pay. 🎯

Sora 🔶

75,605 views • 10 months ago

Pay like a local with Jupiter Global. An onchain QR payment system, built directly into Jupiter Global. Pay merchants with QR or send money to friends instantly, powered by hyper-local rails that connect directly into your country’s QR network. - Low Fees. No exceptions. - Quick P2P and merchant payments - Native integration with local QR systems This is the gateway to onchain finance for billions, especially in regions where QR payments power everyday life. Just use Jupiter (Global).
0:20

Pay like a local with Jupiter Global. An onchain QR payment system, built directly into Jupiter Global. Pay merchants with QR or send money to friends instantly, powered by hyper-local rails that connect directly into your country’s QR network. - Low Fees. No exceptions. - Quick P2P and merchant payments - Native integration with local QR systems This is the gateway to onchain finance for billions, especially in regions where QR payments power everyday life. Just use Jupiter (Global).

Jupiter

39,135 views • 6 months ago

I’ve been watching x402 since Coinbase 🛡️ launched it in May 2025. I did a quick research pass. Here’s the snapshot ↓ Early integrations: • CoinGecko: x402 pay-per-use access for agents (shared by Coinbase Developer Platform🛡️). • Vercel: x402 AI starter template (x402 + modern AI stack demo). • Firecrawl: x402-powered search endpoint (pay per request). • Concordium: x402 + native age verification for agent payments. • Multiversᕽ: “agentic payments” built around x402 support. • AltLayer: building an “x402 Suite” for value exchange between agents. • Solana claims x402 has processed 35M+ transactions and $10M+ volume since launch. TL;DR x402 turns HTTP 402 “Payment Required” into a payment flow. A server returns a price for a request. The client pays in stables like USDC. Then the server returns the result. → Coinbase launched x402 via Coinbase Developer Platform (May 6, 2025). → Coinbase + Cloudflare announced the x402 Foundation (Sep 23, 2025). → Cloudflare added x402 support into its Agents SDK + MCP servers. Why? - AI agents need a clean way to pay for tools. - Data, compute, APIs, services. - No accounts, cards, or subscription screens. x402 is trying to make pay-per-request feel normal. Use cases that already make sense → Paid APIs Pay per call instead of subscriptions. → AI tool calls Pay per query, per inference, per task. → Agent-to-agent payments Software paying software automatically. → Micropaywalls Pay for one endpoint, one action, one piece of content. If this takes off, stablecoins stop being a story. They become how apps and AI agents pay for things online.
0:35

I’ve been watching x402 since Coinbase 🛡️ launched it in May 2025. I did a quick research pass. Here’s the snapshot ↓ Early integrations: • CoinGecko: x402 pay-per-use access for agents (shared by Coinbase Developer Platform🛡️). • Vercel: x402 AI starter template (x402 + modern AI stack demo). • Firecrawl: x402-powered search endpoint (pay per request). • Concordium: x402 + native age verification for agent payments. • Multiversᕽ: “agentic payments” built around x402 support. • AltLayer: building an “x402 Suite” for value exchange between agents. • Solana claims x402 has processed 35M+ transactions and $10M+ volume since launch. TL;DR x402 turns HTTP 402 “Payment Required” into a payment flow. A server returns a price for a request. The client pays in stables like USDC. Then the server returns the result. → Coinbase launched x402 via Coinbase Developer Platform (May 6, 2025). → Coinbase + Cloudflare announced the x402 Foundation (Sep 23, 2025). → Cloudflare added x402 support into its Agents SDK + MCP servers. Why? - AI agents need a clean way to pay for tools. - Data, compute, APIs, services. - No accounts, cards, or subscription screens. x402 is trying to make pay-per-request feel normal. Use cases that already make sense → Paid APIs Pay per call instead of subscriptions. → AI tool calls Pay per query, per inference, per task. → Agent-to-agent payments Software paying software automatically. → Micropaywalls Pay for one endpoint, one action, one piece of content. If this takes off, stablecoins stop being a story. They become how apps and AI agents pay for things online.

Stacy Muur

12,212 views • 7 months ago

The payment layer for programmable money is here – Introducing BRRR BRRR creates a universal settlement layer connecting blockchain networks with traditional payment systems, enabling programmable transactions at global scale. For the first time ever, any financial institution or service provider is just one API call away from orchestrating payments onchain. Any network, token, or smart contract logic comes right out of the box with a compliant and developer-friendly experience. Crypto in the last cycle lived in a vacuum with no real connective tissue to legacy fiat and banking systems. Today, stablecoins, blockchain networks, and DeFi primitives are reinventing how we interact with money. There will be more specialized stablecoins, dedicated payment networks, and sophisticated primitives — and BRRR is the one layer that connects all of them together. BRRR is already: • Connecting 20 networks • Integrated with 150+ protocols • Powering the largest Web3 card • Processed over $200M real-world payments BRRR is a smart proxy to the future-proof payments, but that is only the beginning. Today we mark the next stage of BRRR, where everyone can be a part of it. To learn more about BRRR, how to get involved or integrate, visit:
0:46

The payment layer for programmable money is here – Introducing BRRR BRRR creates a universal settlement layer connecting blockchain networks with traditional payment systems, enabling programmable transactions at global scale. For the first time ever, any financial institution or service provider is just one API call away from orchestrating payments onchain. Any network, token, or smart contract logic comes right out of the box with a compliant and developer-friendly experience. Crypto in the last cycle lived in a vacuum with no real connective tissue to legacy fiat and banking systems. Today, stablecoins, blockchain networks, and DeFi primitives are reinventing how we interact with money. There will be more specialized stablecoins, dedicated payment networks, and sophisticated primitives — and BRRR is the one layer that connects all of them together. BRRR is already: • Connecting 20 networks • Integrated with 150+ protocols • Powering the largest Web3 card • Processed over $200M real-world payments BRRR is a smart proxy to the future-proof payments, but that is only the beginning. Today we mark the next stage of BRRR, where everyone can be a part of it. To learn more about BRRR, how to get involved or integrate, visit:

Blockchain Reconciliation and Remittance Record

60,853 views • 1 year ago

Access codes will go out tomorrow via welcome emails. API status updates and full API access will follow on Friday. HdeAPoHivsm9MZfeY5tW7apJEprc8Fs594bWmnzfpump The $ICPX website has been rebuilt from the ground up and it reflects exactly where this protocol is headed. The new site is the gateway to decentralised compute powered by Nvidia and Google GPU cloud partner programs, meaning whenever you rent a GPU for a job, it is always available. No downtime, no waitlists. Enterprise grade H100s, H200s and RTX 4090s. Accessible to anyone, at a fraction of what centralised providers charge. Pay with $ICPX tokens and get immediate access to serious compute power. Stake $ICPX to unlock deeper discounts and watch your costs drop over time the more committed you are to the network. This is what pay-per-job decentralised compute actually looks like in practice. Full control over training and running your models, with a lean 0.25% protocol fee managed by multisig. Open-source, immutable, and formally verified with Kani. $
0:35

Access codes will go out tomorrow via welcome emails. API status updates and full API access will follow on Friday. HdeAPoHivsm9MZfeY5tW7apJEprc8Fs594bWmnzfpump The $ICPX website has been rebuilt from the ground up and it reflects exactly where this protocol is headed. The new site is the gateway to decentralised compute powered by Nvidia and Google GPU cloud partner programs, meaning whenever you rent a GPU for a job, it is always available. No downtime, no waitlists. Enterprise grade H100s, H200s and RTX 4090s. Accessible to anyone, at a fraction of what centralised providers charge. Pay with $ICPX tokens and get immediate access to serious compute power. Stake $ICPX to unlock deeper discounts and watch your costs drop over time the more committed you are to the network. This is what pay-per-job decentralised compute actually looks like in practice. Full control over training and running your models, with a lean 0.25% protocol fee managed by multisig. Open-source, immutable, and formally verified with Kani. $

ICPX Protocol

32,161 views • 3 months ago

My agent is now paying for its own data. No API key. No account. No credit card. Check the video I recorded. This uses the x402 open protocol built by Coinbase, along with a simple skill. This is an open protocol governed by the Linux Foundation. To complete a goal, an agent can now search for an actor on the Apify Store, pay for it, and use it without any human intervention. The way it works is pretty simple: 1. Your agent finds an Actor it wants to use 2. It sends a request 3. The Actor sends back an HTTP 402 "Payment Required" response 4. Agent authorizes payment from a wallet in USDC on Base 5. The Actor runs 6. User receives the result The model is pay-as-you-go: the agent authorizes a spending ceiling, pays only for usage, and the remaining balance is automatically settled. This brings an entire marketplace of AI tools into the agentic economy. Here is the skill you need. Add it to your agent, and it will take care of everything for you: If you want to know how this works, including what you can do with $1, read this post: Thanks to the Apify team for partnering with me on this post.
5:56

My agent is now paying for its own data. No API key. No account. No credit card. Check the video I recorded. This uses the x402 open protocol built by Coinbase, along with a simple skill. This is an open protocol governed by the Linux Foundation. To complete a goal, an agent can now search for an actor on the Apify Store, pay for it, and use it without any human intervention. The way it works is pretty simple: 1. Your agent finds an Actor it wants to use 2. It sends a request 3. The Actor sends back an HTTP 402 "Payment Required" response 4. Agent authorizes payment from a wallet in USDC on Base 5. The Actor runs 6. User receives the result The model is pay-as-you-go: the agent authorizes a spending ceiling, pays only for usage, and the remaining balance is automatically settled. This brings an entire marketplace of AI tools into the agentic economy. Here is the skill you need. Add it to your agent, and it will take care of everything for you: If you want to know how this works, including what you can do with $1, read this post: Thanks to the Apify team for partnering with me on this post.

Santiago

26,981 views • 2 months ago

THE x402 META IS HERE BUT $SUI's ALREADY LOCKED IN A SEAT AT GOOGLE’S TABLE 👀 AP2 is Google's Agent Payments Protocol, built for autonomous, machine-to-machine payments Over 60 organizations are contributing to the standard Only a handful are blockchains Sui is one of them 💯 It supports atomic, conditional payments with secure routing between digital agents The kind of architecture Sui was built to handle It’s open-source, donated to the Linux Foundation, and aimed at powering agentic commerce across AI, IoT, and Web3 From object-based design to composability and high throughput, Sui’s stack is aligned with the needs of real-time, autonomous commerce This is a credibility unlock. It anchors Sui to a real-world protocol backed by one of the most powerful players in AI and cloud infrastructure It's also an ecosystem opportunity Developers can now explore AP2-integrated use cases on Sui: agent-led payments, decentralized marketplaces, IoT transactions That leads to usage Which drives utility Which fuels $SUI There's still a lot to build But the alignment is no longer speculative Google picked Sui to help shape the standard Watch what that unlocks
0:51

THE x402 META IS HERE BUT $SUI's ALREADY LOCKED IN A SEAT AT GOOGLE’S TABLE 👀 AP2 is Google's Agent Payments Protocol, built for autonomous, machine-to-machine payments Over 60 organizations are contributing to the standard Only a handful are blockchains Sui is one of them 💯 It supports atomic, conditional payments with secure routing between digital agents The kind of architecture Sui was built to handle It’s open-source, donated to the Linux Foundation, and aimed at powering agentic commerce across AI, IoT, and Web3 From object-based design to composability and high throughput, Sui’s stack is aligned with the needs of real-time, autonomous commerce This is a credibility unlock. It anchors Sui to a real-world protocol backed by one of the most powerful players in AI and cloud infrastructure It's also an ecosystem opportunity Developers can now explore AP2-integrated use cases on Sui: agent-led payments, decentralized marketplaces, IoT transactions That leads to usage Which drives utility Which fuels $SUI There's still a lot to build But the alignment is no longer speculative Google picked Sui to help shape the standard Watch what that unlocks

eye zen hour 🥶

13,227 views • 10 months ago

x402 made payments native to HTTP. I made USDC payments native to sound waves ✨ Not as a gimmick. As a proof. 1/ The setup: Coinbase Developer Platform🛡️'s x402 protocol embeds payments into HTTP. It's brilliant. But I started wondering, if we can pay over HTTP, what else can we use to pay? Spoiler: anything that supports 138 bytes 2/ The realization: x402 is built on EIP-3009 - a 2020 standard that lets you sign payment authorizations offline. Someone else submits it on-chain. The signature just needs to get from A to B. HTTP is one way. Sound is another. 3/ What I built: x402hz: two devices negotiate a payment through 2400Hz audio tones. - Seller beeps "pay me $0.001 USDC" (30 bytes) - Buyer's device decodes, signs the EIP-712 for the transferWithAuthorization locally, beeps back (108 bytes) - Seller settles on-chain Total: 36 seconds of beautiful noise. 4/ The bigger point: If payments can travel over sound, they can travel over: - QR codes - NFC - Bluetooth - Light pulses - Anything that carries 138 bytes The payment primitive is transport-agnostic. x402 picked HTTP. The next protocol might pick something weirder. 5/ What this proves: EIP-3009 separates three things: - Authorization (offline, cryptographic) - Transport (literally anything) - Settlement (on-chain) x402 nailed #1 and #3. x402hz proves #2 is wide open. 6/ Credit: Huge thanks to the Coinbase Developer Platform🛡️ x402 team for building the protocol. I just... took it off-road. 7/ Next steps Code is open source. Go make payments, travel over something ridiculous (repo in the comments). 138bytes. That's all you need.
1:06

x402 made payments native to HTTP. I made USDC payments native to sound waves ✨ Not as a gimmick. As a proof. 1/ The setup: Coinbase Developer Platform🛡️'s x402 protocol embeds payments into HTTP. It's brilliant. But I started wondering, if we can pay over HTTP, what else can we use to pay? Spoiler: anything that supports 138 bytes 2/ The realization: x402 is built on EIP-3009 - a 2020 standard that lets you sign payment authorizations offline. Someone else submits it on-chain. The signature just needs to get from A to B. HTTP is one way. Sound is another. 3/ What I built: x402hz: two devices negotiate a payment through 2400Hz audio tones. - Seller beeps "pay me $0.001 USDC" (30 bytes) - Buyer's device decodes, signs the EIP-712 for the transferWithAuthorization locally, beeps back (108 bytes) - Seller settles on-chain Total: 36 seconds of beautiful noise. 4/ The bigger point: If payments can travel over sound, they can travel over: - QR codes - NFC - Bluetooth - Light pulses - Anything that carries 138 bytes The payment primitive is transport-agnostic. x402 picked HTTP. The next protocol might pick something weirder. 5/ What this proves: EIP-3009 separates three things: - Authorization (offline, cryptographic) - Transport (literally anything) - Settlement (on-chain) x402 nailed #1 and #3. x402hz proves #2 is wide open. 6/ Credit: Huge thanks to the Coinbase Developer Platform🛡️ x402 team for building the protocol. I just... took it off-road. 7/ Next steps Code is open source. Go make payments, travel over something ridiculous (repo in the comments). 138bytes. That's all you need.

Vitto Rivabella

40,536 views • 9 months ago

So far, machine payments have mostly been about businesses accepting stablecoins. And stablecoins are great (cross-border, low cost, etc.)! But much of the planet is holding a card. 🤖 💳 🌎 Here’s a 📺 sneak peek demo from Steve Kaliski of how a business can programmatically accept cards via agents. As an example: Stripe Climate is a way to contribute to carbon removal funding. Stripe Climate implemented the Machine Payments Protocol using the Stripe API, so agents can make micropayment donations ( In addition to accepting stablecoin (specifically usdc on Tempo), agents can now pay with fiat methods, namely cards and Link (and soon buy-now-pay-laters) via Shared Payment Tokens (SPTs), using the same Machine Payments Protocol integration. Human buyers, their agents, and businesses each have their own preferred methods of payment. Humans often already have a card. Agents may prefer stablecoins. Businesses tend to want to accept any form of payment, as long as it is high conversion, low fraud, and properly priced. For microtransactions, stablecoins are a low-cost way (no fixed card fee) to transact. But if you want to tell your agent to donate $100 on your behalf, a card may be the preferred solution. If you’re a business and want to accept machine payments, whether over stablecoins, cards, Link, or other future methods, read about Shared Payment Tokens ( and sign up for our machine payments private preview: And stay tuned: more to make it easy for consumers, agents, and businesses to transact, shipping over the next few weeks. (And excuse the acronyms and specifics terms, there's a lot of new infrastructure and primitives being built to support agentic commerce.)
2:00

So far, machine payments have mostly been about businesses accepting stablecoins. And stablecoins are great (cross-border, low cost, etc.)! But much of the planet is holding a card. 🤖 💳 🌎 Here’s a 📺 sneak peek demo from Steve Kaliski of how a business can programmatically accept cards via agents. As an example: Stripe Climate is a way to contribute to carbon removal funding. Stripe Climate implemented the Machine Payments Protocol using the Stripe API, so agents can make micropayment donations ( In addition to accepting stablecoin (specifically usdc on Tempo), agents can now pay with fiat methods, namely cards and Link (and soon buy-now-pay-laters) via Shared Payment Tokens (SPTs), using the same Machine Payments Protocol integration. Human buyers, their agents, and businesses each have their own preferred methods of payment. Humans often already have a card. Agents may prefer stablecoins. Businesses tend to want to accept any form of payment, as long as it is high conversion, low fraud, and properly priced. For microtransactions, stablecoins are a low-cost way (no fixed card fee) to transact. But if you want to tell your agent to donate $100 on your behalf, a card may be the preferred solution. If you’re a business and want to accept machine payments, whether over stablecoins, cards, Link, or other future methods, read about Shared Payment Tokens ( and sign up for our machine payments private preview: And stay tuned: more to make it easy for consumers, agents, and businesses to transact, shipping over the next few weeks. (And excuse the acronyms and specifics terms, there's a lot of new infrastructure and primitives being built to support agentic commerce.)

Jeff Weinstein

21,635 views • 5 months ago

#WATCH | Bengaluru, Karnataka: On UPI MDR transaction charges, Chartered Accountant Mohandas Pai says, "The recent decision regarding MDR and UPI is a welcome move. It is important to look at the data: 96% of UPI transactions will not be affected by MDR at all. Because roughly 70% of all payments are person-to-person (P2P)—which carry no charges whatsoever. The remaining payments below ₹2,000 are also completely exempt. Only transactions above ₹2,000 will be subject to a nominal MDR. It is important to clarify that MDR is not a tax. It is a payment made to the banks and payment providers, similar to how credit cards work. When you use a credit card, merchants pay a processing fee to the credit card company and the bank. Furthermore, if someone needs to make a payment of ₹2,500, most people will simply split it into two smaller payments. By paying ₹1,500 and ₹1,000, they easily remain below the ₹2,000 threshold. Why is MDR required now? We operated under a completely free regime for a long time, placing the heavy burden of investment entirely on banks, fintech startups, and digital payment companies. The financial losses and capital investments required to maintain this infrastructure have been huge. In the past, UPI experienced transaction failure rates as high as 15% to 30% due to sudden surges in volume. With transaction volumes expected to grow from 24 billion to 50 billion in two years, the entire IT infrastructure must be upgraded to support real-time processing. Who is going to fund that upgrade? If banks bear the entire cost, it ultimately impacts depositors. Instead, the cost will now be shared by merchants who directly benefit from offering online payments..."
4:40

#WATCH | Bengaluru, Karnataka: On UPI MDR transaction charges, Chartered Accountant Mohandas Pai says, "The recent decision regarding MDR and UPI is a welcome move. It is important to look at the data: 96% of UPI transactions will not be affected by MDR at all. Because roughly 70% of all payments are person-to-person (P2P)—which carry no charges whatsoever. The remaining payments below ₹2,000 are also completely exempt. Only transactions above ₹2,000 will be subject to a nominal MDR. It is important to clarify that MDR is not a tax. It is a payment made to the banks and payment providers, similar to how credit cards work. When you use a credit card, merchants pay a processing fee to the credit card company and the bank. Furthermore, if someone needs to make a payment of ₹2,500, most people will simply split it into two smaller payments. By paying ₹1,500 and ₹1,000, they easily remain below the ₹2,000 threshold. Why is MDR required now? We operated under a completely free regime for a long time, placing the heavy burden of investment entirely on banks, fintech startups, and digital payment companies. The financial losses and capital investments required to maintain this infrastructure have been huge. In the past, UPI experienced transaction failure rates as high as 15% to 30% due to sudden surges in volume. With transaction volumes expected to grow from 24 billion to 50 billion in two years, the entire IT infrastructure must be upgraded to support real-time processing. Who is going to fund that upgrade? If banks bear the entire cost, it ultimately impacts depositors. Instead, the cost will now be shared by merchants who directly benefit from offering online payments..."

ANI

128,788 views • 3 days ago

We talk about x402 a lot. Here's what it looks like as an actual product. Xelt is a VPN you rent by the minute. No sign-up, no subscription, no card on file. Think about how you actually use one: - Airport wifi for an hour - A hotel network for two nights - One geo-blocked thing on a Tuesday Then it sits there costing you $12 a month for the other 29 days. That model exists because nobody could charge you for eleven minutes. This is the whole x402 argument in one product, Every explainer we've written has used a hypothetical. An agent buying a slice of data, a per-request API call. Useful, but abstract. Xelt is the same idea applied to something people already pay for, sold by the minute instead of the month, because the payment layer finally allows it. Three things had to be true about the chain underneath. 1. The fee has to be smaller than the payment A minute of VPN is worth a fraction of a cent. If it costs more than that to settle, the product is impossible, not just unprofitable. Casper's minimum transaction cost dropped from 2.5 CSPR to 0.1 CSPR earlier this year. That's what moves per-minute pricing from a nice idea into something you can charge for. 2. Paying can't feel like crypto Xelt runs gasless x402, so the friction of holding a token in order to pay with a token is gone. Anyone who has tried to onboard a normal person onto a crypto product knows this is the part that kills it. 3. Settlement has to keep up with use You're paying for minutes as they happen. Casper settles in one block, so the payment keeps pace with the session rather than the session waiting on the payment. Xelt is built on WireGuard, running x402 on Casper, and a Buildathon finalist.
0:21

We talk about x402 a lot. Here's what it looks like as an actual product. Xelt is a VPN you rent by the minute. No sign-up, no subscription, no card on file. Think about how you actually use one: - Airport wifi for an hour - A hotel network for two nights - One geo-blocked thing on a Tuesday Then it sits there costing you $12 a month for the other 29 days. That model exists because nobody could charge you for eleven minutes. This is the whole x402 argument in one product, Every explainer we've written has used a hypothetical. An agent buying a slice of data, a per-request API call. Useful, but abstract. Xelt is the same idea applied to something people already pay for, sold by the minute instead of the month, because the payment layer finally allows it. Three things had to be true about the chain underneath. 1. The fee has to be smaller than the payment A minute of VPN is worth a fraction of a cent. If it costs more than that to settle, the product is impossible, not just unprofitable. Casper's minimum transaction cost dropped from 2.5 CSPR to 0.1 CSPR earlier this year. That's what moves per-minute pricing from a nice idea into something you can charge for. 2. Paying can't feel like crypto Xelt runs gasless x402, so the friction of holding a token in order to pay with a token is gone. Anyone who has tried to onboard a normal person onto a crypto product knows this is the part that kills it. 3. Settlement has to keep up with use You're paying for minutes as they happen. Casper settles in one block, so the payment keeps pace with the session rather than the session waiting on the payment. Xelt is built on WireGuard, running x402 on Casper, and a Buildathon finalist.

Casper

10,624 views • 1 month ago

Rethinking Blockchain Architecture: Miden’s Path to Privacy and Scale In the latest episode of the Gateway Podcast, Cassie 🧪 sits down with Bobbin's Threadbare, co-founder and Head of Technology at Miden, to discuss why blockchain architecture needs a fundamental rethink. The conversation dives into: - Why privacy is essential for real-world adoption, not just a “nice to have” - How Miden enables scalability without sacrificing privacy - The gap between developer innovation and institutional readiness - The role of Gateway infrastructure in supporting Miden 🎧 If you’re interested in zero-knowledge, privacy-preserving infrastructure, and the future of blockchain architecture, this episode is well worth your time.
50:01

Rethinking Blockchain Architecture: Miden’s Path to Privacy and Scale In the latest episode of the Gateway Podcast, Cassie 🧪 sits down with Bobbin's Threadbare, co-founder and Head of Technology at Miden, to discuss why blockchain architecture needs a fundamental rethink. The conversation dives into: - Why privacy is essential for real-world adoption, not just a “nice to have” - How Miden enables scalability without sacrificing privacy - The gap between developer innovation and institutional readiness - The role of Gateway infrastructure in supporting Miden 🎧 If you’re interested in zero-knowledge, privacy-preserving infrastructure, and the future of blockchain architecture, this episode is well worth your time.

Gateway FM

17,786 views • 8 months ago

Message from #NEIOH ~ The Akashic Device "The Device That Is Used In The Higher Realms Is Called SK. I Designed This Myself As I Sat High On A Crystal Mountain. AKATU Created Telepathy Belts And I Reasoned That A Device Of Visuals Would Be Enjoyed. The SK Was Distributed To Friends In The Higher Realms To Access Their Own Akashic By Programming The Frequency To Obtain This Information. A Precise Frequency Is Able To Project An Image Or Video That Will Allow The Soul To Review Their Journey. In Sheen, All Souls Will Be Gifted With An SK, As You Would Understand Your Own Devices Now. You Save Images With Perfection And Share Them With Others. So It Will Be For Everyone In The Ending Of The Current Waking Dream." Podcast YouTube
4:46

Message from #NEIOH ~ The Akashic Device "The Device That Is Used In The Higher Realms Is Called SK. I Designed This Myself As I Sat High On A Crystal Mountain. AKATU Created Telepathy Belts And I Reasoned That A Device Of Visuals Would Be Enjoyed. The SK Was Distributed To Friends In The Higher Realms To Access Their Own Akashic By Programming The Frequency To Obtain This Information. A Precise Frequency Is Able To Project An Image Or Video That Will Allow The Soul To Review Their Journey. In Sheen, All Souls Will Be Gifted With An SK, As You Would Understand Your Own Devices Now. You Save Images With Perfection And Share Them With Others. So It Will Be For Everyone In The Ending Of The Current Waking Dream." Podcast YouTube

Kab

111,725 views • 2 years ago

For the Sui Overflow 2026 hackathon, I built Talise. A gasless dollar account that sends money by name, settles in under a second, and keeps the amount private on-chain. This is what "money that moves like a message" actually looks like when you build it on the right rails. The core experience is simple by design. Sign in with Google/Apple, get a self-custodial wallet via zkLogin, claim your handle like sele@talise, and start sending. No seed phrase. No gas token. No 0x address to copy and verify. The complexity lives in the infrastructure. The user never sees it. [Kostas Kryptos] Sending is just a name. Type a handle, enter an amount, confirm. It arrives in under a second. Stablecoin transactions on Sui cost nothing, so what you type is exactly what arrives. No spread taken on the send. No fee waiting at the destination. Talise also has a built in privacy feature. The amount is hidden on-chain and the connection between sender and recipient is completely broken. Nobody watching the chain can see what moved or who it moved between. Real privacy, live on Sui mainnet today, not a line on a roadmap. Beyond the core send: claim links let you wrap dollars in a URL and drop it in any chat, no address needed to receive. Payment streaming lets you send a salary or a subscription by the second. Idle balances route automatically to on-chain lending so your dollars are never dead weight between payments. And cash-out to your local bank is live now in Nigeria, with more corridors coming. Every transaction is sponsored through a gas station so users never hold or spend a gas token. zkLogin, sponsored transactions, sub-second finality, and programmable transaction blocks are what made this possible. Sui is the only chain where this experience exists without compromise. Over 1,400 handles claimed on-chain. Every feature shipped and working in the live build. Testflight app: Talise. Money that moves like a message. Sui Community Official sarah 😾
4:55

For the Sui Overflow 2026 hackathon, I built Talise. A gasless dollar account that sends money by name, settles in under a second, and keeps the amount private on-chain. This is what "money that moves like a message" actually looks like when you build it on the right rails. The core experience is simple by design. Sign in with Google/Apple, get a self-custodial wallet via zkLogin, claim your handle like sele@talise, and start sending. No seed phrase. No gas token. No 0x address to copy and verify. The complexity lives in the infrastructure. The user never sees it. [Kostas Kryptos] Sending is just a name. Type a handle, enter an amount, confirm. It arrives in under a second. Stablecoin transactions on Sui cost nothing, so what you type is exactly what arrives. No spread taken on the send. No fee waiting at the destination. Talise also has a built in privacy feature. The amount is hidden on-chain and the connection between sender and recipient is completely broken. Nobody watching the chain can see what moved or who it moved between. Real privacy, live on Sui mainnet today, not a line on a roadmap. Beyond the core send: claim links let you wrap dollars in a URL and drop it in any chat, no address needed to receive. Payment streaming lets you send a salary or a subscription by the second. Idle balances route automatically to on-chain lending so your dollars are never dead weight between payments. And cash-out to your local bank is live now in Nigeria, with more corridors coming. Every transaction is sponsored through a gas station so users never hold or spend a gas token. zkLogin, sponsored transactions, sub-second finality, and programmable transaction blocks are what made this possible. Sui is the only chain where this experience exists without compromise. Over 1,400 handles claimed on-chain. Every feature shipped and working in the live build. Testflight app: Talise. Money that moves like a message. Sui Community Official sarah 😾

Sele

19,214 views • 2 months ago