All smart contracts of Stacks can be found at [https://github.com/stacks-network/stacks-blockchain/blob/master/src/chainstate/stacks/boot](https://github.com/stacks-network/stacks-blockchain/blob/master/src/chainstate/stacks/boot).  However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

Though the Node implementation asset has “testnet” in the folder name, it is not a testnet node and is within the scope of the bug bounty program.

During a planned network upgrade, and with a 3 month window after the last hard fork is released, we’ve lowered the payouts for all classes of bug reports. This is a temporary measure as we work out any undiscovered bugs in our testing during this network transition. We still welcome reports during this transition, but be aware there will likely be a reduced payout until the network upgrade is finalized.

Any remotely-exploitable denial of service in a node

Any network denial of service impacting more than 10% of miners that does not shut down the network

Any in-scope smart contract fails to deliver promised returns, but doesn’t lose value

Any underpricing or overpricing of smart contract operations

Any unintended chain split or network partition

Any remotely-exploitable memory access, disk access, or persistent code execution. Attacks are restricted to the Stacks blockchain RPC/P2P ports

Any theft of an unclaimed reward

Any permanent freezing of an unclaimed reward

Any transient consensus failures

Any block stuffing without fund transfers being blocked

Anylock stuffing such that smart contract calls can be blocked, but without paying any requisite higher transaction fees

Any network to shut down or otherwise not confirm new valid transactions for multiple blocks

Any triggering of a deep fork of 10 or more blocks without spending the requisite Bitcoin

Any causing the direct loss of funds other than through any form of freezing

Any chain split caused by different nodes processing the same block or transaction and yielding different results

Any confirmation of an invalid transaction, such as with an incorrect nonce

Any loss of user funds by permanent freezing or theft

Any loss of governance funds (limited to `.cost-vote`)

Any governance vote manipulation

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.

__Please note that all variants of remote denial-of-service attacks will automatically have their impact set to “Low”, regardless of any further downstream impact.__

Please review open PRs before your submission as all duplicate attacks are considered “Out of Scope” as per below.

Stacks Codebase

Rewards are distributed according to the impact of the vulnerability based on the [Immunefi Vulnerability Severity Classification System V2.2](https://immunefi.com/immunefi-vulnerability-severity-classification-system-v2-2). This is a simplified 5-level scale, with separate scales for each category, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit. If there is any discrepancy with the classification in the Impacts in Scope section, the classification in the Impacts in Scope section will hold true.

Please note that Critical finding bounties are capped at 10% of the damage resulting from the finding. This mostly takes into account technical and financial damage but also includes the “human” impact, including reputational risk. We will guarantee a minimum payout of $25,000 USD for all valid Critical findings.

__We agree to:__

  - Respond meaningfully to all reported issues in a timely manner.
  - Not pursue legal action against or “counter-hack” any researchers acting in good faith and abiding by this program’s rules.
  - Consider theoretical attacks and findings without proof-of-concept code as long as technically meaningful, evidence-based arguments are provided.

__You must:__

  - Undergo full KYC. We are based in the United States and abide by all relevant law, including OFAC controls and sanctions.
  - Not be based or test from an OFAC-sanctioned country or region or (be a sanctioned individual or organization) as defined here: [https://ofac.treasury.gov/sanctions-programs-and-country-information](https://ofac.treasury.gov/sanctions-programs-and-country-information)
  - Report all bugs using this template. __All fields are required unless otherwise marked__. Fields with a star (*) must be encrypted with the security@stacks.org GPG key, fingerprint 8A8B 3C3B 803A 0603 8FB5  3F69 357C 80AB 0885 87A0.
    - Executive summary of issue: 
    - Finding details: 
    - Repository, file, and line of code where finding is found:  
    - Steps to replicate*: 
    - Proof-of-concept exploitation code*: 
    - Screenshots or video of finding being exploited using the PoC you have provided*:  
    - Impact of finding (short term): 
    - Impact of finding (long term): 
    - Mitigation suggestions (short term):
    - Mitigation suggestions (long term): 
    - (Optional) Suggested patch:
    - (Optional) Any useful links or resources:
    - (Optional) Do you want a shout-out on our Security Wall of Fame? 
    - (Optional, if approved) Do you want a cybersecurity-themed NFT sent to your Stacks wallet?
  - Use a private testnet. Testing on mainnet or public testnets is forbidden.

Payouts are handled by the __Stacks Foundation team__ directly and are denominated in __USD__. However, payments will be made in the __USD__ equivalent in the __Stacks__ token (STX).