Astar Network
Astar Network supports the building of dApps with EVM and WASM smart contracts and offers developers true interoperability with cross-consensus messaging and cross-virtual machines. Astar’s unique Build2Earn model empowers developers to get paid through a dApp staking mechanism for the code they write and dApps they build.
PoC required
KYC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Any network to shut down or otherwise not confirm new valid transactions for multiple blocks
Unintended permanent chain split requiring hard fork (network partition requiring hard fork)
Direct loss of funds
Permanent freezing of funds (fix requires hardfork)
Transaction/consensus manipulation
Unauthorized token minting
Governance compromise
Getting access to an identity that can lead to unauthorized access to system’s or user’s assets
Empty or freeze the contract's holdings (e.g. economic attacks, flash loans, reentrancy, MEV, logic errors, integer over-/under-flow)
Cryptographic flaws
Execute arbitrary system commands
Retrieve sensitive data/files from a running server such as /etc/shadow, database passwords, and blockchain keys(this does not include non-sensitive environment variables, open source code, or usernames)
Out of scope
-
Spamming
-
Any physical attacks against Astar property, or employees
-
Phishing or other social engineering attacks against our Astar’s employees
-
Any attack requiring successful phishing or another scam to be executed
-
Astar network footprints such as employee email addresses, subdomains, whois info
-
GitHub and other cloud platforms misconfiguration are considered web/app vulnerabilities.
-
All vulnerabilities and attack methods that are listed in OWASP https://owasp.org/www-community/attacks/
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