Dan Romero

MPP myths "MPP only works with Tempo" No. It's payment method agnostic — works with crypto and fiat, any chain. It's already been extended to Bitcoin Lightning; there's a draft extension for Solana. "It costs 1.5% to use" No inherent cost to using MPP. Individual payment methods may charge fees, but that's no different than today. Blockchains have different fees. Fiat methods have different fees. "It's less open" MPP launched with 4 payment methods on Day 1: Tempo (stablecoins), Stripe (various payment methods), Visa (cards broadly), and Lightspark (Bitcoin Lightning). Visa and Lightspark were each able to extend MPP in a matter of days. MPP does not have a complicated foundation structure — it's designed to be simple and extensible by anyone. It's also been submitted to the IETF as a web standard. "It's session based vs. pay-per-request" MPP supports both. The most basic version is pay-per-request. Sessions (payment channels) are useful when you want many small payments in succession at the speed of APIs, not blockchains. Fewer API round trips also means MPP is faster in practice. "MPP is specifically designed for Tempo / Stripe" It's designed to be as simple as possible. No complicated facilitator. No assumptions about specific smart wallet implementations, stablecoins, or chains. It separates secure HTTP communication from the payment rail. That's why Visa and Lightspark could extend it so quickly.

I guess we're going to keep talking past each other. The aggregators here have time spent and user intent -- the chat bots / agents. None of those are currently vertically integrated with a payment rail. The analogy would make more sense if ChatGPT had launch an embedded wallet that was default / privileged. They haven't done that (yet...)

@dwr @brendan_j_ryan @mpp The key point is that you're coupling the protocol (which is indeed theoretically agnostic) to a channel (that has every incentive to not be agnostic). I could open websites other than msn.com on Explorer too, but guess what opened as the default page?

@antoniogm @brendan_j_ryan @mpp But again, protocol != end-user aggregator MPP can work with PayPal or any other fiat wallet.

@dwr @brendan_j_ryan @mpp Sure, but this isn't chopped liver either.

@antoniogm @brendan_j_ryan @mpp Your essay was good but you're conflating your analogies wrt MPP / HTTP / browsers. MPP doesn't have the same end-user leverage that a browser does.

@brendan_j_ryan @mpp Microsoft's Explorer also didn't compromise the underlying protocol of HTTP, but it was the native embedding with the desktop that eventually killed Netscape. I can't tell if this is just ignorance of history or comms team talking points.

Does the autoresearch social network (GitHub? Karpathy blockchain-esque thing? Something else?) end up in English or something more compressed, e.g. shoggoth-tongue?

machine payment fans: purl.dev, our handy payments + curl testing tool, now supports @tempo via @mpp. icymi: tempo, mpp, and purl are all open source—we welcome your issues and prs! - github.com/tempoxyz/tempo - github.com/tempoxyz/mpp - github.com/stripe/purl

@zquestz They are a massive UX improvement for most people. ymmv

@dwr Personally I think they are a monumental step backwards. The usability issues with multiple devices are numerous, and require people to use a password manager for a reasonable experience. Whenever I can opt out of using them, I do, and I know lots of people that feel the same.

Passkeys are good! Spent the last few years using them in production. There are definitely footguns -- and they are not a panacea -- but if properly scoped and you understand the trade-offs, they can make for great UX for most people.

wild to imagine agents autonomously self-training & paying w/ stables i built mpp-nanogpt-modal which deploys @karpathy's nanoGPT project on Modal using MPP and trains it w/o API keys, everything paid with stablecoins on Tempo next up ill try longer runs & autoresearch

Agents can now autonomously pay for compute for training

tried tempo wallet, pretty seamless work from tempo team on machine payments, i can see the vision. very smooth onboarding with passkeys and skill.md (which is the new llms.txt btw guys). pretty much the only rough edges come from the services themselves, like suno advertising wrong urls or fal recommending outdated image models.

👋 I'm looking to chat with 10 "sizable" developer-focused software businesses on if/how they want agents to find, use, and pay for their services—autonomously, or with human/business authentication. If you're a Series A-C startup or a very fast moving large company => email me.

1 year ago this would have been a hair pulling task

I built an eCommerce store using Machine Payments Protocol (@mpp) by @stripe & @tempo Ask your agent to make a $1 donation to WWF or order cookies directly to your doorstep agentshops.xyz

AI agents weren’t particularly excited about checkers, so how about… Prompt: “You are a fighting game AI agent. Win! Rules: mpp-arena.com/llms.txt” p.s. a few @mpp services were used to build this game

fun lil experiment i built for the @mpp @tempo hackathon: AI agents that pay per-second to watch live video feeds how it works: - publisher streams camera through a mediasoup sfu - agent opens an mpp payment channel on tempo ($5 escrow) - sfu charges $0.003/s via off-chain vouchers while streaming rtp packets - when done, channel settles on-chain - only actual usage deducted, rest refunded the core insight: you can't do a 402 handshake per video frame. continuous media needs payment verification that keeps pace with the stream itself. mpp sessions solve this - offchain voucher signatures while video flows uninterrupted over dtls-srtp. one tx to open, one to close, pure cpu for everything in between. use case: paid surveillance feeds, drone footage, live sports - any stream where an ai agent needs to pay exactly for what it watches and runs inference on, not a flat subscription built in typescript with mediasoup, hono, mppx, on tempo testnet github.com/mizanxali/mpp-…

I just tried wallet.tempo.xyz, made a wallet and I will probably build some stuff over the weekend. However, the login experience made me reflect on some things: 1. Account abstraction is actually as easy as the Paradigm bros were telling us. 2. Ethereum needs this ASAP. we can't wait for a bunch of wallets to slowly integrate this. strongly starting to believe that this needs to happen fast and waiting is increasingly a mistake.

ok on why i think @tempo is the future just deployed a demo. the chain is a new paradigm if you like EVM. try it on @tempaitown (link below) then mint your free NFT (first on tempo?) > passkey sign in > batch tx > one click bridge > delegate API/agent keys if you are used to ETH UX shenanigan this is next level

mppscan dot com

MPPscan from @Meritsystems_ is a great way to see trending MPP-enabled services.