Sabitlenmiş Tweet
Kartik
2.4K posts

Kartik retweetledi
Kartik retweetledi
Kartik retweetledi

We've added MPP / Tempo Wallet support to Foundry - out on latest nightly.
- foundryup -n tempo
- cast bn -r tempo
- cast send erc20 <...> -r tempo --from `tempo wallet whoami --json-output | jq -r .wallet` (to be made less verbose)
h/t @onbjerg @gndizzy @zerosnacks
Georgios Konstantopoulos@gakonst
with MPP we'll finally be able to ship high quality RPC URLs built-in Foundry w/o us having to subsidize as that's unsustainable so any user that has onboarded once to Tempo Wallet will be able to just use any paid RPC API w/o any additional configuration + traces + low latency
English
Kartik retweetledi

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.

English

@sweetman_eth @varunsrin @mpp Don't have the code and it wouldn't work anymore anyway. We haven't added websocket support to the mpp sdks yet, but will do that soon and then should be easy to use!
English

@Slokh @varunsrin @mpp Is your codebase open source? I am interested in streaming payments for audio generation, especially via Lyria 3.
English

I'm trying to use StableEnrich to fetch X tweets/profile information via Tempo MMP but it's returning 404.
Any advice @Slokh ?

English

The real metric is Sandwiches Per Second. Nothing else really matters
Georgios Konstantopoulos@gakonst
did you order a sandwich with mpp yet stranger
English

@mpp @tempo Have been working on our Tempo CLI that interfaces with both, check it out!
wallet.tempo.xyz/welcome
English

Excited to see what people build with @mpp and @tempo now that they're public!
Been a crazy first 6 weeks btw 🫡
Tempo@tempo
Tempo Mainnet is live! Starting today, anyone can build on Tempo through our public RPC endpoints. Alongside mainnet, we’re introducing the Machine Payments Protocol, an open standard for machine payments.
English
Kartik retweetledi

@GSkrovina I was at a restaurant paying and the terminal showed the emergency alert as well while I was signing 💀
English

Pretty cool seeing projects changing hands rather than winding down recently.
@farcaster_xyz -> @neynarxyz
@LC -> @masknetwork
@foundation -> @Blackdoveart
Assuming a combination of them being built on an open crypto stack and AI tooling making it easier than ever before to build context quickly.
English
Kartik retweetledi
Kartik retweetledi









