Polygon

Back to Explore Polygon | Polygon is a fast, low cost, and battle tested blockchain. Live for 5+ years, with 99.99% uptime and millions of users, join them in moving money and RWAs today. ETH Polygon Blockchain L2 Solidity Maximum Bounty $250,000 Live Since 13 September 2021 Last Updated 28 July 2026 PoC Required KYC required Submit a Bug Information Scope Resources Rewards Polygon provides rewards in USDC, POL on Ethereum, Polygon , denominated in USD. Rewards by Threat Level Blockchain/DLT Critical Max: $250,000 Min: $20,000 Primacy of Impact High Flat: $10,000 Primacy of Impact Medium Flat: $2,000 Primacy of Impact Critical Reward Calculation Reward amount is 10 % of the funds directly affected, capped at the maximum critical reward of: $250,000 Minimum reward to discourage security researchers from withholding a bug report: $20,000 The reward is dependent on the ratio between the funds at risk, which includes all affected projects on top of the respective blockchain/DLT, and the market cap according to the average between CoinMarketCap.com and CoinGecko.com, calculated at the time the bug report is submitted. Smart Contract Critical Max: $250,000 Min: $20,000 Primacy of Impact High Flat: $10,000 Primacy of Impact Medium Flat: $2,000 Primacy of Impact Critical Reward Calculation Mainnet assets: Reward amount is 10 % of the funds directly affected up to a maximum of: $250,000 Minimum reward to discourage security researchers from withholding a bug report: $20,000 Rewards Body Reward Distribution Payouts over the lower bound reward are directly related to the direct funds at risk. If no funds are at risk, the Critical or High payouts are limited to the minimum, unless decided otherwise by Polygon Labs. For the purposes of clarification, funds at risk refer to the proof of loss of funds. Rewards for critical Blockchain/DLT and smart contract bug reports will be further capped at 10% of direct funds at risk if the bug discovered is exploited. However, there is a minimum reward of USD 50 000 . Payouts and Payout Requirements Payouts are handled by the Polygon Labs team directly and are denominated in USD. Payouts are done in USDC or POL at the Polygon Labs teams' discretion. Polygon Labs commits to honoring payouts according to the terms set out in this program at the time of report submission, and to treat this program as the agreement and source of truth concerning bug reports and responsible disclosures. POL Payouts will be determined using TWAP 5 day price calculated from payment date. Polygon Labs requires an invoice to be received for each payout. An invoice template can be provided by Polygon Labs. This bug bounty program is only open to individuals who reside outside of the countries that are restricted by OFAC and by UNSC resolutions. If the individual is a US person, tax information may be required in order to properly issue a 1099. Polygon Labs requires an invoice to be received for each payout. An invoice template can be provided by Polygon Labs. KYC Requirements Polygon Labs does have a Know Your Customer (KYC) requirement for bug bounty payouts. KYC Info Required Wallet Address Passport Place of residence KYC information is only required on confirmation of the validity of a bug report which Polygon Labs determines in its sole discretion. View impacts in scope Program Overview Polygon is a Layer 2 scaling solution that achieves scale by utilizing sidechains for off-chain computation and a decentralized network of Proof-of-Stake (PoS) validators. Polygon strives to solve the scalability and usability issues while not compromising on decentralization and leveraging the existing developer community and ecosystem. It aims at improving existing platforms by providing scalability and superior user experience to dApps and user functionalities. It is a scaling solution for public blockchains. Polygon PoS supports all the existing Ethereum tooling along with faster and cheaper transactions. For more information about Polygon Labs and Polygon protocols, please visit https://polygon.technology/ . For Whitehats : It is highly recommended that you review the details of this program in full. Although many Bug Bounty programs have standard terms and conditions, each also has their own unique details that are critical to your success. Prior to submitting a report please review the Immunefi Bug Report Template and Best Practices . Known Issues Category Description / Link Last Updated At Smart Contract │ Any external tokens are expected to correctly follow their standards. Tokens are expected not to have non-standard functionalities such as fees on transfer, blacklists, etc. Rebasing tokens specifically are not supported 8 May 2026 Smart Contract │ CS-POLYGON-SPOL-024 Migration Completion Can Be Front-Run 24 July 2026 Smart Contract │ CS-POLYGON-SPOL-006 "Bridge Liquidity on L1" 14 August 2026 Category Smart Contract Description / Link Any external tokens are expected to correctly follow their standards. Tokens are expected not to have non-standard functionalities such as fees on transfer, blacklists, etc. Rebasing tokens specifically are not supported Last Updated At 8 May 2026 Category Smart Contract Description / Link CS-POLYGON-SPOL-024 Migration Completion Can Be Front-Run Last Updated At 24 July 2026 Category Smart Contract Description / Link CS-POLYGON-SPOL-006 "Bridge Liquidity on L1" Last Updated At 14 August 2026 KYC required The submission of KYC information is a requirement for payout processing. Proof of Concept Proof of concept is always required for all severities. Responsible Publication Category 3: Approval Required Prohibited Activities Default prohibited activities Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet Any testing with pricing oracles or third-party smart contracts Attempting phishing or other social engineering attacks against our employees and/or customers Any testing with third-party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks) Any denial of service attacks that are executed against project assets Automated testing of services that generates significant amounts of traffic Public disclosure of an unpatched vulnerability in an embargoed bounty Any other actions prohibited by the Immunefi Rules Feasibility Limitations The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity. Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report. Chain Rollbacks Pre-Impact Bug Monitoring Attack Investment Amount Attacks With A Financial Risk To The Attacker When Is An Impactful Attack Downgraded To Griefing? Submit a Bug Total paid 8.2M from 90 paid reports Total Assets in Scope 13