AI-assisted software maintenance, bounty delivery, project funding, MRG rewards, and public proof-ledger verification.

Claim MRG Tokens | Main Repository | MergeOS Scan | Product Site

MergeOS is an AI-assisted operating system for software maintenance and bounty work. A customer can fund a project, MergeOS turns the work into scoped tasks, contributors claim eligible issues, pull requests are reviewed with evidence, and approved work is recorded in a public proof ledger.

The organization behind this profile, mergeos-bounties, hosts the public bounty intake, project code, claim workflow, and contributor-facing issues for the current MergeOS MVP.

All new bounty work must follow this workflow:

1. Open the Claim MRG Tokens issue #1.
2. Comment with the bounty issue you want to claim, your GitHub handle, and a short implementation plan.
3. Wait for maintainer confirmation before starting.
4. Create a focused branch or fork for the fix.
5. Open a pull request that links the bounty issue and your claim comment.
6. Include evidence in the pull request: screenshots, GIF, video, test notes, or another clear proof artifact.
7. Keep the PR open for maintainer review. Approved work receives the assigned MRG reward through the MergeOS review flow.

Do not open random one-off bounty issues without maintainer direction. New bug reports and bounty requests should start from the Claim MRG Tokens intake issue so the project has one clear public queue.

Every bounty PR must include:

• A clear description of the bug, feature, or integration completed.
• A link to the bounty issue.
• A link to the claim comment or a note that the maintainer assigned the work.
• Screenshots, GIF, video, or other visual proof when the work changes UI, payment flows, admin screens, ledger views, or user-facing behavior.
• Test notes listing the commands run, local/staging URL tested, and any sandbox account or mock provider used.
• Confirmation that secrets, production credentials, private customer data, and raw webhook secrets are not committed.

PRs without evidence are not ready for bounty review.

Always check the issue thread and Claim MRG Tokens queue before starting, because assignments can change.

MergeOS currently welcomes scoped work around:

• Payment flows, including PayPal Sandbox and crypto gateway test modes.
• Server webhook callbacks, signature verification, and idempotent payment state updates.
• Public proof ledger sanitization and explorer improvements.
• Admin review workflows for projects, tasks, SSL, payments, users, and ledger entries.
• GitHub issue import, bounty scoring, and PR evidence review.
• Frontend UX for customer funding, marketplace browsing, ledger logs, and contributor onboarding.
• Tests, deployment hardening, documentation, and operational reliability.

MRG is the internal MergeOS reward and proof token used for bounty accounting inside this project. Each eligible bounty issue lists its reward amount, acceptance criteria, evidence requirements, and review expectations.

MRG rewards are assigned by maintainers after claim approval and PR review. Do not assume a payout for unclaimed work, duplicate work, incomplete work, or PRs without evidence.

Clone the main repository:

git clone https://github.com/mergeos-bounties/mergeos.git
cd mergeos

Run the backend:

cd backend
go test ./...
go run ./cmd/mergeos

Run the public frontend:

cd frontend
npm install
npm run local

Run the admin workspace:

cd admin
npm install
npm run local

Run MergeOS Scan:

cd scan
npm install
npm run dev

Before opening a PR, run the relevant tests and builds for the area you touched.

Never commit:

• .env files with real credentials.
• PayPal production credentials.
• Crypto gateway production keys.
• Webhook signing secrets.
• SMTP passwords.
• Private customer data.
• Raw payment payloads containing sensitive data.

Use documented sandbox or test-mode configuration. If a gateway has no official sandbox, implement a deterministic mock provider that exercises the same server callback path.

Maintainers review bounty PRs for:

• Claimed work and issue linkage.
• Correct scope and clean implementation.
• Evidence quality.
• Test/build status.
• Security and secret hygiene.
• Public ledger sanitization.
• No duplicate reward minting.
• No hidden production credential usage.

Approved PRs are merged through the MergeOS review process and recorded through the platform ledger where applicable.

New contributor? Start with the public intake:

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

Comment there first, then build with evidence. That keeps the bounty queue fair, reviewable, and easy for everyone to follow.