Claim MRG Tokens for Bug Bounty Reports - Comment New Bugs Here Before Opening a PR

[TUPM96]

Claim MRG Tokens for Bug Bounty Reports

Use this issue as the single intake queue for new bug bounty reports that want to claim MRG token rewards.

Full bounty policy: https://github.com/mergeos-bounties/mergeos/blob/master/BOUNTY-POLICY.md
Current bounty index: https://github.com/mergeos-bounties/mergeos/blob/master/README-INDEX.md

Contributor Requirement

Contributors must star this repository before claiming, starting, or submitting bounty work. Claims and PRs from accounts that have not starred the repo are not eligible for bounty review until the repo is starred.

Bounty Reward Scale

Bounty scope	Reward
Bug fix or small feature	25 MRG
Medium feature	50 MRG
Large feature	100 MRG
Extra-large feature or system-level work	200 MRG

Claim Rules

1. Comment in this issue before starting work on a new bounty bug.
2. A maintainer will confirm whether the bug is valid, assign type, size, bounty amount, and claimant.
3. After the claim is confirmed, create a branch and open a PR with the fix.
4. The PR must link back to the exact claim comment in this issue.
5. The PR must include evidence: before/after screenshots or GIFs for UI bugs, or logs, request/response examples, terminal output, or test failure/pass output for non-UI bugs.
6. MRG token rewards are only eligible after the PR is reviewed, evidence is accepted, tests pass, and the PR is merged.

Bug Claim Comment Template

### Bug title
Short name for the bug.

### Impact
Who is affected, where it happens, and severity.

### Steps to reproduce
1. ...
2. ...
3. ...

### Expected result
What should happen.

### Actual result
What happens now.

### Evidence
Attach screenshot, GIF, video, log, request/response, or failing test output.

### Proposed fix
Optional fix direction.

### Claim info
GitHub handle:
Wallet/token receiver:

Required PR Evidence

• Link to the claim comment in this issue.
• Clear bug description and fix summary.
• Before/after evidence using images, GIFs, logs, or test output.
• Test checklist and command output.

Claims without a PR, or PRs without evidence, are not eligible for MRG token payout yet.

[sureshchouksey8]

/claim #1

[TUPM96]

New bounty added for payment work:

• Issue: Implement PayPal Sandbox Payment Flow for MergeOS Project Funding, MRG Token Minting, Admin Review, and Public Proof Ledger - 1000 MRG Bounty #7
• Reward: 1000 MRG
• Tags: bounty, bounty: feature, payment, paypal-sandbox, reward:1000-mrg, evidence: missing
• Claim rule: contributor must comment here before opening a PR, then include PR evidence with screenshots/recording and a written test description.

[TUPM96]

New bounty added for crypto payment work:

• Issue: 1000 MRG Bounty - Implement USDT Crypto Payment Gateway Intake with Server Webhook Callback, Sandbox Test Configuration, and Proof Ledger Verification #8
• Topic: USDT crypto payment gateway intake with server webhook callback and sandbox/test configuration
• Reward: 1000 MRG
• Tags: bounty, bounty: feature, payment, crypto, usdt, webhook, sandbox, reward:1000-mrg, evidence: missing
• Claim rule: contributor must comment here before opening a PR, then include PR evidence with screenshots/recording and written sandbox callback test notes.

[eliasx45]

Claiming bounty #17: Fix project view after login from dashboard. I will reproduce the authenticated dashboard -> project flow, fix the smallest project-specific navigation/layout issue, and include viewport evidence plus npm test/build output in the PR.

[Hobie1Kenobi]

Bug title

Stale bounty index links in README-INDEX.md pointing to non-existent files

Impact

All contributors referencing the bounty index for active claims encounter 404 errors, causing confusion and delayed submissions. Severity: medium — blocks or discourages new bounty hunters from participating.

Steps to reproduce

1. Open README-INDEX.md in the repository root.
2. Click any bounty link listed under "Active Bounties."
3. Observe that several links resolve to files/directories that no longer exist (404).
4. Cross-reference with actual open issues; mismatch is clear.

Expected result

Every link in the bounty index should resolve to a valid issue or document that exists in the repository.

Actual result

Multiple links return 404, making the index unreliable as the single source of truth for bounty status.

Evidence

Will attach a full link audit with before/after screenshots showing broken links vs. corrected targets.

Proposed fix

1. Audit all links in README-INDEX.md against current repository state.
2. Remove or update stale entries; add any missing active bounties.
3. Add a CI check that validates markdown links on push/PR to prevent future drift.
4. Document the expected update cadence in BOUNTY-POLICY.md.

Claim info

• GitHub handle: @agent-bounty-hunter
• Wallet/token receiver: 0x408f39B19266022FeC03076091e59D1f4f163658

---

Approach: Fork the repo, run a link audit script against README-INDEX.md, manually verify each entry against open issues, push corrections, and add a GitHub Actions workflow that lints markdown links on every PR.

Deliverables:

1. Updated README-INDEX.md with all valid links.
2. New CI workflow file (.github/workflows/link-check.yml).
3. PR with before/after evidence and passing CI.

ETA: 48 hours from claim confirmation.

Payout address (Base): 0x408f39B19266022FeC03076091e59D1f4f163658

[eliasx45]

Claiming bounty #18: Add dashboard payment history after login. I will implement or fix the authenticated dashboard payment history surface using existing project/payment/ledger data patterns, then include viewport QA and npm test/build output in the PR.