swft

3.3K posts

swft banner
swft

swft

@swftbb

onchain | dev | data | building @protonauts

Katılım Şubat 2011
2K Takip Edilen969 Takipçiler
swft
swft@swftbb·
@dwr ah okay i saw this screenshot floating around but didn’t see the 1.5% mentioned in the docs so didn’t know if it got deleted or moved somewhere else appreciate the clarification
swft tweet media
English
1
0
0
61
Dan Romero
Dan Romero@dwr·
@swftbb MPP doesn’t have fees. Tempo is basically free. If you use the Stripe method, then you would pay those fees.
English
1
0
2
94
PhiMarHal
PhiMarHal@PhiMarHal·
@danrobinson Like, how does a person like you not value their own intellectual honesty? Especially in a situation where it costs nothing. It's genuinely improbable the public at large would change their mind on Tempo as a whole because of this one tweet here.
English
2
0
16
168
Dan Robinson
Dan Robinson@danrobinson·
Tempo mainnet is live and permissionless We designed it to be the best blockchain for payments, and every feature serves that goal We're also introducing a new standard for web and agentic payments, the Machine Payments Protocol, which you can use today
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
53
7
142
107.9K
swft retweetledi
Zach Pandl
Zach Pandl@LowBeta·
It's official: "onchain" not "on-chain" Footnote 1 from SEC guidance yesterday
Zach Pandl tweet media
English
95
114
853
75.3K
Matt Huang
Matt Huang@matthuang·
A few things I like about MPP (machine payments protocol) Payment-method agnostic (supports stablecoins on Tempo, Stripe, cards, Bitcoin lightning, etc) Open and extensible (without our permission) Streaming payments (via state channels) Minimal and efficient
Machine Payments Protocol (mpp.dev)@mpp

Introducing the Machine Payments Protocol: an open standard for machine payments co-authored by @tempo and @stripe MPP is designed to be extensible and payment-method agnostic, already supporting stablecoins, cards, and more.

English
23
13
205
57.7K
Apex777.eth
Apex777.eth@apex_ether·
Thoughts on Tempo and MPP?
English
6
0
5
1.1K
swft
swft@swftbb·
@danrobinson @bemevolent isn’t there a 1.5% fee capture by stripe on payments over $0.33? why would i use this and pay fees when x402 v2 also handles cards + stablecoins?
English
0
0
0
62
Dan Robinson
Dan Robinson@danrobinson·
1) MPP is compatible with credit cards! x.com/jackforestell/… MPP provides a standard way for websites to quote the price and accept payment (rather than agent having to navigate a human UI for card entry) 2) Stablecoins have some advantages over cards, particularly for small payments and on the merchant side: * Can spin up new credentials (with custom spending limits) instantly and for less than a cent * ~$0.001 rather than $0.30 fixed fee (and free for incremental streaming payments); no % fee * Lower overhead on merchants since there are no chargebacks I think it unlocks a lot of services that you simply would never offer if you could only use card rails
Jack Forestell@jackforestell

Enter @Visa’s new card spec for Machine Payments Protocol (MPP)—an open standard from @tempo and @stripe—bringing card‑based payments into autonomous, machine‑to‑machine flows. Combined with enablers like @BasisTheory and @getVGS, developers can securely tokenize and orchestrate credentials while transacting on global card rails. Open by design. No single rail. Global reach.

English
3
0
15
1.5K
swft retweetledi
Pranshu Rastogi 🦇🔊
Pranshu Rastogi 🦇🔊@pranshurastogii·
Ethereum planned to cut L1 deposit wait times by 98%. Not with a hard fork. Not with a new chain. Not by breaking anything. Just by counting attestations differently. The Fast Confirmation Rule (FCR) is the upgrade shipping to @ethereum right now ↓
English
5
16
145
9.4K
swft
swft@swftbb·
we have fast. what we need is secure.
English
0
0
0
27
swft
swft@swftbb·
i can tell a new SaaS product is going to fail when you see them still trying to guess what the user wants
English
0
0
0
40
swft
swft@swftbb·
@AdamRackis yea the dude broke like 10 cardinal rules of deployments 😭 but let’s blame the tool
English
0
0
1
88
swft
swft@swftbb·
after playing around with openclaw.. it’s probably my least favorite agentic orchestrator setup mostly all hype vs different approaches
English
0
0
0
63
swft retweetledi
pashov
pashov@pashov·
🚨Ethereum Developers: you can now install your first AI Auditor in 1 minute - fully autonomous, available 24/7, with multiple sub-agent helpers. Open Source. FREE to use (with your AI model) and already finding vulnerabilities in smart contracts. Link below🫡
pashov tweet media
English
167
255
1.3K
148.6K
swft
swft@swftbb·
@Rasmic “final”, “actual-final”, “final-for-real-this-time”
English
0
0
0
104
Micky
Micky@Rasmic·
openai really needs to work on better naming i guess i'll be using extra high fast turbo
Micky tweet media
English
31
2
162
9.6K
swft
swft@swftbb·
this is a big thing with AI adoption that’ll be a differentiator for teams imo sometimes it should take a long time to get to a solution with implementation time going to 0, it’s worth it to spend more time on other areas of the process
TBPN@tbpn

.@kenburns on technology that seems to make your creative work faster: "There are things I knew would take two weeks, now they take two days, and things that took two days now take two hours, [etc.]." "And you think there's salvation in that. But there are as many traps, as many places of quicksand. So you just want to be sort of careful about how you approach it."

English
0
0
2
59
swft
swft@swftbb·
an openclaw agent to manage your openclaw agent
GIF
English
0
0
0
72