← Opportunities

MPC Cryptography Library Bug Bounty

Funder
Bron Security · Bron Security Bug Bounty 🟡 Some evidence
Type / status
bounty · open
Amount
0 – 20,000 USD
Deadline
rolling
Ecosystems
Categories
security
Tech stack
Apply
https://bugbounty.bron.org/rewards-mpc
Source
https://bugbounty.bron.org/rewards-mpc
Fit
8% · poor fit · The Venture23 Aleo team focuses on ZK protocol and smart-contract engineering, not MPC cryptography libraries or security bug hunting, making them an outsider to this bounty.
Trust
59% · model self-report 90% · first seen 2026-09-28 · v6
Verified
2026-11-17 · page still up, no closing language

Bron Security runs a bug bounty program for its open-source MPC cryptography library (bron-crypto) that implements threshold signature schemes. Researchers can submit vulnerabilities in cryptographic implementations, memory safety, logic errors, key generation, signing, verification protocols, and BoringSSL integration via email. Rewards range from up to $500 for Low severity to over $20,000 for Exceptional findings, paid in USD-denominated stablecoins to a Bron wallet, plus a non-transferable NFT granting a Basic tier subscription. Reports must use the provided template and are assessed using CVSS v4.0 or expert evaluation for complex issues.

Eligibility: Open to security researchers who can submit vulnerability reports via email using the Vulnerability Report Template; a Bron wallet is required to receive rewards.

Pipeline

Override status:

Funder track record · does Bron actually pay grants?

🟡 Some payout evidence · 1 grantee found · last payout 2023-04-01 · checked 2026-10-30 · 0 forum reports, 6 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
Torfaen Play Service£11,6002023-04-01“A great example of this was in partnership with Torfaen Play Service who received £11,600 to provide play service provision during the school holidays.” source

Trust breakdown (2/4 checkable facts verified)

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

Fit breakdown (against the ORG_* profile)

SignalWeightResultNote
model fit0.510%model rated 10%
ecosystem overlap0.250%none vs aleo
category overlap0.1517%security vs zk, privacy, infra, dev_tooling, security, interoperability
tech overlap0.10%none vs rust, leo, zk

Sources (5)

RoleDocumentFromFetched
primaryMPC Cryptography Library - Bron SecurityWeb discovery: ecosystem sweep2026-09-28
primaryMPC Cryptography Library - Bron SecurityWeb discovery: ecosystem sweep2026-10-09
primaryMPC Cryptography Library - Bron SecurityWeb discovery: ecosystem sweep2026-10-12
primaryMPC Cryptography Library - Bron SecurityWeb discovery: ecosystem sweep2026-10-13
primaryMPC Cryptography Library - Bron SecurityWeb discovery: ecosystem sweep2026-10-26

History (6)

vChangedFields
62026-10-26title, summary, amountMin, amountMinUsd, applicationUrl
52026-10-13summary, amountMin, amountMinUsd, type
42026-10-12summary
32026-10-09summary, amountMax, amountMaxUsd, applicationUrl
22026-09-28summary, amountMin, amountMax, amountMinUsd, amountMaxUsd, type
12026-09-28created

Extracted text

🔐 Non-Custodial Operations

Bron never holds or controls user private keys, funds, or assets. All transactions are user-initiated and executed directly with third-party smart-contract protocols. Swap and staking functions are performed via independent third-party APIs. Bron only provides technical access and does not pool, intermediate, or custody user assets.

## Library Overview

**bron-crypto** is an open source MPC (Multi-Party Computation) cryptography library that implements threshold signature schemes. This library is part of the Bron wallet infrastructure and is licensed under Apache License 2.0.

