the dormant code

Reserved in 1997. Left empty for ~30 years.

402 Payment Required has been in the HTTP spec since the early web, marked "reserved for future use" and almost never implemented. It was the internet's promise to itself that one day the web would know how to charge for things — a promise left blank for a generation.

x402 is the open protocol (from Coinbase, now under neutral governance) that finally wires it up: a server answers a request with 402 and payment instructions, the client signs a stablecoin payment, and the same HTTP round-trip settles onchain — no accounts, no API keys, humans and AI agents alike, in about a second on Base.

Simple things make impossible things possible on Base.

a place in the timestamp

Not minted from a form. Minted from a response.

HTTPBASE20 didn't come from a launchpad button. It came from a request to an x402 endpoint that returned 402 Payment Required. The payment was signed, settled onchain on Base, and the 200 OK that came back carried a brand-new B20 token: the first ever born this way.

You can fork the code. You cannot fork the timestamp. HTTPBASE20 is the first B20 token whose origin story is an HTTP status code.

the public birth

No deploy button. A reply.

HTTPBASE20 wasn’t launched from a dashboard — it was summoned in the open, on X, for anyone to watch. @Theunsecretman fired an x402 call at a purpose-built endpoint wired to the B20 launchpad from cc0.company. @bankrbot caught the request, settled the payment onchain on Base, and replied with a freshly minted token.

You can fork the code. You cannot fork the thread. The whole genesis — request, 402, payment, mint — is public and permanent.

Three steps. No manual required.