Contribute to Calimero Network and earn rewards
Join our
Calimero is on a mission to become a truly community-led project, and
we're inviting developers from everywhere to contribute. Through our
bounty program, you can pick an open task, submit a pull request, and
get rewarded for your work. Every bounty is clearly listed with a
status and reward, so you always know what’s available. Whether it’s
fixing bugs, adding features, or improving documentation, your
contributions help shape the future of Calimero—and we make sure your
efforts are recognized.
Join our
Developer Bounty Program
Claim a bounty
Explore Open Bounties
- Browse bounties marked as “Up for grabs” and choose one you’d like to work on.
Express Interest
- Click on the bounty and comment on the GitHub issue indicating that you’d like to claim it.
Get Assigned
- Once you’re officially assigned to the issue, you can begin working on it.
Land a PR for the bounty
When your work is ready, open a pull request (PR) in the appropriate repository.
Be sure to:
- Link the relevant issue in the PR description.
- If the work is still in progress and you’d like early feedback, feel free to request a preliminary review from the team.
- If you get any comments on your PR, don't forget to re-request the PR review once the changes are done.
Get Rewarded
Once your PR is merged, you’ll be eligible for the associated bounty reward. Our DevRel team will reach out via Discord or GitHub to coordinate the payout.
We appreciate your contribution — every improvement helps the community grow.
If you enjoyed the bounty process, explore more opportunities and keep the momentum going!.
First time contributing to Calimero?
We recommend starting with issues labeled “good first issue” for a smoother onboarding experience.
NOTE: You can claim up to 3 open issues at a time.
Bounties
Title  | Reward | Status | Link |
|---|---|---|---|
| Implement meroctl devnet command | 250 USDC | In Progress (Claimed) | View on GitHub |
| Improve generation of comments from e2e tests | 250 USDC | In Progress (Claimed) | View on GitHub |
| Clean up credentials parsing from config | 50 USDC | In Progress (Claimed) good first issue | View on GitHub |
| Add ability to list aliases | 50 USDC | In Progress (Claimed) good first issue | View on GitHub |
| Proposals default limit to 1 | 250 USDC | In Progress (Claimed) | View on GitHub |
| CLI trunk versioning | 250 USDC | In Progress (Claimed) good first issue | View on GitHub |
| Expose proposal management to the CLIs | 250 USDC | Up for Grabs good first issue | View on GitHub |
| `merod config` revamp | 250 USDC | Up for Grabs good first issue | View on GitHub |
| `meroctl` should be able to connect remotely | 250 USDC | In Progress (Claimed) good first issue | View on GitHub |
| Document external APIs in calimero-sdk | 50 USDC | Up for Grabs | View on GitHub |
| Newly generated identities should be stored temporally | 100 USDC | In Progress (Claimed) good first issue | View on GitHub |
| meroctl and merod new version check | 50 USDC | In Progress (Claimed) | View on GitHub |
| Do not send private keys over the wire ever | 250 USDC | In Progress (Claimed) | View on GitHub |
| Application Registry | TBD | Up for Grabs | View on GitHub |
| e2e tests for Calimero SDK and node compatibility | 500 USDC | Up for Grabs | View on GitHub |
| User shall be able to invite other users to context | 250 USDC | In Progress (Claimed) | View on GitHub |
| Pull out `rocksdb` from `calimero_store` | 100 USDC | In Progress (Claimed) | View on GitHub |
| Tracking issue for schema generation | TBD | Up for Grabs | View on GitHub |
| Avoid all forms of blocking IO | 50 USDC | In Progress (Claimed) | View on GitHub |
| Streamline app build & deployment process | 500 USDC | Up for Grabs | View on GitHub |
| Javascript Protocol SDK | 2000 USDC | Up for Grabs | View on GitHub |
| Pre-compiled WASM binaries | 500 USDC | Up for Grabs | View on GitHub |
| CI: `e2e-tests` doesn't exit when the node runs into an issue | 100 USDC | Resolved good first issue | View on GitHub |
| Guard against overriding aliases, unless forced | 100 USDC | Resolved good first issue | View on GitHub |
| `merod`'s interactive CLI should support `context update` | TBD | Resolved good first issue | View on GitHub |
| CLI: `identity` should be scoped under `context` | 200 USDC | Resolved good first issue | View on GitHub |
| meroctl: create aliases after context creation, or identity invitation | 100 USDC | Resolved good first issue | View on GitHub |
| merod: create aliases after context creation, or identity invitation | TBD | Resolved good first issue | View on GitHub |
| Introduce a macro to simplify transport definition & declaration | 50 USDC | Resolved good first issue | View on GitHub |
| chore(config): remove protocol duplication in context config | 50 USDC | Resolved good first issue | View on GitHub |
| Consider alias replacement in execution args | 250 USDC | Resolved good first issue | View on GitHub |
| Create aliases after context creation, or identity invitation | 150 USDC | Resolved good first issue | View on GitHub |
| Validate alias targets before associating them | 100 USDC | Resolved good first issue | View on GitHub |
| Default selections for CLI variables | TBD | Resolved good first issue | View on GitHub |
| feat(meroctl): Fetch did through meroctl | 100 USDC | Resolved good first issue | View on GitHub |
| refactor: output of meroctl create context command | 10 USDC | Resolved | View on GitHub |
| Meroctl event listener | 100 USDC | Resolved good first issue | View on GitHub |
| Expose context config permissions management to the APIs | 100 USDC | In Progress (Claimed) good first issue | View on GitHub |
| Improve meroctl Report implementations | 100 USDC | Resolved | View on GitHub |
| merod has missing help descriptions for several fields | 50 USDC | Resolved | View on GitHub |
| Add an app install --watch subcommand to meroctl | TBD | Resolved good first issue | View on GitHub |
| Open admin-dashboard from CLI | 50 USDC | Resolved | View on GitHub |