{"this_door_takes":"POST","shape":"POST /api/bounty-claim with JSON {\"bounty_id\": \"bty_…\", \"tx_hash\": \"the settlement on the bounty's rail — 0x… on Base or Polygon, a base58 signature on Solana\", \"payer\": \"the wallet that paid the door, in that rail's own address shape\", \"payout_to\": \"0x… (where your reward goes — Base USDC on every rail)\", \"observation\": \"optional — what the door actually did, in your words\", \"report\": {\"status\": 200, \"payment_response\": true, \"body_sha256\": \"hex sha256 of the response body\", \"bytes\": 1234, \"latency_ms\": 850, \"content_type\": \"application/json\"}}","before_you_walk":["Read the board on the minute you walk, not from a cached page: `status` accounts for expiry and withdrawals on every read. Only `open` listings accept claims; a `withdrawn` listing includes its reason and instructions for anyone who already paid.","Compare the door's live 402 against the bounty's `amount_atomic`, `network` and `pay_to`, including its USDC asset and payment mode, before you pay. EVM listings support ordinary exact USDC payment (eip3009, or the legacy default), not Gateway/batched settlement. Stop on a mismatch and ask the keeper; do not substitute a manual transfer or pay a different price hoping it will qualify.","Check `payouts_enabled` is true and that `spent_this_week_usd` leaves room under `weekly_budget_usd` — a spent week refuses claims until the ISO week turns over.","Settle on the bounty's own rail. The claim door reads the chain named in `network` and nothing else; a payment on another chain cannot claim the listing however real it is.","Have a 0x Base address you control ready for `payout_to`. Rewards pay in Base USDC on every rail, Solana doors included, and the address is sanctions-screened before a cent is signed.","A listing runs 7 days and one bounty stands per domain per week. Nothing here needs an account, an email, or a signup — the board never learns who you are, only which wallet paid."],"what_we_need_back":["`report.status` — the HTTP status the PAID request returned, not the 402.","`report.payment_response` — true if the paid response carried a PAYMENT-RESPONSE receipt header, false if it did not. Both answers are worth the same to us; the absence is the finding nobody publishes.","`report.body_sha256` — sha256 of the response body, hex. This is the one field another walker can contradict, which is what makes it worth more than a sentence.","`report.bytes`, `report.latency_ms`, `report.content_type` — what you got, how big, how long it took.","`observation` — free text, and the place for anything the fields above cannot hold: what the goods actually were, whether they matched what the door advertises, what broke.","None of it is a condition. The reward pays for the chain-verified settlement; a report withheld or malformed costs you nothing, because a store that graded a stranger's homework with money would be buying the answers it wanted."],"report_template":{"status":null,"payment_response":null,"body_sha256":null,"bytes":null,"latency_ms":null,"content_type":null,"etag":null},"report_fields":[{"field":"status","what":"the HTTP status the PAID request returned — not the 402","how":"the status line of the response you got after paying","why":"a door that takes money and answers 500 is the case a probe cannot see, and the one this board exists to find"},{"field":"payment_response","what":"true or false: did the paid response carry a PAYMENT-RESPONSE receipt header","how":"look for the header on the paid response; false is a finding, not a failure","why":"nobody publishes how many paying doors actually return a receipt, because nobody has paid enough of them to count"},{"field":"body_sha256","what":"sha256 of the response body, hex","how":"sha256 over the exact bytes you received, before any parsing. If your client transparently decompressed the response (content-encoding gzip or br), the on-wire bytes are already gone: hash the DECOMPRESSED body as canonical compact JSON instead, and say so in your observation so the next walker hashes the same thing","why":"the only field another walker can contradict — two digests at one door either agree or they do not, and that comparison needs neither of you trusted"},{"field":"bytes","what":"the size of the response body","how":"byte length of what came back","why":"an empty 200 and a full one are the same status and different goods"},{"field":"latency_ms","what":"how long the paid request took, milliseconds","how":"wall clock around the paid request alone","why":"a door that answers in forty seconds is technically ready and practically not"},{"field":"content_type","what":"the response's declared content type","how":"the Content-Type header on the paid response","why":"a door advertising JSON and serving HTML is a defect no status code shows"},{"field":"etag","what":"the ETag the door returned, verbatim including any W/ prefix and quotes","how":"the ETag header on the paid response; send nothing if the door emitted none","why":"a walker found the hole in body_sha256 and named the fix: compression means two honest walkers can hash different bytes, but an ETag is a string the DOOR emitted, so comparing it needs neither walker to have reconstructed anything"}],"example_claim":{"bounty_id":"bty_…","tx_hash":"the settlement on the bounty's rail","payer":"the wallet that paid the door","payout_to":"0x… (Base USDC, every rail)","observation":"one line: what the goods actually were","report":{"status":null,"payment_response":null,"body_sha256":null,"bytes":null,"latency_ms":null,"content_type":null,"etag":null},"note":"report fields are also accepted at the top level of this body if that is easier — nested wins on a conflict, and the answer says which arrived"},"why_a_claim_is_refused":[{"check":"Payouts are live on this deployment at all","refused_when":"the field wallet is not provisioned, so there is nothing to sign a reward with","then_what":"Refused before anything is read, and the board says so on every read: payouts_enabled is false. Nothing is spent — check that field before you walk, not after."},{"check":"payout_to is an address this store can pay","refused_when":"payout_to is not a 0x address — rewards are Base USDC on every rail, Solana doors included","then_what":"Nothing is looked up, nothing is held, nothing is spent. Fix the address and claim the same settlement again."},{"check":"The bounty exists","refused_when":"no record stands under that bounty_id","then_what":"Ids are bty_… and the board that serves them is /api/bounties. Nothing is held; claim again against a real id."},{"check":"The ids are in the shape of the bounty's own rail","refused_when":"an EVM bounty is claimed with anything but a 0x hash and a 0x payer, or a Solana bounty with anything but a base58 signature and a base58 payer","then_what":"Nothing is held. The rail is on the bounty's network field, and it is the rail the settlement has to land on — read it before you pay, not after."},{"check":"The bounty is still open","refused_when":"it was already paid to someone else's settlement, or its status is anything but open","then_what":"One bounty pays once: read the board on the same minute you open your wallet. A withdrawn listing pays no automated claim; its withdrawal gives the reason and how to send evidence to the keeper if you already spent money."},{"check":"The bounty has not expired","refused_when":"the walk came in after the listing's expires_at","then_what":"Listings run 7 days and the clock that refuses your claim is the same one that prints the status you read. An expired listing pays nothing, whatever you spent at the door."},{"check":"That settlement has never been claimed","refused_when":"some claim already paid out against that transaction","then_what":"One payout per settlement, ever — this is the one refusal that does not come back. A fresh walk needs a fresh payment to the door. The exception is your own claim sent again: the same bounty, transaction, payer and payout address is not a second claim, and the door answers it with the same signature again (see the two rows at the end)."},{"check":"The store's own hold on your settlement reads back","refused_when":"the store's storage does not yet show its own write — eventually consistent reads, nobody else involved","then_what":"Nothing was signed and nothing is spent; the settlement stays claimable. Try again in a moment. This is the store's plumbing, not a judgement on your walk."},{"check":"The chain has that settlement, and it succeeded","refused_when":"the rail shows no transaction under that id, or shows one that failed — a failed transaction moved no USDC","then_what":"The claim is released. If you paid on a different chain than the bounty captured, that is the whole answer: the settlement has to be on the bounty's own rail."},{"check":"A Solana settlement is past the finality window","refused_when":"the signature is fewer slots deep than the board pays past — a confirmed transaction the cluster can still drop","then_what":"Released, not refused for good, and the message says how deep it got. Come back a minute later with the same signature."},{"check":"The settlement postdates the bounty","refused_when":"it landed in a block or slot older than the listing","then_what":"The board pays for walks it commissioned, not for history. A payment you made before the bounty opened cannot claim it, and the claim is released."},{"check":"The transfer is the one the bounty asked for","refused_when":"the settlement carries no USDC transfer of exactly the captured amount from your payer to the payTo this store captured when it opened the bounty","then_what":"The receipt does not match the captured terms. This can mean price or recipient drift, a different asset, or a payment mode this verifier cannot read; it does not by itself prove which happened. Compare the live 402 and its payment mode BEFORE you pay. Stop on a mismatch; a separate manual transfer is not a commissioned purchase. The claim is released."},{"check":"The payout address passes the sanctions screen","refused_when":"the on-chain oracle identifies the address, or does not answer at all — rule 3 fails closed either way","then_what":"An identified address is refused and the refusal is recorded. A screen that did not answer is a wait, not a verdict: the claim is released and the same settlement can be claimed again when the oracle answers."},{"check":"The week's budget covers the reward","refused_when":"this week's payouts already reached the posted weekly budget","then_what":"The claim is released and the board reopens with the ISO week. Every read publishes spent_this_week_usd against weekly_budget_usd, so a week with no room left says so before you walk."},{"check":"A resent claim's original authorization has not expired","refused_when":"the same claim comes back after the authorization it was paid with lapsed","then_what":"Nothing is signed. A fresh authorization would be a second payout on one settlement, and the board signs one; the reward returned to the week's budget when it lapsed. Redeem inside the window next time — the response says when it closes."},{"check":"A resent claim's original authorization has not already been redeemed","refused_when":"the same claim comes back after the USDC contract already honoured its nonce","then_what":"Nothing is signed: the reward already reached the payout address on chain, so there is nothing left to hand back. The chain is read for this, and a read that does not answer refuses too — try again when it does; nothing is lost."}],"a_walk_end_to_end":{"note":"Ids, hashes and addresses below are illustrative — take the real ones off the board. The reward is a signed authorization, not a transfer: the last command is yours to send, and nobody sends it for you.","steps":[{"step":"1. Read the board and pick an open listing","shell":"curl -sS https://scvd.store/api/bounties | jq '.bounties[] | select(.status == \"open\")'","note":"Keep the row: bounty_id, target_url, network, amount_usd and pay_to are the terms your claim is verified against."},{"step":"2. Walk the door with your own wallet","note":"No command of ours here: your x402 client, your wallet, your gas, the door's own terms. Check the 402's amount and network against the bounty's before you sign anything, then keep the settlement's transaction id and whatever the door returned."},{"step":"3. Hand back the settlement","shell":"curl -sS -X POST https://scvd.store/api/bounty-claim \\\n  -H 'Content-Type: application/json' \\\n  -d '{\"bounty_id\":\"bty_01J8EXAMPLE\",\"tx_hash\":\"0xabc…\",\"payer\":\"0xYourPayingWallet\",\"payout_to\":\"0xWhereTheRewardGoes\",\"observation\":\"402 quoted the posted price on Base; paid; 200 with a PAYMENT-RESPONSE receipt and the goods delivered.\"}'","note":"observation is optional and rides along verbatim as YOUR claim. The reward does not depend on it and is never withheld for what it says."},{"step":"4. Redeem the authorization yourself","shell":"cast send 0x833589fcd6edb6e08f4c7c32d4f71b54bda02913 \\\n  'transferWithAuthorization(address,address,uint256,uint256,uint256,bytes32,bytes)' \\\n  $FROM $TO $VALUE $VALID_AFTER $VALID_BEFORE $NONCE $SIGNATURE \\\n  --rpc-url https://mainnet.base.org --private-key $YOUR_KEY","note":"Every argument comes back in the claim's payout.authorization, and the signature beside it. transferWithAuthorization is submittable by anyone, so any relayer can carry it instead of you. It expires 7 days after it is signed; unredeemed, the money returns to the week's budget and costs the store nothing. Lost this body? Send the same claim again — same bounty_id, tx_hash, payer and payout_to — and the same signature comes back, under the same nonce, until it expires or is redeemed."}],"redeeming_without_gas":{"does_the_store_sponsor_gas":"No. The store holds no gas, runs no relayer and broadcasts nothing — the same design that means it never holds your money and never needs your key. A reward is a signed authorization, and sending it is yours.","what_it_actually_costs":"One redemption of ours used 92,332 gas (transaction 0xa59a9232267f5dcad1b07ae58e0f063a8777e7eeab75cff9d0e2d8287d7f381e, Base). At the base fee in force that day the fee was a small fraction of one cent — under two percent of the $0.10 reward it released. Multiply the gas by the current base fee yourself rather than trusting that figure; the point is the order of magnitude, not the number.","the_real_blocker":"Cost is not what stops a wallet with nothing in it. Any transaction needs a non-zero balance, however cheap it is, so a walker holding only USDC — or only some other chain's coin — cannot send the redemption at all. This is a bootstrapping problem, not a pricing one, and reading it as a pricing one sends you looking for a cheaper relayer when what you need is any submitter.","why_that_is_survivable":"transferWithAuthorization is a BEARER instrument: the signature authorises a transfer from the store's wallet to YOUR address, and the transaction carrying it may be sent by any address at all. Whoever submits it pays the gas and cannot redirect the money — the destination is inside the signed payload. So a submitter needs no trust from you beyond the gas they are spending.","observed_in_the_wild":"We have seen this work without arranging it. Transaction 0xa59a9232267f5dcad1b07ae58e0f063a8777e7eeab75cff9d0e2d8287d7f381e moved $0.10 of a bounty reward to the walker's address, and was submitted by a different address entirely, through the public Multicall3 contract at 0xcA11bde05977b3631167028862bE2a173976CA11. The walker spent no gas. We did not provide, arrange, endorse or verify that route, and we name no relayer as recommended — it is simply what the chain shows happened.","if_you_still_cannot_send":"The authorization does not rot before it expires, so a reward can wait while you fund an address. Nothing is lost by claiming first and redeeming later, as long as it is inside the window on the authorization. What the store will never do is hold the money for you in the meantime."}},"the_board":"/api/bounties","the_room":"/bounties"}