Skip to content
bugbounty.fyi
Get paid to secure open source 475 paid open-source programs on Sorona, up to $1M Perk Low bugs: $100 or 1 mo Claude Max

Also on Patchstack. All 476 paid open-source programs

Try

Highest paying Newly launched Paid without KYC Full safe harbor
All results

About this site

Citrea Protocol & Smart Contracts

By Citrea Bug bounty on HackenProof citrea.xyz

Accepting reports KYC to get paid L1/L2 Rust Solidity
Go to program
Top reward
$250,000
Top severity paid
Critical
Assets in scope
40
Public CVEs
0
Last change

At a glance

What to know before you start testing.

Pays up to $250,000
for critical bugs.
Report on HackenProof
Submit through the program page.
Replies within 3 days
As the policy promises.
Paid by USDC on Ethereum
Proof of identity needed to get paid.
No public write-ups
Keep findings private.

Rewards

What HackenProof lists as the payout for each severity.

Severity Reward
Critical $250,000
Response
Within 3 days First Response 3d

Summarised with AI from the program policy on HackenProof, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

40 assets you may test.

Smart contracts 36

  • https://basescan.org/address/0x11030f79109269d796fd0FB956D6244e502757f7
  • https://bscscan.com/address/0x6dFbBb567Ee504016aD06E0880A96238c7EAC61d
  • https://etherscan.io/address/0x2c01390E10e44C968B73A7BcFF7E4b4F50ba76Ed
  • https://etherscan.io/address/0xbc9bdd439a71418c6a5d4f6c37bae75c8215ec03
  • https://etherscan.io/address/0xdaa289CC487Cf95Ba99Db62f791c7E2d2a4b868E
  • https://etherscan.io/address/0xE1CD98671869aEd24889fA86172153Cdf1d220DD
  • https://explorer.mainnet.citrea.xyz/address/0x02B5F31C5A3CCaE18Dcb7425D7eA11dbcd0fa81B
  • https://explorer.mainnet.citrea.xyz/address/0x18D8A784d0F90Dea03d7BFEeFDb4c51eddfD9feF
  • https://explorer.mainnet.citrea.xyz/address/0x2015F35030A8Ff2C0CA161a865414996F8E80AA4
  • https://explorer.mainnet.citrea.xyz/address/0x3100000000000000000000000000000000000001
  • https://explorer.mainnet.citrea.xyz/address/0x3100000000000000000000000000000000000002
  • https://explorer.mainnet.citrea.xyz/address/0x3100000000000000000000000000000000000003
  • https://explorer.mainnet.citrea.xyz/address/0x3100000000000000000000000000000000000004
  • https://explorer.mainnet.citrea.xyz/address/0x3100000000000000000000000000000000000005
  • https://explorer.mainnet.citrea.xyz/address/0x3100000000000000000000000000000000000006
  • https://explorer.mainnet.citrea.xyz/address/0x3100000000000000000000000000000000000007
  • https://explorer.mainnet.citrea.xyz/address/0x31ffffffffffffffffffffffffffffffffffffff
  • https://explorer.mainnet.citrea.xyz/address/0x3200000000000000000000000000000000000001
  • https://explorer.mainnet.citrea.xyz/address/0x3200000000000000000000000000000000000002
  • https://explorer.mainnet.citrea.xyz/address/0x3200000000000000000000000000000000000003
  • https://explorer.mainnet.citrea.xyz/address/0x3200000000000000000000000000000000000004
  • https://explorer.mainnet.citrea.xyz/address/0x3200000000000000000000000000000000000005
  • https://explorer.mainnet.citrea.xyz/address/0x3200000000000000000000000000000000000007
  • https://explorer.mainnet.citrea.xyz/address/0x3B035A24c49Bf7100897b3D0C0A6CEe4044a8bee
  • https://explorer.mainnet.citrea.xyz/address/0x41710804caB0974638E1504DB723D7bddec22e30
  • https://explorer.mainnet.citrea.xyz/address/0x4fDDfcB9e334E387af824EdEd3793b947F36eb35
  • https://explorer.mainnet.citrea.xyz/address/0x5A4d0dc24DB3751cDC6d217a16e02b84949B4999
  • https://explorer.mainnet.citrea.xyz/address/0x6925ccD29e3993c82a574CED4372d8737C6dbba6
  • https://explorer.mainnet.citrea.xyz/address/0x814B0538398596248B39e499262E6Cf53F276452
  • https://explorer.mainnet.citrea.xyz/address/0x9f3096Bac87e7F03DC09b0B416eB0DF837304dc4
  • https://explorer.mainnet.citrea.xyz/address/0xc5Ec494878F51d2641a17B49606B47e933c961d3
  • https://explorer.mainnet.citrea.xyz/address/0xDF240DC08B0FdaD1d93b74d5048871232f6BEA3d
  • https://explorer.mainnet.citrea.xyz/address/0xE045e6c36cF77FAA2CfB54466D71A3aEF7bbE839
  • https://explorer.mainnet.citrea.xyz/address/0xe15ee513f807d12a78a80a97ab586E95c6319901
  • https://explorer.mainnet.citrea.xyz/address/0xF8b5983BFa11dc763184c96065D508AE1502C030
  • https://explorer.mainnet.citrea.xyz/token/0x547AfD93B9c47D552059FEb556909e017f8a9b25