**Repository:** [github.com/bronlabs/bron-crypto](https://github.com/bronlabs/bron-crypto)  
**Security Policy:** [View Security Policy](https://github.com/bronlabs/bron-crypto/blob/master/SECURITY.md)

For detailed information about scope and experimental features, please refer to the [SECURITY.md](https://github.com/bronlabs/bron-crypto/blob/master/SECURITY.md) file in the repository. All reports must be submitted via email to [\[email protected\]](/cdn-cgi/l/email-protection#5c3e293b3e33293228251c3e2e333272332e3b).

## Reward Calculation

Rewards are calculated based on the CVSS v4.0 Base score when applicable. Use the official calculator: [https://www.first.org/cvss/calculator/4-0](https://www.first.org/cvss/calculator/4-0)

🎖️ NFT Reward Guarantee

Every accepted bounty submission entitles the researcher to a **non-transferable Bron NFT** in addition to the monetary reward listed below. The NFT grants a complimentary Basic tier subscription for 2026 (or an upgrade to the next tier if Basic is already active, capped at Enterprise). To receive any reward, a **Bron wallet is required** — bounty payments are distributed in stablecoins to the researcher's Bron wallet address.

Severity Level

CVSS v4.0 Score

Reward Range (USD)

Low

0.1 — 3.9

Up to $500

Medium

4.0 — 6.9

$500 — $5,000

High

7.0 — 8.9

$5,000 — $10,000

Critical

9.0 — 9.4

$10,000 — $20,000

Exceptional

9.5 — 10.0

more than $20,000

⚠️ Important: Expert Assessment for Complex Vulnerabilities

**If a vulnerability is complex or cannot be properly assessed using CVSS v4.0 metrics, the reward assessment will be conducted individually based on expert evaluation by the core development team.**

Cryptographic vulnerabilities in MPC libraries often involve complex interactions between mathematical primitives, protocol implementations, and security properties that may not map cleanly to standard CVSS scoring. In such cases, our security team will evaluate the vulnerability based on:

*   Potential impact on threshold signature security
*   Exploitation complexity and feasibility
*   Affected components and their criticality
*   Business and security context
*   Novelty and research value of the finding

The final reward amount will be determined through careful expert analysis, ensuring fair compensation for valuable security research while maintaining consistency with our overall bug bounty program structure.

💰 Reward Adjustments

If the PoC demonstrates direct impact on threshold signature security, key generation flaws, or protocol-level vulnerabilities, our security team may apply an increased reward within the specified ranges.

🛡️ Compliance Notice

All bounty payments are made in USD-denominated stablecoins to the researcher's Bron wallet address and are subject to sanctions screening and anti-money-laundering controls consistent with Bron's compliance policy. Rewards cannot be paid to individuals or entities on applicable sanctions lists.

## Scope Information

The bug bounty program covers security vulnerabilities in threshold signature schemes and their direct or indirect dependencies. For additional scope details, see the [SECURITY.md](https://github.com/bronlabs/bron-crypto/blob/master/SECURITY.md) file in the repository.

📋 Key Scope Points

*   **In Scope:** Threshold signature schemes and their direct or indirect dependencies, cryptographic implementation flaws, memory safety issues, logic errors in threshold signature schemes, issues in key generation/signing/verification protocols, vulnerabilities in BoringSSL integration
*   **Out of Scope:** Side-channel vulnerabilities (timing attacks, etc.), experimental features that are not dependencies of threshold signature schemes, vulnerabilities in third-party dependencies (unless they create bron-crypto-specific security issues), **availability and denial-of-service findings** (including Go panic/crash bugs triggered by malformed input — the MPC library threat model assumes authenticated participants and focuses on confidentiality and integrity of threshold signatures; process crashes are expected boundary conditions in the no-honest-majority setting)

## How to Report

All vulnerability reports for the MPC library must be submitted via email:

*   **Email:** [\[email protected\]](/cdn-cgi/l/email-protection#492b3c2e2b263c273d30092b3b262767263b2e) — Please use the [Vulnerability Report Template](report.html)

GitHub Security Advisories are no longer accepted as a submission channel. All reports must go through email.