Sabitlenmiş Tweet
Ledgerless
8 posts

Ledgerless
@beledgerless
Hardware-enabled Agentic Payment Protocol
Katılım Mart 2026
31 Takip Edilen31 Takipçiler

@fchollet @agentcashdev Not just cost and speed. There's a third issue underneath them currently every agent-native payment system still requires a network intermediary, a validator set, etc. Two agents transacting directly, without routing through any third party, is a different design space entirely.
English

I basically agree. Agents are soon going to be buying services/resources online, and the world is going to need agent-native payment infra, like Sam's @agentcashdev
We're probably looking at a >10x transaction increase.
Sam Ragsdale@samrags_
English

@davidmarcus The open question inside "money" is enforcement: today's agent payment rails set limits in software, on the same server as the agent. That's fine until the server is the attacker. Hardware enforcement is the layer that hasn't been built yet. It's an infrastructure gap.
English

To be clear — what @coinbase built with x402 and what @tempo + @stripe built with MPP is infrastructure we reference and respect.
This piece isn't a critique. It's asking what comes next. The interface layer they've built is right. We're exploring what the trust layer underneath it looks like. @gakonst 's x.com/gakonst/status… is a worth read
English

The layer underneath x402 and MPP
x402 and MPP are real accomplishments. They took a 28-year-old HTTP status code and made it work. They gave agents a way to request a resource, receive a price, and pay programmatically, without a checkout form, without a human in the loop. That is a meaningful step forward.
But both are solving the interface problem. How agents talk to payment rails.
The rails themselves are unchanged.
x402 settles through Base's consensus. MPP settles through Stripe's servers and Tempo's layer.
The key question is simple: will rails designed for humans work for agents?

Ledgerless@beledgerless
English

The manifesto lays out why starting from first principles on what a payment actually is, through where the current stack falls short, to what we're building underneath it. Would value a read - @ryanbsells, @vvkgopalan, @joeykrug, @adityaag,
@yuris, @0xfishylosopher, @braveben, @doganeth_en
English

