Protocol Paused For Bug Fix Upgrade - 5/26/18 9:00pm EDT - (UPDATE: Resumed at 5/27/18 2:30pm EDT)


Hi everyone. This announcement is to let you know that we have identified a bug in the Livepeer protocol smart contracts, and will be conducting a fix. This is a non-critical bug that remains unexploited at this time. After some analysis however, we have decided to pause the protocol so that we can prepare a fix, test it, and get it deployed, without putting any user’s protocol role or tokens at risk. While Livepeer is still in the alpha testing stage, this sort of issue is fully expected, and we have built these upgrade and bug fix mechanisms for exactly this purpose. It is important for us to mitigate risks for our early protocol participants as much as possible.

The estimated duration of the protocol pause is 2 days. However it is possible that the protocol will be resumed quicker, avoiding the need to miss a single protocol round.

During the paused period, the protocol will be inactive and protocol parameters will stay the same. This means any interaction with the protocol will be ineffective. For delegators, your token will stay bonded but will receive no rewards because there will be no round progression. For transcoders, your nodes will not be able to initialize round or call reward, and there will be no token reward minted. However, non-participating tokens can still be transferred as usual. Broadcasters are urged to continue using Rinkeby to test and develop. The Livepeer team is working hard to fix the bug, and we will be in constant communication with updates. Expect a full post-mortem with details of the issue and remedy after the fix has been deployed and verified. If you notice any issues, please report to the discord channel at, and check here for updates.

Transcoder Campaign: 0x88 Hyper Transcoder

The protocol patch has been tested, deployed, and the protocol is unpaused and active again as of 2:30pm EDT on 5/27/18.

A full post mortem will follow this week with details around the bug, the fix, and steps going forward. As a reminder, this sort of incident is expected during the alpha stage of the project, and it is the exact reason that upgrade and bug fix mechanisms are built into the protocol.

Thanks to everyone who pulled extra hours over a holiday weekend to push through the fix here.