Contribute to Calimero Network and earn rewards

Join our
Developer Bounty Program

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.

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

Click on the bounty name to view it on GitHub
arrow-down
Title arrow-down Reward arrow-down Status arrow-down
Implement meroctl devnet command link 250 USDC In Progress (Claimed)
Improve generation of comments from e2e tests link 250 USDC In Progress (Claimed)
Clean up credentials parsing from config link 50 USDC In Progress (Claimed) good first issue
Add ability to list aliases link 50 USDC In Progress (Claimed) good first issue
Proposals default limit to 1 link 250 USDC In Progress (Claimed)
CLI trunk versioning link 250 USDC In Progress (Claimed) good first issue
Expose proposal management to the CLIs link 250 USDC Up for Grabs good first issue
`merod config` revamp link 250 USDC Up for Grabs good first issue
`meroctl` should be able to connect remotely link 250 USDC In Progress (Claimed) good first issue
Document external APIs in calimero-sdk link 50 USDC Up for Grabs
Newly generated identities should be stored temporally link 100 USDC In Progress (Claimed) good first issue
meroctl and merod new version check link 50 USDC In Progress (Claimed)
Do not send private keys over the wire ever link 250 USDC In Progress (Claimed)
Application Registry link TBD Up for Grabs
e2e tests for Calimero SDK and node compatibility link 500 USDC Up for Grabs
User shall be able to invite other users to context link 250 USDC In Progress (Claimed)
Pull out `rocksdb` from `calimero_store` link 100 USDC In Progress (Claimed)
Tracking issue for schema generation link TBD Up for Grabs
Avoid all forms of blocking IO link 50 USDC In Progress (Claimed)
Streamline app build & deployment process link 500 USDC Up for Grabs
Pre-compiled WASM binaries link 500 USDC Up for Grabs
CI: `e2e-tests` doesn't exit when the node runs into an issue link 100 USDC Resolved good first issue
Guard against overriding aliases, unless forced link 100 USDC Resolved good first issue
`merod`'s interactive CLI should support `context update` link TBD Resolved good first issue
CLI: `identity` should be scoped under `context` link 200 USDC Resolved good first issue
meroctl: create aliases after context creation, or identity invitation link 100 USDC Resolved good first issue
merod: create aliases after context creation, or identity invitation link TBD Resolved good first issue
Introduce a macro to simplify transport definition & declaration link 50 USDC Resolved good first issue
chore(config): remove protocol duplication in context config link 50 USDC Resolved good first issue
Consider alias replacement in execution args link 250 USDC Resolved good first issue
Create aliases after context creation, or identity invitation link 150 USDC Resolved good first issue
Validate alias targets before associating them link 100 USDC Resolved good first issue
Default selections for CLI variables link TBD Resolved good first issue
feat(meroctl): Fetch did through meroctl link 100 USDC Resolved good first issue
refactor: output of meroctl create context command link 10 USDC Resolved
Meroctl event listener link 100 USDC Resolved good first issue
Expose context config permissions management to the APIs link 100 USDC In Progress (Claimed) good first issue
Improve meroctl Report implementations link 100 USDC Resolved
merod has missing help descriptions for several fields link 50 USDC Resolved
Add an app install --watch subcommand to meroctl link TBD Resolved good first issue
Open admin-dashboard from CLI link 50 USDC Resolved