Interlay
Program Overview
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.
For more information about Interlay, please visit https://interlay.io/.
Rewards by Threat Level
Rewards are distributed according to the impact of the vulnerability based on the 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 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.
The following vulnerabilities are not eligible for a reward:
- Audit reports: https://github.com/interlay/interbtc/tree/master/docs/audits
- Blockchain implementation issues: https://github.com/interlay/interbtc/issues
- Off-chain client issues: https://github.com/interlay/interbtc-clients/issues
- Security design limitations: https://spec.interlay.io/security_performance/xclaim-security.html and https://spec.interlay.io/security_performance/btcrelay-security.html
- Economic design limitations: https://spec.interlay.io/economics/incentives.html
For more information regarding the documentation, please refer to:
- Official docs: https://docs.interlay.io/#/
- Development environments:
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.
Blockchain/DLT
- Critical
- Level
- Up to USD $500,000
- Payout
- High
- Level
- USD $25,000
- Payout
- Medium
- Level
- USD $10,000
- Payout
- Low
- Level
- USD $2,500
- Payout
Smart Contract
- Critical
- Level
- Up to USD $500,000
- Payout
- High
- Level
- USD $25,000
- Payout
- Medium
- Level
- USD $10,000
- Payout
- Low
- Level
- USD $2,000
- Payout
Websites and Applications
- Critical
- Level
- USD $7,500
- Payout
- High
- Level
- USD $3,000
- Payout
- Medium
- Level
- USD $1,000
- Payout
Assets in scope
- Blockchain/DLT - Parachain implementationType
- Blockchain/DLT - ClientsType
- Websites and Applications - Kintsugi AppType
- Websites and Applications - Kusama APIType
- TargetWebsites and Applications - Interlay AppType
- TargetWebsites and Applications - Interlay APIType
All Blockchain/DLT of Interlay can be found at 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.
Impacts in scope
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.
Blockchain/DLT
- Network not being able to confirm new transactions (Total network shutdown)CriticalImpact
- Unintended permanent chain split requiring hard fork (Network partition requiring hard fork)CriticalImpact
- Direct loss of funds of 10% or more of all fundsCriticalImpact
- Permanent freezing of funds (fix requires hardfork) of 10% or more of all fundsCriticalImpact
- Unintended chain split (Network partition)HighImpact
- Transient consensus failuresHighImpact
- Direct loss of funds of less than 10% of all fundsHighImpact
- Permanent freezing of funds (fix requires hardfork) of less than 10% of all fundsHighImpact
- High compute consumption by validator/mining nodesMediumImpact
- Attacks against thin clientsMediumImpact
- DoS of greater than 30% of validator or miner nodes and does not shut down the networkMediumImpact
- RPC API crashMediumImpact
- DoS of greater than 10% but less than 30% of validator or miner nodes and does not shut down the networkLowImpact
- Underpricing transaction fees relative to computation timeLowImpact
Smart Contract
- Manipulation of governance voting result deviating from voted outcome and resulting in a direct change from intended effect of original resultsCriticalImpact
- Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield of 10% or more of all fundsCriticalImpact
- Permanent freezing of fundsCriticalImpact
- Protocol insolvencyCriticalImpact
- Theft of unclaimed yieldHighImpact
- Permanent freezing of unclaimed rewardsHighImpact
- Temporary freezing of funds for a minimum period of 1 dayHighImpact
- Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield less than 10% of all fundsHighImpact
- Permanent freezing of funds less than 10% of all fundsHighImpact
- Smart contract unable to operate due to lack of fundsMediumImpact
- Block stuffing for profitMediumImpact
- Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)MediumImpact
- Theft of gasMediumImpact
- Unbounded gas consumptionMediumImpact
- Contract fails to deliver promised returns, but doesn't lose valueLowImpact
- Permanent freezing of unclaimed yieldLowImpact
Websites and Applications
- Execute arbitrary system commandsCriticalImpact
- 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)CriticalImpact
- Taking down the applicationCriticalImpact
- 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.CriticalImpact
- Subdomain takeover with already-connected wallet interactionCriticalImpact
- Direct theft of user fundsCriticalImpact
- Malicious interactions with an already-connected wallet such as modifying transaction arguments or parameters, substituting contract addresses, submitting malicious transactionsCriticalImpact
- 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.HighImpact
- 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.HighImpact
- Improperly disclosing confidential user information such as email address, phone number, physical address, etc.HighImpact
- Subdomain takeover without already-connected wallet interactionHighImpact
- Changing non-sensitive details of other users (including modifying browser local storage) w/o already-connected wallet interaction and w/ up to one click of user interaction, such as changing the first/last name of user, or enabling/disabling notificationsMediumImpact
- Injecting/modifying the static content on the target application without Javascript (Reflected) such as reflected HTML injection or loading external site dataMediumImpact
- Redirecting users to malicious websites (Open Redirect)MediumImpact
Out of Scope & Rules
The following vulnerabilities are excluded from the rewards for this bug bounty program:
- Attacks that the reporter has already exploited themselves, leading to damage
- Attacks requiring access to leaked keys/credentials
- Attacks requiring access to privileged addresses (governance, strategist)
Smart Contracts and Blockchain
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Basic economic governance attacks (e.g. 51% attack)
- Lack of liquidity
- Best practice critiques
- Sybil attacks
- Centralization risks
Websites and Apps
- Theoretical vulnerabilities without any proof or demonstration
- Attacks requiring physical access to the victim device
- Attacks requiring access to the local network of the victim
- Reflected plain text injection ex: url parameters, path, etc.
- This does not exclude reflected HTML injection with or without javascript
- This does not exclude persistent plain text injection
- Self-XSS
- Captcha bypass using OCR without impact demonstration
- CSRF with no state modifying security impact (ex: logout CSRF)
- Missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”) without demonstration of impact
- Server-side non-confidential information disclosure such as IPs, server names, and most stack traces
- Vulnerabilities used only to enumerate or confirm the existence of users or tenants
- Vulnerabilities requiring un-prompted, in-app user actions that are not part of the normal app workflows
- Lack of SSL/TLS best practices
- DDoS vulnerabilities
- Feature requests
- Issues related to the frontend without concrete impact and PoC
- Best practices issues without concrete impact and PoC
- Vulnerabilities primarily caused by browser/plugin defects
- Leakage of non sensitive api keys ex: etherscan, Infura, Alchemy, etc.
- Any vulnerability exploit requiring browser bugs for exploitation. ex: CSP bypass
The following activities are prohibited by this bug bounty program:
- Any testing with mainnet or public testnet contracts; all testing should be done on private testnets
- Any testing with pricing oracles or third party smart contracts
- Attempting phishing or other social engineering attacks against our employees and/or customers
- Any testing with third party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks)
- Any denial of service attacks
- Automated testing of services that generates significant amounts of traffic
- Public disclosure of an unpatched vulnerability in an embargoed bounty