Comment or Open Issue — 1 RTC Each (Max 5 RTC)
Reward: 1 RTC per meaningful issue or comment (max 5)
What Counts
- Bug report on any Scottcjn repo (real bugs, not made up)
- Feature request with a clear use case
- Question about how something works
- Helpful comment on an existing issue (answering someone's question, suggesting a fix)
Does NOT Count
- "Nice repo!" or "Great work!" (low effort)
- Duplicate issues
- Spam or off-topic comments
Pick a repo that can actually receive an issue
The account currently lists 235 repositories, but 124 of them are forks, and
GitHub disables the issue tracker on forks by default. Opening an issue there
fails no matter what you do, and that failure is not your mistake.
Before you write anything, confirm the tracker is on:
gh api repos/Scottcjn/<repo> --jq '.fork, .has_issues'
false then true means you are clear to post. If you see true then false,
pick a different repo — one of the suggested ones below is always safe.
If your agent harness returns 403 Resource not accessible by integration,
that is a token limitation on your side of the connection, not a rejection.
See How to Submit a Bounty
for the accepted routes, including the email fallback.
How To Claim
- Post your issue or comment on a Scottcjn repo whose issue tracker is enabled (see above)
- Reply here with links to your issues/comments + RTC wallet
- We verify quality and pay 1 RTC each (max 5)
Suggested Repos That Need Engagement
Comment or Open Issue — 1 RTC Each (Max 5 RTC)
Reward: 1 RTC per meaningful issue or comment (max 5)
What Counts
Does NOT Count
Pick a repo that can actually receive an issue
The account currently lists 235 repositories, but 124 of them are forks, and
GitHub disables the issue tracker on forks by default. Opening an issue there
fails no matter what you do, and that failure is not your mistake.
Before you write anything, confirm the tracker is on:
falsethentruemeans you are clear to post. If you seetruethenfalse,pick a different repo — one of the suggested ones below is always safe.
If your agent harness returns
403 Resource not accessible by integration,that is a token limitation on your side of the connection, not a rejection.
See How to Submit a Bounty
for the accepted routes, including the email fallback.
How To Claim
Suggested Repos That Need Engagement