← Opportunities

Coinbase cb-mpc Bug Bounty

Funder
Coinbase · Coinbase HackerOne program 🟑 Some evidence
Type / status
bounty Β· open
Amount
up to 15,000 USD
Deadline
rolling
Ecosystems
ethereumbitcoinsolanapolygonavalanchearbitrumoptimismbasecosmosnearstellarripplelitecoindogecoincardanopolkadottronfilecoinalgorandtezoseoszcashdashmonerozecbchbnbmaticdotatomnearftmonehbaregldxtzatomiotavetfilhntcrvsnxcompuniaavemakeryvsusdusdcusdtdaibusdtusdpaxhusdgusdusdpusddlusdfraxustusdnusdxusdkusdiusdjusdkusdlusdmusdnusdousdpusdqusdrusdsusdtusduusdvusdwusdxusdyusdz
Categories
security
Tech stack
cpp
Apply
https://hackerone.com/coinbase
Source
https://github.com/coinbase/cb-mpc/blob/master/BUG_BOUNTY.md
Fit
38% Β· weak fit Β· The Venture23 Aleo team has relevant ZK and cryptography expertise in Rust and Leo, which is adjacent to the C++ MPC library, making them a credible but not native fit for this Ethereum-focused security bounty.
Trust
62% Β· model self-report 90% Β· first seen 2026-10-09 Β· v2
Verified
2026-11-14 Β· page still up, no closing language

Coinbase offers a bug bounty for vulnerabilities in its open-source MPC cryptography library (cb-mpc). Eligible reports must target issues reachable through the library's supported public C++ APIs (signing, DKG, TDH2) and include a proof-of-concept for High and Critical tiers. Rewards range up to $15,000 for Critical vulnerabilities and up to $6,000 for High severity bugs. Applications are submitted via the Coinbase HackerOne program.

Eligibility: Open to security researchers who responsibly disclose vulnerabilities reachable through the library's supported public APIs; submissions must not use internal headers as entry points for PoCs.

Pipeline

Override status:

Funder track record Β· does Coinbase actually pay grants?

🟑 Some payout evidence · 11 grantees found · last payout 2024-11-27 · checked 2026-10-29 · 0 forum reports, 10 web pages read, 2 unverifiable claims dropped

Proven payer: at least 3 named grantees and one payout in the last 90 days. Every grantee below is quoted word for word from its source. When a source does not date a grant, the date is when that page or post was published.

