Polymesh
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.
PoC required
KYC required
Rewards
Rewards by Threat Level
Reward amount is 10% of the funds directly affected, capped at the maximum critical reward of:
$6,000Rewards 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.
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.
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.
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.