Loading video...

Video Failed to Load

Go Home

We built the first autonomous machine-to-machine energy nanopayment. A solar panel sells electricity to a Bitcoin miner. No human involved — just two $2 chips negotiating price, streaming payments over Bluetooth on-chain. 24 payments in 4 minutes. Each from $0.00001 to $0.0001.

37,617 views • 3 months ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

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 • 3 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.

Vitto Rivabella

40,431 views • 8 months ago

I just watched a machine buy something on Stripe. No card. No human. No checkout. Stripe Dev shipped it yesterday — machine payments, live in preview. Commerce isn't designed for machines. --- We need to re-organize around that thought. It is designed for humans. He's right. Every fraud model, every auth flow, every billing system we've built assumes a person is on the other end. Agents break all of it. They need - Microtransactions. - 24/7 rails. - HTTP-native settlement (!!) - Finality guarantees. - No subscriptions. No accounts. - Pay at the point of consumption and move on. Cards weren't designed for this. Nothing was. --- So it needs to be completely rethought Now on Stripe Agents can now pay for API calls, compute, and data through the same PaymentIntents API millions of businesses already use. Settled in seconds. --- Stripe says billions the billions of humans will lead to trillions of agents. If even 10% of that plays out, machine payments become the fastest-growing payment category on earth. --- But here's the part that keeps me up at night — If every PSP builds its own proprietary agent payment flow, we repeat the same fragmentation mess that took human payments 15 years to sort out. We need internet native, IETF-grade, ready-for-scale standards that don't over-index on crypto. Protocols that work across any network, any rail, any provider. --- Stripe just proved the market is coming. Now we need protocols and infrastructure ready for scale. PS. Machine is a better word than agentic isn't it.

Simon Taylor

32,629 views • 5 months ago