All Strike Finance code can be found at [https://github.com/StrikeFinance](https://github.com/StrikeFinance). Documentation and further resources can be found at [https://docs.strike.org/](https://docs.strike.org/) 

Strike is an autonomous and decentralized money market that enables variable based rates for supplying digital asset collaterals to the protocol and from borrowing digital assets from the protocol with over-collateralized assets. 

Manipulation of governance voting result deviating from voted outcome and resulting in a direct change from intended effect of original results

Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield

Direct theft of any user NFTs, whether at-rest or in-motion, other than unclaimed royalties

Permanent freezing of funds

Permanent freezing of NFTs

Unauthorized minting of NFTs

Predictable or manipulable RNG that results in abuse of the principal or NFT

Unintended alteration of what the NFT represents (e.g. token URI, payload, artistic content)

Protocol insolvency

Execute arbitrary system commands

Retrieve sensitive data/files from a running server, such as:   etc, shadow; database passwords; blockchain keys (this does not include non-sensitive environment variables open source code, or usernames); Taking down the application/taking down the NFT URI

Taking state-modifying authenticated actions (with or without blockchain state interaction) on behalf of other users without any interaction by that user, such as: Changing registration information; Commenting; Voting; Making trades; Withdrawals, etc.

Changing NFT metadata

Subdomain takeover with already-connected wallet interaction

Direct theft of user funds

Malicious interactions with an already-connected wallet, such as:  Modifying transaction arguments or parameters; Substituting contract addresses; Submitting malicious transactions

Direct theft of user NFTs

Injection of malicious HTML or XSS through metadata

Theft of unclaimed yield

Theft of unclaimed royalties

Permanent freezing of unclaimed yield

Permanent freezing of unclaimed royalties

Temporary freezing of funds

Temporary freezing of NFTs

Injecting/modifying the static content on the target application without JavaScript (persistent), such as:  HTML injection without JavaScript; Replacing existing text with arbitrary text; Arbitrary file uploads, etc

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; Password of the victim etc.

Improperly disclosing confidential user information, such as:  Email address; Phone number; Physical address, etc.

Subdomain takeover without already-connected wallet interaction

Smart contract unable to operate due to lack of token funds

Block stuffing

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

Theft of gas

Unbounded gas consumption

Changing non-sensitive details of users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as: Changing the first/last name of user; Enabling/disabling notifications

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)

Contract fails to deliver promised returns, but doesn't lose value

Changing details of users (including modifying browser local storage) without already-connected wallet interaction and with significant user interaction, such as:  Iframing leading to modifying the backend/browser state (must demonstrate impact with PoC)

Taking over broken or expired outgoing links, such as:  Social media handles, etc.

Temporarily disabling user to access target site, such as:  Locking up the victim from login; Cookie bombing, etc.

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 of the vulnerability based on the [Immunefi Vulnerability Severity Classification System V2.3](https://immunefi.com/immunefi-vulnerability-severity-classification-system-v2-3/). 
For critical smart contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD 50 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.

__Repeatable Attack Limitations__

  - If the smart contract where the vulnerability exists can be upgraded or paused, only the initial attacks within the first hour will be considered for a reward. This is because the project can mitigate the risk of further exploitation by upgrading or pausing the component where the vulnerability exists. The reward amount will depend on the severity of the impact and the funds at risk. 

  - For critical repeatable attacks on smart contracts that can not be upgraded or paused, the project will consider the cumulative impact of the repeatable attacks for a reward. This is because the project cannot prevent the attacker from repeatedly exploiting the vulnerability until all funds are drained and/or other irreversible damage is done. Therefore, this warrants a reward equivalent to 10% of funds at risk, capped at the maximum critical reward. 

__Reward Calculation for High Level Reports__

  - High vulnerabilities concerning theft/permanent freezing of unclaimed yield/royalties are considered at the full amount of funds at risk, capped at the maximum high reward of USD 10 000. This is to incentivize security researchers to uncover and responsibly disclose vulnerabilities that may have not have significant monetary value today, but could still be damaging to the project if it goes unaddressed.   

  - In the event of temporary freezing, the reward increases at a multiplier of two from the full frozen value for every additional 24h that the funds are temporarily frozen, up until a max cap of the high reward. This is because as the duration of the freezing lenghents, the potential for greater damage and subsequent reputational harm intensifies. Thus, by increasing the reward proportionally with the frozen duration, the project ensures stronger incentives for bug disclosure of this nature.      

For critical web/apps bug reports will be rewarded with __USD 15 000__ only if the impact leads to:

  - A loss of funds involving an attack that does not require any user action
  - Unauthorized minting of tokens on-chain
  - Private key or private key generation leakage leading to unauthorized access to user funds 

All other impacts that would be classified as Critical would be rewarded a flat amount of __USD 5 000__. The rest of the severity levels are paid out according to the Impact in Scope table.

__Reward Payment Terms__

Payouts are handled by the __Strike Finance__ team directly and are denominated in __USD__. However, payments are done in __STRK__.

The calculation of the net amount rewarded is based on the average price between CoinMarketCap.com and CoinGecko.com at the time the bug report was submitted. No adjustments are made based on liquidity availability. 


Strike Finance

Resources & Documentation