StarkNet is a validity rollup based on zk-STARK proofs. It operates as an L2 network over Ethereum, enabling any dApp to achieve scale for its computation – without compromising Ethereum's composability and security.

StarkNet is currently still in “alpha” stage. For more information about StarkNet, please visit https://starknet.io/ and https://docs.starknet.io/.

IN SCOPE

Blockchain/DLT

Critical: Max: $250,000 Min: $15,000

• Permanent freezing of funds
• Direct loss of funds

High: $10,000

• Network not being able to confirm new transactions (total network shutdown)
• Unintended chain split (network partition)

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: $15,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.

Prohibition On Simultaneous Submissions

Researchers are not permitted to submit the same vulnerability report simultaneously on multiple platforms. Violation of this rule will result in the blocking of the researcher's account.

OUT OF SCOPE

• Theoretical vulnerabilities without any proof or demonstration
• Old compiler version
• The compiler version is not locked
• Vulnerabilities in imported contracts
• Code style guide violations
• Redundant code
• Gas optimizations
• Best practice issues
• 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
• Vulnerabilities that can be exploited through front-run attacks only
• Network-level DoS
• Exploits as a result of a malicious operator, with the exception of malicious verifier, until Starknet is fully decentralized
• 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
• 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

• Avoid using web application scanners for automatic vulnerability searching which generates massive traffic
• Make every effort not to damage or restrict the availability of products, services, or infrastructure
• Avoid compromising any personal data, interruption, or degradation of any service
• Don’t access or modify other user data, localize all tests to your accounts
• Perform testing only within the scope
• Don’t exploit any DoS/DDoS vulnerabilities, social engineering attacks, or spam
• Don’t spam forms or account creation flows using automated scanners
• In case you find chain vulnerabilities we’ll pay only for vulnerability with the highest severity.
• Don’t break any law and stay in the defined scope
• Any details of found vulnerabilities must not be communicated to anyone who is not a HackenProof Team or an authorized employee of this Company without appropriate permission
• All communication regarding the program must take place exclusively through the HackenProof platform. Contacting the project team directly through support channels, social media, or any other external communication channels is strictly prohibited. Researchers who violate this rule may be disqualified from the program and may face account suspension.

• Do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.
• No vulnerability disclosure, including partial is allowed for the moment.
• Platform-Only Disclosure: Disclosure is only possible through the HackenProof Disclosure function.
• Researchers may request disclosure (Limited or Full) within the report ticket.
• We reserve the right to approve, redact, or deny disclosure requests at our sole discretion.
• Mutual Required: Any publication requires explicit mutual agreement. Reports must remain Private until the status is officially changed to "Public" on the HackenProof platform by the team.

We are happy to thank everyone who submits valid reports which help us improve the security. However, only those that meet the following eligibility requirements may receive a monetary reward:

• You must be the first reporter of a vulnerability.
• The vulnerability must be a qualifying vulnerability.
• Any vulnerability found must be reported no later than 24 hours after discovery and exclusively through hackenproof.com
• You must send a clear textual description of the report along with steps to reproduce the issue, include attachments such as screenshots or proof of concept code as necessary.
• You must not be a former or current employee of us or one of its contractor.
• ONLY USE the EMAIL under which you registered your HackenProof account (in case of violation, no bounty can be awarded)
• Provide detailed but to-the point reproduction steps.
• AI-generated reports without runable PoC are not accepted under this program.