https://staking.synthetix.io/ and https://github.com/Synthetixio/js-monorepo/tree/master

Documentation for the assets provided in the table can be found at [https://docs.synthetix.io/synthetix-protocol/readme](https://docs.synthetix.io/synthetix-protocol/readme). 

Unless explicitly listed, only pages of the web/app assets in addition to the direct link are considered in-scope of the bug bounty program. Other subdomains are not considered as in-scope. However, for subdomain takeovers that lead to an impact on the in-scope asset, please refer to our page about [Reported Subdomain Takeovers](https://immunefisupport.zendesk.com/hc/en-us/articles/14352199704593-Reported-Subdomain-Takeovers).

Synthetix provides a building layer that allows other protocols to tap into its universal liquidity pool, offering derivative exposure on an EVM compatible chain.

Direct theft of collateral from liquidity providers and borrowers (i.e. staked assets)

Direct theft of tokens and NFTs from token and NFT holders (i.e. v3 staking position / sUSD / snxUSD /…)

Permanent bricking of staking or trading contracts resulting in losses to owners, where the assets can’t be recovered by any means

Governance voting result manipulation that could result a critical severity classification

Immediate manipulation of the debt of the protocol,  not related to oracle price changes, nor related to debt fluctuations from interactions that are within the intended design

Immediate protocol Insolvency of liquidity providers

Theft of unclaimed yield that can be become claimable by the attacker immediately (i.e. swapped to external assets), or claimable after a period of time where the protocol is unable to safeguard the funds at risk via code updates

Execute arbitrary system commands

Subdomain takeover with already-connected wallet interaction

Theft of unclaimed yield that can be become claimable by the attacker within 24 hours of the attack

Temporary freezing of funds

Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)

Insolvency of liquidity providers and generation of bad debt, where the attack spans multiple transactions over an extended period of time

Governance voting result manipulation that could result a high severity classification

Changing sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as: email or password of the victim, etc

Injecting/modifying the static content on the target application without Javascript (Reflected) such as: reflected HTML injection, loading external site data

Redirecting users to malicious websites (Open Redirect)

Manipulation of the governance voting UI with the intent of luring votes into voting for the wrong candidate

Other governance voting result manipulation

Theft of unclaimed yield that can be become claimable by the attacker

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.

Rewards are distributed according to the impact the vulnerability could otherwise cause based on the Impacts in Scope table further below. 

__Reward Calculation for Critical Level Reports__

For critical Smart Contract bugs, the reward amount is __10%__ of the funds directly affected up to a maximum of __USD $100,000__. The calculation of the amount of funds at risk is based on the time and date the bug report is submitted. However, a minimum reward of __USD $10,000__ is to be rewarded in order to incentivize security researchers against withholding a bug report.   
For critical web/app bugs, the reward amount is __10%__ of the funds directly affected up to a maximum of __USD $30,000__. The calculation of the amount of funds at risk is based on the time and date the bug report is submitted. However, a minimum reward of __USD $1,000__ is to be rewarded in order to incentivize security researchers against withholding a bug report.   

__Repeatable Attack Limitations__

In cases of smart contract vulnerabilities whereby the attacks can be repeated at certain time intervals, if the attack can be stopped by a configuration change, the total value-at-risk from the consecutive attacks is computed by adding up the losses incurred and applying the below discount factors:

| Time Since Attack 1     | Discount Factor     |
| ---------- | ---------- |
| 0 to 15 minutes       | 0%       |
| 15 to 30 minutes       | 25%       |
| 30 to 60 minutes       | 50%       |
| 60 to 120 minutes       | 75%       |
| > 120 minutes       | 100%       |

If the attack cannot be stopped by configuration changes, the discount factors are adjusted by 50% (i.e. 0% / 12.5% / 25% … ), with the terminal discount factor being 100% at 4 hours (from the initial attack).

__Previous Audits__

Synthetix has provided these completed audit review reports for reference. Any unfixed vulnerability mentioned in these reports are not eligible for a reward.
  - [https://github.com/Synthetixio/synthetix-docs/blob/master/content/releases.md](https://github.com/Synthetixio/synthetix-docs/blob/master/content/releases.md)
  -[ https://docs.synthetix.io/v/v3/for-developers/smart-contract-audits](https://docs.synthetix.io/v/v3/for-developers/smart-contract-audits)

__Feasibility Limitations__

Bug reports that involve one or more other protocols (e.g. utilising flash loans from a margin protocol or manipulating the spot prices on a DEX), either to make an attack more severe than it would be in isolation, or to achieve an attack that would otherwise be impossible or infeasible, would be out-of-scope. However, they will be considered within scope and categorised according to the program rules as long as all of the following are true:

  - Losses or other negative effects of the attack are inflicted on users who provide liquidity (whether for staking or trading) directly on contracts managed by Synthetix (i.e. vulnerabilities on the greater Synthetix Ecosystem partners and integrators are out of scope).
  - The losses or other negative effects could be prevented via changes to contracts that can be updated or modified.

In case an attack requires use of attackers’ own funds (in order to perform/execute a trade), and requires the attacker taking on economic or financial risk, then a discount is applied on the value-at risk based on the likelihood of an attack succeeding. The likelihood should be estimated by reference to reasonable assessment of the environment at the time of the bug bounty submission or by reference to the PoC. Synthetix has ultimate discretion in providing their opinion on the discount used and the eligibility of such disclosures to be considered within scope of the bounty program.

__Proof of Concept (PoC) Requirements__

A PoC is required for the following severity levels:
  - Critical
  - High

All PoCs submitted must comply with the Immunefi-wide [PoC Guidelines and Rules](https://immunefisupport.zendesk.com/hc/en-us/articles/9946217628561-Proof-of-Concept-PoC-Guidelines-and-Rules). Bug report submissions without a PoC when a PoC is required will not be provided with a reward.

__Reward Payment Terms__

As part of the bug bounty matching program, Optimism will contribute __52,500 OP__ tokens to match the rewards offered by Synthetix. This means that for every reward paid out by Synthetix to a security researcher, Optimism will provide an additional, matching reward, in OP tokens. The total reward pool for this program is __52,500 OP tokens__. The other 50% of the reward (if applicable for matching) will be paid by __Synthetix__ in __USDC__. 

Rewards are distributed according to the impact of the vulnerability based on the [Immunefi Vulnerability Severity Classification System v. 2.3](https://immunefi.com/immunefi-vulnerability-severity-classification-system-v2-3/). This is a simplified 4-level scale. The development of this scale took into consideration multiple factors that may affect a vulnerability and its likelihood of exploitation, but finalizes them largely by the impact that they cause.

The table below is mostly concerned with the consequence of a successful exploit. Keep in mind that if the exploit requires elevated privileges or uncommon user interaction, the level of the bug may be downgraded to reflect that or rejected. 

__Goodwill Payments__ 

This applies to the following severity and asset levels: 
  - Smart Contract - Low
  - Web/App - Medium
  - Web/App - Low

Synthetix is willing to offer discretionary “Goodwill Payments” for any bugs that fall under these categories and affect __TVL <$1,000__, 

Furthermore, if the value of the assets at risk cannot be estimated, then the bounty payment would be discretionary based on goodwill terms.


Synthetix

Resources & Documentation