Editor’s node: for now, this is less a specific proposal and more an invitation for general brainstorming.
There are many different ways to conceptualize what it is exactly that proof-of-stake systems are doing, or should be doing. To wit:
- A simple, consensus-mechanism-focused understanding would take them to be simply an anti-Sybil mechanism, almost a direct replacement for proof-of-work, where stake needs to be locked in order to guarantee the possibility of slashing, and thus so-called “cryptoeconomic security”. This is the understanding from the original “Slasher” blog post, and it’s still probably the dominant one. From this perspective, proof-of-stake just means some way to allocate voting weight in consensus, usually combined with a short lock period and slashing for misbehaviour in said consensus.
- The concept of “locked stake providing cryptoeconomic security” can be generalized to cover more services, as described e.g. in the rainbow staking post, and logically modeled as in the message logic paper. From this perspective, proof-of-stake just means some kind of token locked for some time that can be partially or fully burned (slashed) if a proof of misbehavior w.r.t. a service commitment is submitted to the appropriate location.
- From a more economic perspective, the “locked stake” or bond aspect of proof-of-stake can be understood as a way to redistribute ownership to participants who lock up their tokens (and perhaps provide services to the network), as compared to participants who don’t. This also gives the network more control over the liquidity of its token supply over time. This can be generalized into a kind of target maturity curve as described here. From this perspective, proof-of-stake just means that tokens can be locked in “bonds”, which typically (a) mature after a fixed period of time and (b) pay interest.
These understandings are mostly separable and complementary, but should be understood as having distinct goals and thus design criteria. I think (3) can be further split into two distinct sub-goals:
- Give the network the ability to control its own liquid token supply over time through regulation of interest rates. This has some similarities to sovereign bond markets and central bank interest rate controls.
- Give the network the ability to redistribute more ownership to parties who have made more long-term commitments which align their interests with those of the network. The aim here is to indirectly encourage those parties to take actions which benefit the network as a whole, as they stand to benefit, and to discourage actions which sacrifice long-term sustainability for short-term benefit, as it would be more difficult to exit. A great advantage of this method, as compared to other methods for rewarding contributions, is that it does not require measurement.
(2) contains some interesting design questions, such as:
- Should these bonds be transferable (before term), non-transferable, or both?
- Intermediate options also exist, e.g. governance-approved transfers, periodic auctions, etc.
- Should interest rates be fixed or variable?
- Should interest be paid periodically, at redemption, or only on exit?
- Can these bonds be used as collateral for service commitments, borrowing, or other things?
- An interesting option is to let them be used as collateral to borrow from the network, if the network itself has a supply of other assets. Some control mechanisms would be necessary to allocate limited borrowable assets in this case.
- Should it be possible to sell a bond early (back to the protocol, or to a third party), and what should the penalty be for doing so?
- A cubic-slashing-like mechanism could potentially be used to set penalties here.
- What kinds of network-legible identity mechanisms could be incorporated, and what would be the benefits and drawbacks of doing so?
- Should it be possible to permanently forfeit the right to exit?