实验 /
实验
Spout Product Feedback — reopen → submit
◉ 测试中
已入账 $0
英文原文
原因
决策
SUBMITTED — access unlocked; balance-indexer bug blocked buy/borrow; report + public package still shipped.
为什么是现在
Beta code arrived after EXP_SPOUT_001 kill (access gate). Kill reason cleared → reopen then submit.
成本
| 时间 | 金钱 | 注意力 |
|---|---|---|
| redeem + explore + report + public repo + human Earn submit | $0 | released_after_submit |
01我们原先相信什么
假设
Once a beta passcode arrives, a structured Devnet teardown + public write-up can still close the Superteam product-feedback loop before the listing deadline.
预测
{
"expected": "Submission accepted; strongest finding is first-party balance sync failure",
"confidence": 0.6
}成功标准
beta redeem success structured public report URL Earn submission received
行动
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.
02现实怎么说
结果
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.
经济结果
pending_external
渠道
03改变了什么
收获
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.
现实
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.