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
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Transaction manipulation / censorship
Double-spending
POLYX minting
Unauthorized token minting
Staled or undermined consensus/network
Governance censorship, compromise or voting result manipulation
Manipulation of signing keys or master keys to gain unauthorized access to an identity
Ability to use an extrinsic panic unexpectedly without proper handling
Block the on-chain governance system from it's expected behavior
Block other users from their ability to perform expected tasks (griefing)
Ability to put chain data into an unexpected state which otherwise doesn't cause any disruption, forcing the emission of events which are incorrect
Out of scope
- Best practice critiques
Blockchain/DLT 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
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 (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
- 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