GranteeAmountDateEvidence
BrianKnowsβ€”2024-11-27β€œCongratulations to **BrianKnows, Magnet Labs, Questflow, Cat Town, and Basics** on being recipients of CDP's November 2024 Builder Grants!” source
Magnet Labsβ€”2024-11-27β€œCongratulations to **BrianKnows, Magnet Labs, Questflow, Cat Town, and Basics** on being recipients of CDP's November 2024 Builder Grants!” source
Questflowβ€”2024-11-27β€œCongratulations to **BrianKnows, Magnet Labs, Questflow, Cat Town, and Basics** on being recipients of CDP's November 2024 Builder Grants!” source
Cat Townβ€”2024-11-27β€œCongratulations to **BrianKnows, Magnet Labs, Questflow, Cat Town, and Basics** on being recipients of CDP's November 2024 Builder Grants!” source
Basicsβ€”2024-11-27β€œCongratulations to **BrianKnows, Magnet Labs, Questflow, Cat Town, and Basics** on being recipients of CDP's November 2024 Builder Grants!” source
BrianKnowsβ€”2024-11-01β€œCongratulations to BrianKnows, Magnet Labs, Questflow, Cat Town, and Basics on being recip...” source
Magnet Labsβ€”2024-11-01β€œCongratulations to BrianKnows, Magnet Labs, Questflow, Cat Town, and Basics on being recip...” source
Questflowβ€”2024-11-01β€œCongratulations to BrianKnows, Magnet Labs, Questflow, Cat Town, and Basics on being recip...” source
Cat Townβ€”2024-11-01β€œCongratulations to BrianKnows, Magnet Labs, Questflow, Cat Town, and Basics on being recip...” source
Basicsβ€”2024-11-01β€œCongratulations to BrianKnows, Magnet Labs, Questflow, Cat Town, and Basics on being recip...” source
Shinkai$15K2024-09-30β€œCongratulations to **Shinkai**, **Intentify**, **AIFI Zone**, **Community Gaming**, and **SphereOne** on being the first recipients of CDP's AI Builder Grants!” source
Intentify$15K2024-09-30β€œCongratulations to **Shinkai**, **Intentify**, **AIFI Zone**, **Community Gaming**, and **SphereOne** on being the first recipients of CDP's AI Builder Grants!” source
AIFI Zone$15K2024-09-30β€œCongratulations to **Shinkai**, **Intentify**, **AIFI Zone**, **Community Gaming**, and **SphereOne** on being the first recipients of CDP's AI Builder Grants!” source
Community Gaming$15K2024-09-30β€œCongratulations to **Shinkai**, **Intentify**, **AIFI Zone**, **Community Gaming**, and **SphereOne** on being the first recipients of CDP's AI Builder Grants!” source
SphereOne$15K2024-09-30β€œCongratulations to **Shinkai**, **Intentify**, **AIFI Zone**, **Community Gaming**, and **SphereOne** on being the first recipients of CDP's AI Builder Grants!” source
Ayaβ€”2022-09-05β€œAfrican Startup Aya, Receives Grant From Coinbase Giving” source
Shinkaiβ€”undatedβ€œCongratulations to Shinkai, Intentify, AIFI Zone, Community Gaming, and SphereOne on being...” source
Intentifyβ€”undatedβ€œCongratulations to Shinkai, Intentify, AIFI Zone, Community Gaming, and SphereOne on being...” source
AIFI Zoneβ€”undatedβ€œCongratulations to Shinkai, Intentify, AIFI Zone, Community Gaming, and SphereOne on being...” source
Community Gamingβ€”undatedβ€œCongratulations to Shinkai, Intentify, AIFI Zone, Community Gaming, and SphereOne on being...” source
SphereOneβ€”undatedβ€œCongratulations to Shinkai, Intentify, AIFI Zone, Community Gaming, and SphereOne on being...” source

Trust breakdown (3/4 checkable facts verified)

SignalWeightResultNote
deadline0.350%rolling claimed but not stated
amount0.25100%figure appears in source
apply link0.075100%link in source
funder0.075100%named in source
source quality0.1550%social or search hit
model confidence0.190%model self-report
corroborationbonus+5%2 sources

Fit breakdown (against the ORG_* profile)

SignalWeightResultNote
model fit0.570%model rated 70%
ecosystem overlap0.250%ethereum, bitcoin, solana, polygon, avalanche, arbitrum, optimism, base, cosmos, near, stellar, ripple, litecoin, dogecoin, cardano, polkadot, tron, filecoin, algorand, tezos, eos, zcash, dash, monero, zec, bch, bnb, matic, dot, atom, near, ftm, one, hbar, egld, xtz, atom, iota, vet, fil, hnt, crv, snx, comp, uni, aave, maker, yv, susd, usdc, usdt, dai, busd, tusd, pax, husd, gusd, usdp, usdd, lusd, frax, ust, usdn, usdx, usdk, usdi, usdj, usdk, usdl, usdm, usdn, usdo, usdp, usdq, usdr, usds, usdt, usdu, usdv, usdw, usdx, usdy, usdz vs aleo
category overlap0.1517%security vs zk, privacy, infra, dev_tooling, security, interoperability
tech overlap0.10%cpp vs rust, leo, zk

Sources (2)

RoleDocumentFromFetched
primarycb-mpc/BUG_BOUNTY.md at master Β· coinbase/cb-mpc Β· GitHubWeb discovery: ecosystem sweep2026-10-03
primarycb-mpc/BUG_BOUNTY.md at master Β· coinbase/cb-mpc Β· GitHubWeb discovery: ecosystem sweep2026-10-09

History (2)

vChangedFields
22026-10-23title, summary, type
12026-10-09created

Extracted text

[](/coinbase/cb-mpc)

