All Blockchain/DLT of Interlay can be found at [https://github.com/interlay](https://github.com/interlay). However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

If an impact can be caused to any other asset managed by Interlay that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project. This only applies to Critical and High impacts.

A collaborative effort of pioneers around the globe working together on bringing Bitcoin to any blockchain. Invest, earn and pay with your Bitcoin on any blockchain. Radically open and secured by insurance.

Network not being able to confirm new transactions (Total network shutdown)

Unintended permanent chain split requiring hard fork (Network partition requiring hard fork)

Direct loss of funds of 10% or more of all funds

Permanent freezing of funds (fix requires hardfork) of 10% or more of all funds

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 of 10% or more of all funds

Permanent freezing of funds

Protocol insolvency

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)

Taking down the application

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.

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

Unintended chain split (Network partition)

Transient consensus failures

Direct loss of funds of less than 10% but more than 1% of all funds

Permanent freezing of funds (fix requires hardfork) of less than 10% of all funds

Theft of unclaimed yield

Temporary freezing of funds for a minimum period of 1 day

Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield less than 10% but more than 5% of all funds

Permanent freezing of funds less than 10% of all funds

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 or 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

High compute consumption by validator/mining nodes

Attacks against thin clients

DoS of greater than 30% of validator or miner nodes and does not shut down the network

RPC API crash

Smart contract unable to operate due to lack of funds

Theft of gas

Unbounded gas consumption

Direct loss of funds of less than 1% of all funds

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 websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.

All web/app bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. All Smart Contracts and Blockchain/DLT bug reports require a PoC to be eligible for a reward. Explanations and statements are not accepted as PoC and code is required.

Critical, high, and medium smart contract and blockchain/DLT vulnerabilities are capped at 10% of economic damage, primarily taking into consideration funds at risk, but also PR and branding aspects, at the discretion of the team.  However, there is a minimum Critical reward of USD 5 000, minimum High reward of USD 1500, and minimum Medium reward of USD 750. 

The following vulnerabilities are not eligible for a reward:

  - Audit reports: [https://github.com/interlay/interbtc/tree/master/docs/audits](https://github.com/interlay/interbtc/tree/master/docs/audits) 
  - Blockchain implementation issues: [https://github.com/interlay/interbtc/issues](https://github.com/interlay/interbtc/issues)
  - Off-chain client issues: [https://github.com/interlay/interbtc-clients/issues](https://github.com/interlay/interbtc-clients/issues) 
  - Security design limitations: [https://spec.interlay.io/security_performance/xclaim-security.html](https://spec.interlay.io/security_performance/xclaim-security.html) and [https://spec.interlay.io/security_performance/btcrelay-security.html](https://spec.interlay.io/security_performance/btcrelay-security.html) 
  - Economic design limitations: [https://spec.interlay.io/economics/incentives.html](https://spec.interlay.io/economics/incentives.html) 

For more information regarding the documentation, please refer to:
  - Official docs: [https://docs.interlay.io/#/](https://docs.interlay.io/#/) 
  - Development environments:
    - [https://github.com/interlay/interbtc-api/#development](https://github.com/interlay/interbtc-api/#development)
    - [https://github.com/interlay/interbtc-clients#development](https://github.com/interlay/interbtc-clients#development)
    - [https://github.com/interlay/interbtc#testing](https://github.com/interlay/interbtc#testing)

Payouts are handled by the __Interlay__ team directly and are denominated in USD. However, payouts are done in __KINT, INTR or USDC__, with the choice of the ratio at the discretion of the team.

Interlay

Resources & Documentation