Source code 3

  • https://github.com/chainwayxyz/citrea/releases/latest
  • https://github.com/chainwayxyz/clementine-cli
  • https://github.com/chainwayxyz/clementine/releases/latest

Web 1

  • https://rpc.mainnet.citrea.xyz

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Citrea Protocol & Smart Contracts (via HackenProof)'s policy.

While testing

  • Any vulnerability found must be reported no later than 24 hours after discovery and exclusively through hackenproof.com
  • ONLY USE the EMAIL under which you registered your HackenProof account (in case of violation, no bounty can be awarded)
  • You must send a clear textual description of the report along with steps to reproduce the issue, include attachments such as screenshots or proof of concept code as necessary.
  • Do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization
  • Please do NOT publish/discuss bugs

Not accepted

  • Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
  • Impacts caused by attacks requiring access to leaked keys/credentials
  • Best practice recommendations
  • Feature requests
  • Impacts requiring phishing or other social engineering attacks against project's employees and/or customers
  • Incorrect data supplied by third party oracles
  • Impacts requiring basic economic and governance attacks (e.g. 51% attack)
  • Lack of liquidity impacts
  • Impacts from Sybil attacks
  • Impacts involving centralization risks
  • AI-generated reports without runable PoC are not accepted under this program.

Summarised with AI from the program policy on HackenProof, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 1 hour ago.

No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.

Before we tracked it

Scope and reward changes recorded before this page started tracking it.

  1. Scope removed

    https://etherscan.io/address/0xbc9bdd439a71418c6a5d4f6c37bae75c8215ec03

  2. Scope removed

    https://etherscan.io/address/0x6925ccD29e3993c82a574CED4372d8737C6dbba6

  3. Scope removed

    https://etherscan.io/address/0x9f3096bac87e7f03dc09b0b416eb0df837304dc4

  4. Scope removed

    https://etherscan.io/address/0x2c01390E10e44C968B73A7BcFF7E4b4F50ba76Ed

  5. Scope removed

    https://etherscan.io/address/0xdaa289CC487Cf95Ba99Db62f791c7E2d2a4b868E

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search NVD

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.

Original policy

Copied from hackenproof.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.

