Lab / EXP_SPOUT_002

Experiment

Spout Product Feedback — reopen → submit

Completed archived · started 2026-09-16 · ended 2026-09-17

Why

Decision
SUBMITTED — access unlocked; balance-indexer bug blocked buy/borrow; report + public package still shipped.
Why now
Beta code arrived after EXP_SPOUT_001 kill (access gate). Kill reason cleared → reopen then submit.
Cost
TimeMoneyAttention
redeem + explore + report + public repo + human Earn submit$0released_after_submit

01What We Believed

Hypothesis
Once a beta passcode arrives, a structured Devnet teardown + public write-up can still close the Superteam product-feedback loop before the listing deadline.
Prediction
{
  "expected": "Submission accepted; strongest finding is first-party balance sync failure",
  "confidence": 0.6
}
Success criteria
beta redeem success
structured public report URL
Earn submission received
Action
Redeemed beta; connected Devnet wallet; funded via official faucets; documented chain vs in-app $0 balance bug; published structured report + public write-up; human Earn submit.

02What Reality Said

Result
{
  "status": "submitted_pending_review",
  "summary": "Earn submitted 2026-09-17. Package https://github.com/xbox002000/spout-beta-feedback-2026-09 · Devnet faucet showed 20 USDC + ~5.5 SOL on-chain while Spout UI stayed $0 · Market Closed · Earn tab coming soon.",
  "report": "https://github.com/xbox002000/spout-beta-feedback-2026-09/blob/main/REPORT.md",
  "public": "https://github.com/xbox002000/spout-beta-feedback-2026-09/blob/main/PUBLIC.md"
}
Economic outcome
pending_external

03What Changed

Learning
A killed access-gate bet can reopen when the gate clears. Genuine testing can still produce a high-severity product finding without a successful buy. Earn credits are finite — one credit per bounty submit.
Reality
Believed Spout was dead without a passcode → Reality code arrived → Changed REOPEN → SUBMITTED. Believed faucet failure → Reality chain funded, app indexer empty → Changed primary bug to balance sync.