## FilesExpand file tree

master

/

# BUG\_BOUNTY.md

Copy path

Blame

More file actions

Blame

More file actions

## Latest commit

## History

[History](/coinbase/cb-mpc/commits/master/BUG_BOUNTY.md)

[](/coinbase/cb-mpc/commits/master/BUG_BOUNTY.md)History

27 lines (17 loc) Β· 3.84 KB

master

/

# BUG\_BOUNTY.md

Copy path

Top

## File metadata and controls

*   Preview
    
*   Code
    
*   Blame
    

27 lines (17 loc) Β· 3.84 KB

[Raw](https://github.com/coinbase/cb-mpc/raw/refs/heads/master/BUG_BOUNTY.md)

Copy raw file

Download raw file

Edit and raw actions

# CB-MPC (Coinbase Multi-Party Computation) Open Source Release

[](#cb-mpc-coinbase-multi-party-computation-open-source-release)

The [Coinbase HackerOne program](https://hackerone.com/coinbase) is the source of truth for the current bug bounty scope, eligibility requirements, and rewards. This document contains a copy of the relevant program content for convenience and may not reflect the latest updates.

Coinbase is proud to announce the open-sourcing of our MPC cryptography library! You can access it here: [https://github.com/coinbase/cb-mpc](https://github.com/coinbase/cb-mpc). This significant milestone underscores our commitment to transparency, security, and promoting innovation within the cryptographic community.

With this release, we aim to:

*   Enhance the security of the field by enabling developers to quickly deploy threshold signing/MPC for protecting cryptoassets in their applications.
*   Increase transparency regarding Coinbase’s use of MPC, and encourage collaboration within the developer community.

Note that while the code is based on Coinbase's production environment, it is not exactly the same, and it has been modified to make it useful as a general-purpose library.

The primary focus of our bug bounty program will include identifying and addressing potential vulnerabilities in our open-source MPC implementation. Given the sensitive nature of these cryptographic protocols, it's imperative to safeguard against any exploits that could compromise cryptoassets. Responsible disclosure via the Bug Bounty Program or directly is encouraged (for direct disclosure see [https://github.com/coinbase/cb-mpc/blob/master/SECURITY.md](https://github.com/coinbase/cb-mpc/blob/master/SECURITY.md)).

Through community collaboration and vigilant security reviews, we aspire to provide an easy to use and highly secure MPC library to help developers secure cryptoassets across the entire cryptocurrency and blockchain ecosystem.

To keep this bounty focused on issues that affect real integrations, eligible reports should target vulnerabilities reachable through the library's supported public APIs. High-level protocol entry points are exposed via the public C++ headers under `include/cbmpc/api/` (e.g., signing, DKG, TDH2).

For **High** and above, submissions must include a proof-of-concept that triggers the issue through those public APIs. Reports may reference or require fixes in `include-internal/` for root cause and impact analysis, but the PoC must not use `include-internal/` as the entry point. For MPC protocol-break PoCs, we expect the participating parties to run independently, ideally on separate machines. At least one honest party should use unmodified library code, and the malicious party should interact only through the protocol boundary exposed by the supported public APIs. Demo applications and sample code under `demo-*`, and the C API headers under `include/cbmpc/c_api/*`, are not in scope for this bug bounty program.

Vulnerability Tier

Description

Reward

**Extreme**

Open Source Bugs (cb-mpc): not applicable

N/A

**Critical**

Easily exploitable, high-severity bugs in protocols accessible from the public API (e.g., signing, DKG, TDH2 in the cb-mpc open-source library) that could lead to key compromise or remote code execution. Exploitation requires no material precondition beyond normal protocol operation and broadly affects typical deployments.

Up to $15,000

**High**

High-severity bugs in protocols accessible from the public API (e.g., signing, DKG, TDH2 in the cb-mpc open-source library) that could lead to key compromise or remote code execution, but require additionalβ€”yet realisticβ€”conditions, access, or effort to exploit. Exploitation must remain feasible in a realistic deployment and must not depend on unlikely conditions.

Up to $6,000

**Low / Medium**

Out of scope

$0