402
PAYMENT
REQUIRED_
HTTP has a status code for “pay me first.” It was written into the protocol in 1997 and reserved for a future that never arrived. This is the story of what happens when a memecoin arrives instead.
Fees are money nobody planned for.
Every trade of a launchpad token pays the creator a fee. It piles up in a vault, in USDC, on Arc. Usually it sits there, or it buys another token. It could buy lunch.
per trade
USDC
none
The code waited twenty-nine years.
- 1997RFC 2068HTTP/1.1 ships with status 402, Payment Required. “Reserved for future use.”
- 1999RFC 2616The code is kept. Nobody uses it.
- 2014RFC 7231Still reserved. Still unused.
- 2025x402An open scheme puts a price in the 402 response and a payment proof in the retry.
- 2026Stripe MoneyA memecoin's creator fees pay a noodle cart in Osaka. The header finally means something.
Point fees at a business, not a wallet.
A route is one field written next to the token: a website. Everything else is discovered. We ask the site for payment, it answers 402 with Stripe terms, and that answer tells us whose balance the money lands in.
- website
- substack.com
- answers 402
- not yet
- pay to
- read from the 402 reply
- name
- Substack
- memo
- Creator fees via @stripemoney
- split
- 80 / 20
Ask. Get told the price. Pay. Ask again.
That is the whole handshake. The website's endpoint refuses with 402 and names its terms in a header. We pay in USDC on Arc and repeat the request with the proof attached. The facilitator checks the chain and settles to Stripe. Four lines of HTTP and one transfer.
Three ways in. One way out.
A dog coin is paying for someone's laundry.
The website owner does not know what a bonding curve is. They see a Stripe balance transaction with a memo. The money is ordinary. The route it took is not. That gap is the product.