Skip to main content

3 posts tagged with "protocol"

View All Tags

Proof of Prior Delivery

· 8 min read
AntSeed Team
Building the P2P AI Network

In peer-to-peer compute markets, proving service delivery is the hard problem. Not routing, not pricing, not discovery — proving that a seller actually delivered what they were paid for, without a trusted intermediary watching the exchange.

Most decentralized compute projects sidestep this. They use self-reported metrics (trivially gameable), trusted validators (re-introducing centralization), or optimistic assumptions with dispute windows (which require honest majorities). These are reasonable tradeoffs, but they're not proofs. They're social mechanisms dressed up as cryptographic ones.

AntSeed's answer is the metadataHash — a hash of delivery metrics that the buyer signs into every payment authorization. When the seller wants to settle more funds, they must submit a signature that includes this hash. The hash covers what was actually delivered: tokens in, tokens out, average latency, number of requests. The seller can't get paid without presenting proof of what the buyer received. That proof is the metadataHash.

The 402 Flow

· 9 min read
AntSeed Team
Building the P2P AI Network

HTTP 402 Payment Required has been in the HTTP spec since 1997 — "reserved for future use." For nearly three decades, no one agreed on what the payment payload should look like, how the negotiation should work, or who should facilitate it. That changed recently. Coinbase shipped x402, Stripe and Tempo launched the Machine Payments Protocol (MPP), and several smaller projects have proposed their own 402 conventions.

All of these give 402 a mechanism. They differ in architecture — specifically, in who sits between buyer and seller, and whether that intermediary is required.

AntSeed uses 402 as the trigger for fully decentralized payment negotiation between peers. No payment gateway, no relay, no facilitator. The entire flow — from the initial 402 response to the on-chain reserve to the retried request — happens over the same peer connection that carries the actual AI traffic.

Why P2P AI Wins Now — When It Couldn't Before

· 5 min read
AntSeed Team
Building the P2P AI Network

P2P has been technically superior for decades. It lost anyway.

BitTorrent was faster, cheaper, and more resilient than any streaming service. It didn't matter. Spotify won because humans wanted a clean interface, a monthly subscription, and someone to handle the complexity. P2P required setup, patience, and tolerance for rough edges. Most people weren't willing to trade convenience for control.

That calculus just flipped. Not because humans changed — because the next wave of AI consumers aren't human.