Ethereum’s Thorny Path to PoS

Ethereum’s Thorny Path to PoS

Yesterday Vitalik Buterin, one of the masterminds behind Ethereum, went on a 75-tweet spree to talk about Casper, Ethereum’s planned proof-of-stake consensus protocol.

To address widespread misinformation and confusion surrounding Casper, Vitalik Buterin shared the history and state of Casper research, including the war between its two versions, design issues and more.

A deeper dive into consensus algorithms

As an alternative to proof-of-work, Casper belongs in the category of proof-of-stake algorithms. PoW establishes network consensus by measuring the amount of computational resources expended to support a particular chain of transactions. PoS seeks to replace physical mining with CPUs, GPUs and ASICs by measuring economic resources committed to a particular history.

PoS is believed to be superior to PoW in terms of security because the cost of an attack on a PoS system is much higher. An attack on a PoW system incurs the cost of electricity expended and hardware deterioration, which means it can be repeated once and once again with the attacker suffering only partial costs. PoS, however, does not allow for repeated attacks as ill-used resources are burnt as penalty, which provides a major disincentive for bad actors.

Two major flaws

However, PoS cannot be built simply by copying principles and intuitions from PoW. PoW uses computing power as its voting resource — a resource that once expended cannot be replicated. Therefore, in the event of a fork, miners need to commit to one, not both. A fork in a PoS system, however, creates a copy of a user’s current resources, which means that a validator can vote on both forks. When one of the forks is abandoned, the validator loses only forked resources and retains the ones in the main chain. This is called the Nothing at Stake problem.

Long-range attacks are another flaw that pose a threat to a PoS system’s integrity. A 51% attack on a PoW system is executed by creating a longer fraudulent chain that can go back up to 6 blocks. This limitation is imposed by the amount of computational power attackers can potentially have at their disposal. There are no such limitations in PoS systems, and an attack can start far deep into the chain. This is why it is called a long-range attack.

Casper to the rescue

Casper seeks to eliminate these threats. At one point in time, however, Casper research split into two. Vitalik and his fellow developer Vlad Zamfir had certain disagreements on how to cope with these flaws. Thus, two versions of Casper were born: Vitalik’s Friendly Finality Gadget Casper and Vlad’s Correct-by-Construction Casper.

A PoS protocol is still to be fully implemented on the Ethereum network, but we can hope that Casper will inherit only the best out of both of its versions.

By continuing to browse, you agree to the use of cookies. Read Privacy Policy to know more or withdraw your consent.