Hedera Bug Bounty
Hedera offers a bug bounty program through Immunefi with rewards up to $30,000 for critical blockchain/DLT vulnerabilities. Security researchers can submit bugs affecting Hedera's hashgraph consensus, smart contracts, consensus, and token services. Rewards are paid in USDC on Ethereum and require KYC verification. Applications are submitted via the Immunefi platform.
Eligibility: Open to security researchers and developers who discover vulnerabilities in OP Stack or OP Mainnet codebases; public disclosure or testing on testnet/mainnet forfeits reward eligibility.
Pipeline
Funder track record · does Optimism Collective actually pay grants?
✅ Proven payer · 3 grantees found · last payout 2026-10-12 · checked 2026-10-29 · 2 forum reports, 4 web pages read
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.
| Grantee | Amount | Date | Evidence |
|---|---|---|---|
| Quadri | — | 2026-10-12 post date | “Grant Streamer: On-chain grant disbursement prototype” forum |
| Gonna.eth | — | 2026-05-23 post date | “Season 9 Final Report” forum |
| Ancient8 | 500,000 $OP | 2024-12-01 | “Ancient8 recently secured a 500,000 $OP grant from Optimism's Governance Fund” source |
| Ancient8 | major grant | 2024-12-01 | “Ancient8 has received a major grant from Optimism's Governance Fund” source |
Trust breakdown (1/4 checkable facts verified)
| Signal | Weight | Result | Note |
|---|---|---|---|
| deadline | 0.35 | 0% | rolling claimed but not stated |
| amount | 0.25 | 0% | figure not found in source |
| apply link | 0.075 | 0% | link not in source |
| funder | 0.075 | 100% | named in source |
| source quality | 0.15 | 50% | social or search hit |
| model confidence | 0.1 | 95% | model self-report |
| corroboration | bonus | +10% | 13 sources |
Fit breakdown (against the ORG_* profile)
| Signal | Weight | Result | Note |
|---|---|---|---|
| model fit | 0.5 | 10% | model rated 10% |
| ecosystem overlap | 0.25 | 0% | optimism, ethereum vs aleo |
| category overlap | 0.15 | 17% | security vs zk, privacy, infra, dev_tooling, security, interoperability |
| tech overlap | 0.1 | 0% | none vs rust, leo, zk |
Sources (13)
| Role | Document | From | Fetched |
|---|---|---|---|
| primary | Optimism Documentation | Web discovery: ecosystem sweep | 2026-10-12 |
| mirror | Optimism Bug Bounty | Immunefi | Web discovery: ecosystem sweep | 2026-10-15 |
| mirror | Cosmos Bug Bounty Scope | Immunefi | Web discovery: ecosystem sweep | 2026-10-16 |
| mirror | Stacks Bug Bounty | Immunefi | Web discovery: ecosystem sweep | 2026-10-16 |
| mirror | Hedera Bug Bounty | Immunefi | Web discovery: ecosystem sweep | 2026-10-16 |
| mirror | ZKsync Era Bug Bounty | Immunefi | Web discovery: ecosystem sweep | 2026-10-16 |
| mirror | Stacks Bug Bounty Scope | Immunefi | Web discovery: ecosystem sweep | 2026-10-16 |
| mirror | ZKsync OS Bug Bounty | Immunefi | Web discovery: ecosystem sweep | 2026-10-16 |
| mirror | ZKsync Era Bug Bounty | Immunefi | Web discovery: ecosystem sweep | 2026-10-18 |
| mirror | Hedera Bug Bounty | Immunefi | Web discovery: ecosystem sweep | 2026-10-19 |
| mirror | Cosmos Bug Bounty Scope | Immunefi | Web discovery: ecosystem sweep | 2026-10-23 |
| mirror | SP1 Bug Bounty | Immunefi | Web discovery: ecosystem sweep | 2026-10-24 |
| mirror | Hedera Bug Bounty | Immunefi | Web discovery: ecosystem sweep | 2026-10-24 |
History (13)
| v | Changed | Fields |
|---|---|---|
| 13 | 2026-10-24 | title, summary, amountMin, amountMax, currency, amountMinUsd, amountMaxUsd |
| 12 | 2026-10-24 | title, summary, amountMin, amountMax, currency, amountMinUsd, amountMaxUsd |
| 11 | 2026-10-23 | title, summary, amountMin, amountMax, amountMinUsd, amountMaxUsd, type |
| 10 | 2026-10-19 | title, summary, amountMin, amountMax, amountMinUsd, amountMaxUsd |
| 9 | 2026-10-18 | title, summary, amountMin, amountMax, amountMinUsd, amountMaxUsd |
| 8 | 2026-10-16 | title, summary, amountMin, amountMax, amountMinUsd, amountMaxUsd |
| 7 | 2026-10-16 | title, summary, amountMin, amountMax, amountMinUsd, amountMaxUsd |
| 6 | 2026-10-16 | title, summary, amountMin, amountMax, amountMinUsd, amountMaxUsd |
| 5 | 2026-10-16 | title, summary, amountMin, amountMax, amountMinUsd, amountMaxUsd, type |
| 4 | 2026-10-16 | title, summary, amountMin, amountMax, amountMinUsd, amountMaxUsd, type |
| 3 | 2026-10-16 | title, summary, amountMin, amountMax, amountMinUsd, amountMaxUsd |
| 2 | 2026-10-15 | title, summary, amountMin, amountMinUsd, applicationUrl |
| 1 | 2026-10-12 | created |
Extracted text
This page describes general best practices for reporting bugs and provides specific reporting guidelines for OP Stack and OP Mainnet code contained within the [ethereum-optimism](https://github.com/ethereum-optimism) GitHub organization. **Do not** disclose vulnerabilities publicly or by executing them against a production network. If you do, you will not only be putting users at risk, but you will forfeit your right to a reward. Always follow the appropriate reporting pathways as described below. * **Do not** disclose the vulnerability publicly, for example by filing a public ticket. * **Do not** test the vulnerability on a publicly available network, either the testnet or the mainnet. ## [ ](#optimism-bug-bounty-program) Optimism bug bounty program The Optimism Bug Bounty Program offers up to [$2,000,042](https://immunefi.com/bounty/optimism/) for critical vulnerabilities found in the OP Mainnet codebase. Below you can find information about the various available bug bounty programs and how to report bugs that are not covered by an existing bounty. ### [ ](#main-bounty-page) Main bounty page Optimism has a very detailed [Bug Bounty Page on Immunefi](https://immunefi.com/bounty/optimism/). In the listing you can find all the information relating to components in scope, reporting, and the payout process. ### [ ](#unscoped-bugs) Unscoped bugs If you think you have found a significant bug or vulnerability in OP Stack smart contracts, infrastructure, etc., even if that component is not covered by an existing bug bounty, please report it via the [Immunefi program](https://immunefi.com/bounty/optimism/). The impact of any and all reported issues will be considered and the program has previously rewarded security researchers for bugs not within its stated scope. ## [ ](#reporting-other-vulnerabilities) Reporting other vulnerabilities For vulnerabilities in any websites, email servers, or other non-critical infrastructure within the OP Stack, please report them through the [Optimism bug bounty program on Immunefi](https://immunefi.com/bug-bounty/optimism/information/) and include detailed instructions for confirming and reproducing the vulnerability. ### [ ](#vulnerability-disclosure) Vulnerability disclosure Each OP Stack component maintainer may determine its own process for vulnerability disclosure. However, the following describes a recommended process for disclosure. In the event that an OP Stack component maintainer learns of a critical security vulnerability, the maintainer reserves the right to silently fix it without immediately publicly disclosing the existence or nature of the vulnerability. In such a scenario, the disclosure process used is as follows: 1. Silently fix the vulnerability and include the fix in release X. 2. After 4-8 weeks, disclose that release X contained a security fix. 3. After an additional 4-8 weeks, publish details of the vulnerability, along with credit to the reporter (with express permission from the reporter). ### [ ](#rights-of-maintainers) Rights of maintainers Alongside this policy, maintainers also reserve the right to: * Bypass this policy and publish details on a shorter timeline. * Directly notify a subset of downstream users prior to making a public announcement. This policy is based on the [Geth](https://geth.ethereum.org/) team’s [silent patch policy](https://geth.ethereum.org/docs/developers/geth-developer/disclosures#why-silent-patches). Was this page helpful? YesNo