REQUEST.EXE — claim your permanent number _□×

claim your permanent request number.

every wallet that calls the x402 endpoint gets the next number in line — #000001, #000002, … — recorded onchain-verifiable and yours forever. it can never be reassigned.

Your card reads the chain every time someone opens it, so the tier and balance it shows are always current — not a snapshot from the day you claimed.

tier	you hold
`402 Payment Required`	nothing yet
`200 OK`	any HTTPBASE20
`301 Moved Permanently`	0.10%+ of supply
`418 I'm a teapot`	1.00%+ of supply

Sell your bag and the card drops to 402. Buy back in and it climbs again. It tells the truth, which is the whole point.

CONNECT & CLAIM — do it here, from your wallet _□×

Connect a wallet and make the x402 call right here.

MetaMask, Coinbase Wallet, or any injected wallet on Base.

the endpoint

https://httpbase20.netlify.app/api/request

The same call the button above makes, if you would rather make it yourself. It answers 402, you pay, it returns your permanent number — and mints the pass if the number is 69 or lower. Older agents that only speak x402 v1 can add ?x402=1.

Rather have the agent do it? It pays from your Bankr wallet and gets the very same number. ask @bankrbot to make the call →

Runs in your browser with your wallet. The x402 payment settles on Base; the request number is recorded by the endpoint and the pass, if one is left, is minted to you within a minute. HTTPBASE20 never holds your funds.

THE 69 — the pass that comes with the number _□×

The first 69 request numbers also carry an NFT pass, minted to you automatically — and the pass is the access: it is what lets you clock in each week and earn a share of the HTTPBASE20 trading fees. Without one you can still have a number, but you earn nothing. There will never be a seventieth.

… reading the chain…

TOKEN ID = YOUR NUMBER

Request #8 is token 8. Forever. The pass carries your serial and the wallet that first claimed it.

IT REDRAWS ITSELF

The artwork is generated on every load from the current owner's balance. Tier changes, the NFT changes.

TRANSFERABLE

Sell it, buy one. Once the 69 are gone the only way in is from someone who already has one.

IT IS THE TICKET

Holding a pass is what lets you clock in for the weekly fee share. No pass, no share.

Past #69 you get the number and nothing else. The card still works, still shows your live tier, still sits on the wall forever — but there is no NFT attached to it and it does not earn the weekly fee share. We would rather you knew that before paying than after.

already sold out of your number?

Get your pass on OpenSea — once all 69 are claimed, the secondary market is the only way in. —

Contract —

CLOCK IN — the weekly fee share _□×

Every week a slice of the HTTPBASE20 trading fees is split between pass holders who showed up.

THIS WEEK

clocked in not clocked in

1

Clock in any time from Monday to Sunday, on your card page. One transaction, a couple of cents. You take part from the day you clock in — Monday earns seven days, Thursday earns four.

2

Every night your HTTPBASE20 balance is recorded. Your weight is the sum of those daily balances, so selling mid-week costs you the days after the sale, and buying on Sunday only buys one day.

3

On Monday the week's pool is published and a Claim button appears on your card with your amount on it. Unclaimed rewards stay yours — nothing expires for six months.

how the pool is divided

50% — EQUALLY, EACH DAY

The week's pool is cut into seven days. Half of each day's slice is shared equally between the wallets clocked in that day. One of 69 seats is worth something on its own, whatever the size of your bag.

50% — BY BALANCE, EACH DAY

The other half of each day's slice goes in proportion to your HTTPBASE20 that night. Holding more pays more, in a straight line, with no bonus curves to game.

Days you are not in are shared by the wallets that are. Clock in on Monday and you are in all seven cuts; clock in on Thursday and you are in four, and the three days before that go to the people who were there. It is the same arithmetic the payout runs — the board above shows your share moving as the week fills in.

Two conditions, both checked onchain when you clock in: you hold at least one pass, and at least 1,000,000 HTTPBASE20. Holding several passes on one wallet still counts as one seat — the weight comes from the tokens, not the passes.

The seat pays whoever holds it when the week closes. Sell or send the pass before Sunday midnight and that week's share goes with it, to the wallet that ends the week holding it. Without this a single pass could be walked from wallet to wallet, collecting a full equal share at every stop — so the rule is what keeps one pass worth one share.

where the pool comes from

HTTPBASE20 earns trading fees on every swap, paid in two assets. Of the project's share:

asset	to the weekly pool	the rest
`WETH`	70%	30% — treasury: gas, hosting, running the thing
`HTTPBASE20`	10%	90% — burned, as it always has been

The burn is not going anywhere: nine tenths of the token side still goes to the dead address every week, which benefits every holder whether they clock in or not. The pool is the other tenth, plus most of the WETH.

Rewards are not a promise of profit. The pool is 70% of whatever WETH the fees happen to produce that week — which can be a lot, very little, or nothing at all if nobody trades. The split above can be changed, and any change will be announced before it applies. HTTPBASE20 is a memecoin with no intrinsic value. Nothing here is financial advice.

Contract —

THE WALL — everyone who knocked on the 402 _□×

claimed request numbers

…

loading the wall…

Newest first, tiers read live from Base. PASS means the number carries an NFT; CARD means it is a number only. Full card at /r/<number>.