Livepeer is a decentralized video streaming network built on the Ethereum blockchain. The Livepeer network already includes over 70,000 GPUs, which is enough aggregated power to encode all of the video streaming through Twitch, YouTube and Facebook combined. Through the power of open source software, the harnessing of underutilized resources like compute and bandwidth, and the use of cryptoeconomic incentives for bootstrapping and participation, there is an opportunity to deliver an infrastructure that can power video streaming applications at a highly efficient price, and infinite scale.
For more information about Livepeer, please visit https://livepeer.org/.
This bug bounty program is focused on their smart contracts and is focused on preventing:
- Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
- Permanent freezing of funds
- Unintended issuance of LPT on L1
- Unexpected calls to functions that should only be called by authorized addresses (i.e. Governor)
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 and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.
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. Explanations and statements are not accepted as PoC and code is required.
All vulnerabilities marked in the security review are not eligible for a reward.
Livepeer requires KYC to be done for all bug bounty hunters submitting a report and wanting a reward. The information needed is Visual Proof of Identity. The collection of this information will be done by the project team.
Rewards for critical vulnerabilities are capped at 10% of the economic damage (following the linked examples) with the primary focus on possible loss of funds for Orchestrators, Delegators and Broadcasters at the Smart Contract level only. If there is a repeatable attack, only the first attack is considered unless further attacks cannot be mitigated via an upgrade or pause.
Rewards for high vulnerabilities will depend on the amount of unclaimed yield that is on the line and how long the funds can be frozen.
Payouts are handled by the Livepeer team directly and are denominated in USD. However, payouts are done in USDC.
- Up to USD $40,000
- Up to USD $15,000
- USD $2,500
- USD $1,000
Assets in scope
- Smart Contract - GovernorType
- Smart Contract - ControllerType
- Smart Contract - LivepeerTokenType
- Smart Contract - MinterType
- Smart Contract - Bonding Manager (Proxy)Type
- Smart Contract - Bonding Manager (Target)Type
- Smart Contract - TicketBroker (Proxy)Type
- Smart Contract - TicketBroker (Target)Type
- Smart Contract - RoundsManager (Proxy)Type
- Smart Contract - RoundsManager (Target)Type
- Smart Contract - ServiceRegistry (Proxy)Type
- Smart Contract - ServiceRegistry (Target)Type
- Smart Contract - SortedDoublyLLType
- Smart Contract - PollCreatorType
- Smart Contract - MerkleSnapshotType
- Smart Contract - DelegatorPoolType
- Smart Contract - L2LPTDataCacheType
- Smart Contract - L2PTGatewayType
- Smart Contract - L2Migrator (Proxy)Type
- Smart Contract - L2Migrator (Target)Type
- Smart Contract - L1EscrowType
- Smart Contract - L1LPTDataCacheType
- Smart Contract - L1LPTGatewayType
- Smart Contract - L1MigratorType
- Smart Contract - BridgeMinterType
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.
- Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yieldCriticalImpact
- Permanent freezing of fundsCriticalImpact
- Unintended issuance of LPT on L1CriticalImpact
- Unexpected calls to functions that should only be called by authorized addresses (i.e. Governor)CriticalImpact
- Theft of unclaimed yieldHighImpact
- Permanent freezing of unclaimed yieldHighImpact
- Temporary freezing of fundsHighImpact
- Any unexpected balance inflation when transitioning between L1 and L2HighImpact
- Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)MediumImpact
- Theft of gasMediumImpact
- Unbounded gas consumption or any other gas drainageMediumImpact
- Smart contract has unexpected behavior but doesn’t lose valueLowImpact
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
- Oracle failure/manipulation
- Consensus failure
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