All smart contracts of Livepeer can be found at [https://github.com/livepeer/arbitrum-lpt-bridge](https://github.com/livepeer/arbitrum-lpt-bridge), [https://github.com/livepeer/protocol/](https://github.com/livepeer/protocol/tree/confluence). However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

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.

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

Permanent freezing of funds

Insolvency

Unintended issuance of LPT on L1

Unexpected calls to functions that should only be called by authorized addresses (i.e. Governor)

Direct manipulation treasury voting that manipulate the outcome of the vote resulting in drained funds from the treasury

Theft of unclaimed yield

Permanent freezing of unclaimed yield

Temporary freezing of funds

Any unexpected balance inflation when transitioning between L1 and L2

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

Theft of gas

Unbounded gas consumption or any other gas drainage

Manipulation of protocol governance vote or treasury voting that does not effect the result of the vote

Smart contract has unexpected behavior but doesn’t lose value

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 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](https://code4rena.com/reports/2022-01-livepeer) 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__.

Livepeer

Resources & Documentation