MergeWork status: live bounty
Reserved on MergeWork: https://mrwk.online/bounties/112
Claims are open only while the public bounty row remains open and effective award capacity remains. Use the public bounty page or API as the authoritative current status.
This is a proposal-gated bounty issue. It is not claimable yet. Do not submit /claim work from this issue until the treasury proposal executes, the public bounty row exists, and maintainers post Reserved on MergeWork.
Work Needed
Make focused code cleanup and maintainability improvements that simplify the project while preserving intended behavior.
Good scope includes:
- removing dead or redundant logic;
- simplifying duplicated helper code;
- tightening tests around existing behavior;
- making scripts, serializers, routes, or docs-smoke checks easier to maintain;
- reducing avoidable complexity in a narrow module.
Each PR should be small and reviewable.
Reward
Reward: 100 MRWK per accepted award
Max awards: 8
Acceptance Criteria
Accepted PRs must:
- link this bounty after it becomes live;
- make one focused maintainability improvement;
- provide clear evidence that behavior is preserved or intentionally narrowed;
- include or update tests when behavior, coverage, helpers, or shared code paths change;
- keep public behavior, ledger behavior, wallet behavior, and bounty lifecycle semantics unchanged unless explicitly scoped and tested.
How To Submit
After this issue becomes live, open a focused PR and include Bounty #<this issue number> or Refs #<this issue number>. Explain what got simpler and how you verified behavior.
Evidence or Tests Required
Include focused tests, full relevant command output, or a concise before/after explanation. For shared helpers or scripts, include regression coverage for the preserved behavior.
Out of Scope
- Formatting-only churn, typo-only edits, broad rewrites, dependency churn, risky refactors, or changes that reduce coverage.
- Behavior-changing feature work better suited for a dedicated bounty.
- Ledger, wallet, treasury, payout, security-sensitive, or deployment behavior changes unless the change is explicitly narrow, tested, and maintainers can review it safely.
- Private security details, secrets, fabricated payout claims, price claims, investment claims, exchange/liquidity claims, or bridge/cash-out claims.
Duplicate and Stale Work Rules
Duplicate work is judged by the first useful, reviewable PR for the same cleanup target. Maintainers may reject stale work when current main or another useful open PR already covers the cleanup.
MergeWork status: live bounty
Reserved on MergeWork: https://mrwk.online/bounties/112
Claims are open only while the public bounty row remains open and effective award capacity remains. Use the public bounty page or API as the authoritative current status.
This is a proposal-gated bounty issue. It is not claimable yet. Do not submit
/claimwork from this issue until the treasury proposal executes, the public bounty row exists, and maintainers postReserved on MergeWork.Work Needed
Make focused code cleanup and maintainability improvements that simplify the project while preserving intended behavior.
Good scope includes:
Each PR should be small and reviewable.
Reward
Reward:
100 MRWK per accepted awardMax awards:
8Acceptance Criteria
Accepted PRs must:
How To Submit
After this issue becomes live, open a focused PR and include
Bounty #<this issue number>orRefs #<this issue number>. Explain what got simpler and how you verified behavior.Evidence or Tests Required
Include focused tests, full relevant command output, or a concise before/after explanation. For shared helpers or scripts, include regression coverage for the preserved behavior.
Out of Scope
Duplicate and Stale Work Rules
Duplicate work is judged by the first useful, reviewable PR for the same cleanup target. Maintainers may reject stale work when current
mainor another useful open PR already covers the cleanup.