Polymesh
Program Overview
Polymesh is an institutional-grade blockchain built specifically for regulated assets that makes it easy to create, issue, and manage tokens on the blockchain. It streamlines antiquated processes and opens the door to new financial instruments by solving the inherent challenges with public infrastructure around identity, compliance, confidentiality, and governance.
For more detailed information about Polymesh, you can visit their website or read their whitepaper.
Rewards by Threat Level
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.2. This is a simplified 5-level scale, with separate scales for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.
The following assets/impacts are considered out of scope of this program:
- https://github.com/PolymeshAssociation/Polymesh/tree/develop/contracts
- “test” code - i.e. javascript integration tests or unit tests.
In addition, known issues highlighted in previous audits are considered out of scope. See
Polymesh requires KYC to be done for all bug bounty hunters submitting a report and wanting a reward. The information needed is a Name, Address, Phone Number, Email Address and Crypto Address (for payment of the award).
Payouts are handled by the Polymesh team directly and are denominated in USD. However, payouts are done in USDC or POLYX, at the discretion of the bug report submitter.
Blockchain/DLT
- Critical
- Level
- USD $6,000
- Payout
- High
- Level
- USD $3,000
- Payout
- Medium
- Level
- USD $1,000
- Payout
Assets in scope
- Blockchain/DLTType
Impacts in scope
Only the following impacts are accepted within this bug bounty program. All other impacts are not considered as in-scope, even if they affect something in the assets in scope table.
Blockchain/DLT
- Transaction manipulation / censorshipCriticalImpact
- Double-spendingCriticalImpact
- POLYX mintingCriticalImpact
- Unauthorized token mintingCriticalImpact
- Staled or undermined consensus/networkCriticalImpact
- Governance censorship, compromise or voting result manipulationCriticalImpact
- Manipulation of signing keys or master keys to gain unauthorized access to an identityCriticalImpact
- Ability to use an extrinsic panic unexpectedly without proper handlingHighImpact
- Block the on-chain governance system from it's expected behaviorHighImpact
- Block other users from their ability to perform expected tasks (griefing)HighImpact
- Ability to put chain data into an unexpected state which otherwise doesn't cause any disruption, forcing the emission of events which are incorrectMediumImpact
Out of Scope & Rules
The following vulnerabilities are excluded from the rewards for this bug bounty program:
- Attacks that the reporter has already exploited themselves, leading to damage
- Attacks requiring access to leaked keys/credentials
- Attacks requiring access to privileged addresses (governance, strategist)
Smart Contracts and Blockchain
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Basic economic governance attacks (e.g. 51% attack)
- Lack of liquidity
- Best practice critiques
- Sybil attacks
- Centralization risks
The following activities are prohibited by this bug bounty program:
- Any testing with mainnet or public testnet contracts; all testing should be done on private testnets
- 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
- Automated testing of services that generates significant amounts of traffic
- Public disclosure of an unpatched vulnerability in an embargoed bounty