Bug bounty Triaged by HackenProof Citrea Protocol & Smart Contracts: Program info Citrea Protocol & Smart Contracts Company: Citrea Scope Review: 369999 Submissions: 795 Total rewards: $11,300 Reputation 50 points required KYC Required PoC Required Submission fee $5 Program is: active now Live Submit report Program info Hackers 304 Reports 0 Citrea is the first rollup that enhances the capabilities of Bitcoin blockspace with zero-knowledge technology. Citrea is the only scalability solution that uses Bitcoin both as a data availability and a settlement layer, via its BitVM-based trust-minimized two-way peg program - Clementine. Citrea is fully EVM compatible, enabling all EVM developers to easily build on Bitcoin. For more information about Citrea, please visit https://citrea.xyz. Citrea provides rewards in USDC on Ethereum, denominated in USD. For more details about the payment process, please view the Rewards by Threat Level section further below. All Scope Focus Area Program Rules Eligibility and Coordinated Disclosure Disclosure Guidelines Documentation Scope Search targets In scope Target │ Type │ Severity https://rpc.mainnet.citrea.xyz Copy Blockchain/DLT - Official RPC │ Protocol │ Critical https://github.com/chainwayxyz/citrea/releases/latest Copy Blockchain/DLT - Node / protocol codebase │ Protocol │ Critical https://github.com/chainwayxyz/clementine/releases/latest Copy Blockchain/DLT - Clementine codebase: bridge operator, verifiers, aggregator, watchtower; BitVM-verified circuit │ Infrastructure │ Critical https://github.com/chainwayxyz/clementine-cli Copy Smart Contract │ Critical https://explorer.mainnet.citrea.xyz/address/0x3100000000000000000000000000000000000002 Copy System Contracts Bridge Proxy │ Smart Contract │ Critical https://explorer.mainnet.citrea.xyz/address/0x3100000000000000000000000000000000000003 Copy System Contracts Base Fee Vault Proxy │ Smart Contract │ Critical Show all targets Focus Area Impacts in Scope Below are the impacts accepted by default under this bug bounty program. Nevertheless, Citrea team is open to considering any impactful out-of-scope items on a case-by-case basis, following the Primacy of Impact spirit of this Program. Blockchain/DLT - Citrea Core Rollup Protocol Critical . Invalid state transition accepted as valid (soundness bug in proving/verifying/transition logic) leading to direct loss of funds or protocol insolvency Critical . Direct loss of funds Critical . Permanent freezing of funds (fix requires hardfork) High . Bitcoin-anchoring verification failure: accepting a batch/commitment/proof that should not be accepted (e.g., incorrect parsing/validation of Bitcoin-derived inputs) leading to incorrect canonical state High . Total network shutdown: the network cannot confirm new transactions due to a protocol/client bug (beyond “RPC is down”) High . Reorg-handling bug (Bitcoin-side or Citrea-side) that causes prolonged halt, inconsistent views, or unsafe rollback behavior Medium . Split in Light Client Proofs. The Light Client Proof circuit is designed to be deterministic: a Bitcoin block will always yield the same Citrea state upon successful proving. Any behaviour that breaks this assumption can be used to attack Bridge operators. Medium . Breaking the Batch Proof. Any diversion between "native" L2 block execution vs. "circuit" L2 block execution Medium . Unbounded gas/resource consumption leading to severe degradation or halting of critical components (sequencer/full nodes) without direct theft Medium . A bug in the respective layer 0/1/2 network code that results in unintended smart contract behavior with no concrete funds at direct risk Medium . Block stuffing for profit / griefing that meaningfully harms availability or user experience Low . Issues which require an operator to be dishonest for exploitation. Low . Minor correctness issues that don’t rise to meaningful economic/security impact Blockchain/DLT - Clementine Bridge Protocol Citrea has a Clementine bridge, which is a combination of Blockchain/DLT and Smart contracts items, therefore it is in a separate list below: Critical . Direct theft of BTC/cBTC via deposit/withdraw verification bugs (e.g., forging inclusion proofs, bypassing script checks, replay/duplicate withdrawal intents) Critical . Permanent freezing of bridged funds (cannot be fixed by upgrade / cannot be recovered within the documented model) Critical . Direct loss of funds High . Role/pausing logic vulnerabilities that allow an unprivileged attacker to bypass safety controls (note: “attacker has the owner key” stays out-of-scope; “role escalation / auth bypass” stays in-scope) High . Clementine CLI bugs that allow wallet loss, incorrect deposit address generation, or withdrawal losses High . Bugs with Clementine presigning, causing failure of operator’s reimbursements failed Medium . Griefing that causes large-scale disruption of deposits/withdrawals without theft other than by the Aggregator (e.g., forcing funds into failed deposit paths, forcing costly replacement flows) Low . Issues which require an operator to be dishonest for exploitation. Low . Non-impactful correctness issues (UX-only, docs mismatch, etc.) Low . Clementine Tx Sender failures (Usually these txs can be sent manually) Smart Contracts Critical . Direct theft of any user funds, whether at-rest or in-motion Critical . Permanent freezing of funds Critical . Predictable or manipulable RNG that results in abuse of the principal or NFT Critical . Protocol insolvency High . Permanent/long-term freezing of bridged assets/messages due to logic bugs (fixable by upgrade) High . Temporary freezing of funds High . System Smart contracts are unable to operate Medium . Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol) Medium . Theft of gas Medium . Unbounded gas consumption Low . Minor issues not impacting asset safety or liveness Out of Scope & Rules These impacts are out of scope for this bug bounty program. All Categories Impacts requiring attacks that the reporter has already exploited themselves, leading to damage Impacts caused by attacks requiring access to leaked keys/credentials Impacts caused by attacks requiring access to privileged addresses (governance, strategist) except in such cases where the contracts are intended to have no privileged access to functions that make the attack possible Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production Best practice recommendations Feature requests Impacts on test files and configuration files unless stated otherwise in the bug bounty program Impacts requiring phishing or other social engineering attacks against project's employees and/or customers Blockchain/DLT & Smart Contract Specific Incorrect data supplied by third party oracles Not to exclude oracle manipulation/flash loan attacks Impacts requiring basic economic and governance attacks (e.g. 51% attack) Lack of liquidity impacts Impacts from Sybil attacks Impacts involving centralization risks Reports that are already covered under the LayerZero Bug Bounty Program will be forwarded to LayerZero (and paid under LayerZero’s program if accepted) Program Rules Rewards are distributed according to the impact of the vulnerability based on the HackenProof Vulnerability Classification . Reward Calculation for Critical Level Reports For critical Blockchain/DLT bugs and Smart Contract Bugs, the reward amount is 10% of the funds directly affected, capped at the maximum critical reward 250,000 USD. However, a minimum reward of 25,000 USD is to be rewarded in order to incentivize security researchers against withholding on a bug report. For critical Blockchain/DLT bugs with a non-funds-at risk impact, the reward will be paid out as follows: Network not being able to confirm new transactions (total network shutdown) Permanent freezing of funds (fix requires hardfork) - 50,000 USD For critical web/apps bugs, reports will be rewarded with 25,000 USD, only if the report demonstrates wallet-drain or equivalent financial loss vector. All other impacts that would be classified as Critical would be rewarded a flat amount of 10,000 USD. The rest of the severity levels are paid out according to the Impact in Scope table. Repeatable Attack Limitations If the smart contract where the vulnerability exists can be upgraded or paused, only the initial attack will be considered for a reward. This is because the project can mitigate the risk of further exploitation by upgrading or pausing the component where the vulnerability exists. The reward amount will depend on the severity of the impact and the funds at risk. For critical repeatable attacks on smart contracts that cannot be upgraded or paused, the project will consider the cumulative impact of the repeatable attacks for a reward. This is because the project cannot prevent the attacker from repeatedly exploiting the vulnerability until all funds are drained and/or other irreversible damage is done. Therefore, this warrants a reward equivalent to 10% of funds at risk, capped at the maximum critical reward. Reward Calculation for High Level Reports High vulnerabilities concerning theft/permanent freezing of unclaimed yield/royalties are rewarded within a range of Reward - Smart contract - Min High to Reward - Smart contract - Max High depending on the funds at risk, capped at the maximum high reward. In the event of temporary freezing, the reward doubles from the full frozen value for every additional 24h that the funds are temporarily frozen, up until a max cap of the high reward. This is because as the duration of the freezing lengthens, the potential for greater damage and subsequent reputational harm intensifies. Thus, by increasing the reward proportionally with the frozen duration, the project ensures stronger incentives for bug disclosure of this nature. Reward Payment Terms Payouts are handled by the Citrea team directly and are denominated in USD. However, payments are done in USDC on Ethereum. Blockchain/DLT Critical: 25,000 - 250,000 USD High: 10,000-25,000 USD Medium: 1,000-3,000 USD Low: 100-1000 USD Smart Contract Critical: 25,000 - 250,000 USD High: 10,000-25,000 USD Medium: 1,000-3,000 USD Low: 100-1,000 USD Eligibility and Coordinated Disclosure We are happy to thank everyone who submits valid reports which help us improve the security. However, only those that meet the following eligibility requirements may receive a monetary reward: You must be the first reporter of a vulnerability. The vulnerability must be a qualifying vulnerability Any vulnerability found must be reported no later than 24 hours after discovery and exclusively through hackenproof.com You must send a clear textual description of the report along with steps to reproduce the issue, include attachments such as screenshots or proof of concept code as necessary. You must not be a former or current employee of us or one of its contractor. ONLY USE the EMAIL under which you registered your HackenProof account (in case of violation, no bounty can be awarded) Provide detailed but to-the point reproduction steps AI-generated reports without runable PoC are not accepted under this program. Disclosure Guidelines Do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization No vulnerability disclosure, including partial is allowed for the moment. Please do NOT publish/discuss bugs Documentation Citrea’s codebase can be found at https://github.com/chainwayxyz and https://github.com/chainwayxyz/token-bridge/token-bridge Documentation and further resources can be found on https://docs.citrea.xyz Previous Audits Citrea’s completed audit reports can be found at https://docs.citrea.xyz/security/audits-inquiries. Any unfixed vulnerabilities mentioned in these reports are not eligible for a reward Live since 28 Jan 2026 Published date 28 Jan 2026 Last updated 11 Nov 2026 Range of bounty $100 - $250,000 Severity Critical $25,000 - $250,000 High $10,000 - $25,000 Medium $1,000 - $3,000 Low $100 - $1,000 L1/L2 smart contract blockchain Rust Solidity @ConcAI KYC Verified 1 @TrustSec 2 @fromeo016 KYC Verified 3 @0xsolisec KYC Verified 4 @audinarey KYC Verified 5 Response type Business days First Response 3d Triage Time 3d Reward Time 3d Resolution Time 14d