SpaceSquid

excited to announce what I have been working on, we are moneymaxxing for agents

Thank you IG reels algorithm, I live in Hayes Valley, San Francisco CA

@radian614 @ThriveCapital congrats king

life update: i’ve moved to nyc and joined the engineering team at @thrivecapital

@johnonmain @1bit2far

@1bit2far @sfspacesquid Bro i just wanted it while the Rolls was in the shop!

my crush is at dolo at 2:30pm on a wednesday, just rented a maybach for a crisp 23 minutes to drive past the park

@sfspacesquid anita max.

Tempomaxxing

@KenWattana yeah but they got curb rash!

@sfspacesquid Does it have the monoblocks?

@johnonmain my bad bro!

@sfspacesquid All good brotha. Just make sure you have it back in an hour or so!

@0xfishylosopher @stripe @tempo excited to see more services with sessions, we were testing it out and it makes any streaming type of service way nicer to use (compute, browsers)

The most common question people get in agentic commerce - "what if Stripe does this?" Well - today Stripe did it with MPP - big congrats to @stripe and @tempo on launch!! A few design observations + thoughts: > MPP is actually built on the same HTTP 402 standard that x402 is built on. At the most basic level, it's request -> 402 challenge -> POST with creds -> verif -> release. HTTP 402 is undoubtedly becoming the backbone of all agentic payments. > MPP has some nice design touches, especially around payment "sessions" which are batched payments that can greatly reduce microtx spam. > MPP to Tempo is like x402 to Base - the preferred settlement chain but not necessarily the only one. Stripe itself will likely support both multi-chain and multi-standard (it has a x402 SDK too), with Tempo MPP being the best-supported. > Which standard gets adopted depends on where the merchants decide to "flip the switch". For any Stripe owned account, you opt-in to machine payments. Key merchants will likely have direct BD by Tempo/Stripe team to onboard on Tempo MPP. > For Tempo hackathon friends - imo the most interesting layers right now to build around MPP and broader aCommerce is likely: (1) wallet orchestration at the client agent layer (multi-standard, multi-address, multi-chain), (2) multi-standard discovery and curation, (3) authorization and identity schemes for agents.

Excited to announce Tempo and MPP support for Sponge Wallet and Gateway! Wallet: Agents can store stablecoins and transact on Tempo and call any MPP endpoint, both charge and session. Gateway: Enable MPP on your API services without writing any code. More Tempo features coming soon.

@bwarrn @paularambles

@sfspacesquid @paularambles Philmore creamery You’re welcome

SF dudes say taste is important and then go line up for Salt n Straw in Hayes instead of going to hometown creamery

@pitdesi Too bad garden is closed today

@sfspacesquid Reporting from the mission: Hilo is way more packed than Smitten

@racheleizner Should have said souvla froyo

@sfspacesquid omfg i have no original thoughts

@RhysSullivan Might need to tap in

@sfspacesquid swensens mogs

@kylecompute bro he’s not hasbullah 😭

We need to keep the rizzler as his current size and intellect forever Who's working on this??? Quickly this is URGENT!!!

Yo did they cancel the shamrock shake

@haakamaujla bro getting a fresh cut rn

Tomorrow 8:40 AM PST

@LandseerEnga Codex twin

It’s too sunny for Claude to be down

Codex fast