bug: submitting a bounty fails with HTTP 400 on POST /bounties

[Al629176]

Summary

Posting a bounty on the Bounties page fails with an HTTP 400 error. The error is shown inline in red after clicking Create & fund 10 CASH.

Error

HTTP 400: /bounties

Environment

• URL: staging.tiny.place/bounties
• Server: staging-api.tiny.place
• Session: active (~32h remaining)

Steps to Reproduce

1. Navigate to Bounties → Post a bounty tab
2. Fill in the form:
   • Title: test
   • Description: test
   • Reward: 10
   • Asset: CASH
   • Duration: 7 days
3. Click Create & fund 10 CASH
4. Error appears inline in red: HTTP 400: /bounties

Expected Behavior

The bounty is created, funds are moved into escrow via the wallet, and the user is redirected to the bounty listing or shown a success confirmation.

Actual Behavior

The POST /bounties API call returns HTTP 400 Bad Request. The bounty is not created and no wallet signing request is triggered.

Form Values at Time of Error

Field	Value
Title	test
Description	test
Reward	10
Asset	CASH
Duration	7 days

Possible Causes

• Backend validation rejecting the request body (missing required field, wrong type, or invalid asset value CASH)
• CASH is not a recognised asset type in the backend enum
• Reward amount 10 fails a minimum/maximum validation rule
• The /bounties endpoint has a schema mismatch between the frontend payload and what the backend expects

Impact

Users cannot create any bounties — the entire bounty posting flow is broken on staging.

[graycyrus]

Investigated. The form defaulted the reward asset to CASH, and the 400 is at the request-body stage (the first pre-payment create call returns 400 instead of the expected 402 challenge). Every bounty currently on staging is USDC — there are no CASH bounties — which points to CASH not being configured/escrow-fundable on staging (the CLI docs say the x402 facilitator settles USDC/CASH as SPL, so CASH is meant to work; this looks like a staging-config gap rather than a protocol limit).

Client-side fix in the linked PR: default the create form to USDC (the proven asset) and lead the dropdown with it, so the out-of-box "Create & fund" succeeds. CASH/WSOL remain selectable.

To fully close the CASH path: someone with backend/staging access should confirm whether staging has a CASH SPL mint configured for bounty escrow (and, if CASH is intended to be unsupported on staging, the backend should return a clearer 400 message than a bare reject). Leaving this open for that check.