eBTC
eBTC is a collateralized crypto asset soft pegged to the price of Bitcoin and built on the Ethereum network. It is based on the Liquity protocol and backed exclusively by Staked Ether (stETH). The protocol is designed with an immutable core with minimized counterparty reliance and governance.
Triaged by Immunefi
PoC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Manipulation of governance voting result deviating from voted outcome and resulting in a direct change from intended effect of original results
Direct theft of at least 2 stETH worth of any user funds, whether at-rest or in-motion, other than unclaimed yield
Permanent freezing of funds
Protocol insolvency
Theft of unclaimed yield
Permanent freezing of unclaimed yield
Temporary freezing of funds for at least 15 minutes
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
Out of scope
- If we’re running public tests, then we should not receive reports that are a direct copy of the result of our own testing. This includes information derived branches and PRs on the public repo. This is to prevent reports that are a front-run of our own internal due diligence.
- Findings that share a root cause with properties broken by a public fuzz suite run will be considered known at the time that the fuzzer broke the property.
- Findings that become public knowledge are not considered valid vulnerabilities if the team was already aware of them.
- Deadline based findings should be considered out of scope, attacks tied to MEV supply chain should not be viewed as valid, as they impact end users due to their actions and not the systems functionality.
- Findings tied to stETH rebasing should not be accepted unless they deal with the math tied to PYS and end user appreciation
- eBTC is not responsible to prevent losses in case of slashings
- Impacts that are known, and or have been disputed via previous contests, bounties, etc..
Smart Contract specific
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Impacts requiring basic economic and governance attacks (e.g. 51% attack)
- Lack of liquidity impacts
- Impacts from Sybil attacks
- Impacts involving centralization risks
All categories
- Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
- Impacts caused by attacks requiring access to leaked keys/credentials
- Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
- Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
- Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
- Best practice recommendations
- Feature requests
- Impacts on test files and configuration files unless stated otherwise in the bug bounty program
- Impacts requiring phishing or other social engineering attacks against project's employees and/or customers