Originally posted on the Elixxir blog.
The current definition of Proof of Stake is too broad and generic to be useful. It does not imply any information about the security or insecurity of a platform. This definition does a disservice to all parties—the users, the systems, the experts—because instead of discussions addressing the issues, we spend our time bike-shedding and making untrue assumptions about system properties.
After the back-and-forth on Twitter about some of the details in Elixxir’s technical brief, I feel compelled to build on that conversation and attempt to critique the current definition of Proof of Stake (PoS). As this is my first time publicly participating in this community, I welcome conversation and feedback from community members to help further refine the definition from here. I haven’t received any takers so far, but I’m hoping that will change and I am grateful for the initial critique.
Ignoring the “PoS is anything not PoW” trolls, most high-level definitions of PoS are minorvariations on the following:
“PoS refers to the entire class of mechanisms whereby the amount of cryptocurrency you hold determines the extent to which you can participate in consensus.”
To my mind, there are 3 main problems with this definition:
Problem 1: The primary problem is that it is so high-level that it can only be valid within the narrow context of the protocol and therefore ignores very real externalities.
Problem 2: The definition makes no distinction between systems with different properties.
Problem 3: Systems with similar non-stake mechanisms end up getting unfairly grouped together.
To sum up: when someone labels a platform PoS, it doesn’t tell you anything other than that the platform uses the word "stake" somewhere. The platforms I listed are only a small sample of what is out there, with different models, different crypto, different security properties, and different performance. Putting everything under one oversimplified banner is confusing at best. We are getting triggered by the color of the woodshed out back, and not focusing on the architecture of the house.
Let’s start with the definition I was working from, as it’s clearly not refined enough either:
The age or amount of stake is an input to the consensus mechanism.
With the exception of Dash and Avalanche, this describes all the systems mentioned in my third point above. Two papers that offered their own definitions emerged from the discussion of those systems. One from Bitfury:
Instead of mining power, the probability to create a block and receive the associated reward is proportional to a user’s ownership stake in the system.
And one discussing Chain of Authority (CoA):
Mechanisms that give the decision-making power regarding the continuation of the ledger history to entities who possess coins within the system.
Bitfury’s definition excludes age and deposit mechanisms. In that sense, it is the most specific. I would like to further distinguish according to the selection mechanism (e.g., VRF vs. VDF vs. some other mechanism), but I will stop here. If you have clout in this community and are interested in working on useful definitions, please let me know.
Neither. There is no “Proof of” in Elixxir.
Folks out there assumed the worst and went straight to the bikeshed after reading the word “stake” in our Technical Brief. The words “Proof of” are nowhere in the Elixxir Technical Brief by design, but we are taking this one step further by replacing the term “stake” with “bonded deposit” in all of our documentation. We defined that in terms of a number of tokens, but replacing it with a bonded deposit in USD, ETH, or BTC would be acceptable for purposes of the property we are trying to achieve with this term. Simply put, we want to ensure that you have “skin in the game” to lose when you violate the protocol, and the amount does not give you more or less influence in the consensus in Elixxir.
As far as I know, the design of Elixxir diverges from all other existing platforms in multiple ways.
For more details, check out the technical brief. We will release more information when we publish the white paper.
