Editors Note: This article comes fromWebX Labs Daily (ID: gh_3bc595acebaf), reprinted by Odaily with authorization.
WebX Labs Daily (ID: gh_3bc595acebaf)
, reprinted by Odaily with authorization. image description PoS project staking situation secondary title 20075: The first unlucky egg On the second night of the successful launch of the ETH2.0 beacon chain mainnet, the first person who was punished by the system appeared: validator 20075. For this, the validator paid a Slash penalty of 0.2344 ETH, and the balance became 31.77 ETH. The validator 20075 received this Slash ticket because of double-signature behavior, that is, the validator selected two different blocks in one slot. And whether it is due to node operation errors or intentional actions, this behavior has had a certain adverse impact on the main network. According to later statistics, as many as 600 validators were issued Slash tickets within a day after the Beacon Chain mainnet went live. This caused a controversy in the community: How can a validator be fined for doing a good job? Compared with the Slash penalty in other PoS public chains, the experience of validator 20075 is considered good. The tzscan browser of the Tezos community records miners who have been slashed. There is a record of the highest penalty of 24,256 XTZ, which means that the miner was fined about 170,000 in less than 1 minute. Coincidentally, in June 2019, on Cosmos, which is also cross-chain, a company named Cosmospool.org was deducted 900,000 worth of tokens by the system that day because of the exception of two different blocks. secondary title What happens when Slash slashes occur 1. Privately trying to fork 2. Double signing behavior Double-signing behavior means that at the same height, a node verifies blocks on different chains; or it means that at the same height, a node signs multiple signatures on the same block on one chain. Taking Cosmos as an example, if the nodes offline time is greater than the time when 9500 blocks are generated in the network (about 18 hours), the node will be punished by Slash. But being offline for a short time will not be slashed by Slash. The mechanism of Slash punishment in Polkadot In different networks, these punishment mechanisms may be different. For example, Filecoin is not a PoS consensus mechanism, but the mechanism is similar. In PoS consensus, staking is token, but staking in Filecoin is storage space. The difference from PoS is that tokens can be slashed, but storage space cannot. Therefore, the system will lower the rights of nodes that do not act or even do evil, and reduce the income. No matter what the scenario or mechanism is, the core principle of Slash remains the same, that is, any behavior that damages the stable operation of the main network will be punished. secondary title What is the core purpose of establishing the Slash penalty mechanism? Then, in order for these verifiers to work normally and stably, in addition to the normal incentive mechanism, it is also necessary to bind the interests of the verifiers, that is, they must deposit 32ETH as a deposit to be able to run the verification program and obtain corresponding rewards. reward. The incentive here is positive. In addition, there is also a reverse incentive to suppress the malicious behavior of bad intentions. There are generally two ways of reverse incentives. One is to deduct the node deposit, which is the Slash penalty, and the other is to reduce Even short-term deprivation of the nodes income, the current difficulty in the design of this suppression method lies in how to include and reflect the consideration of malicious behavior in the reward liquidation. In order to prevent attacks like no stake, the PoS mechanism introduces a Slash penalty mechanism to suppress nodes that maliciously attempt to create splits and chaos. Generally, such a mechanism will also appear with a Byzantine fault tolerance mechanism. Slash is a typical mechanism for the later stage of Staking change. By reducing the deterrence of pledged Token in Staking, the purpose of further maintaining system security is achieved. Compared with PoW, Staking-Slash makes the reward and punishment mechanism of PoS more perfect. In PoW, most of the punishment for being evil is missing rewards. In PoS, in addition to missing the reward, you also face the loss of the principal. secondary titleSince 2019, PoS and the Staking Economy behind it have gradually entered the mainstream view, and few people mention the classic PoW. With the gradual landing of the two major PoS public chain IPs, ETH2.0 and Polkadot this year, this trend has reached its peak. Up to now, the ETH pledged by the ETH2.0 beacon chain deposit contract has reached 1.38 million. Polkadot Reached 760 million pieces. This wave has encouraged a large number of currency holders to hold 32 ETH to become validators, but the problem is that most of the attention of the outside world is almost on the skyrocketing ETH market and pledges, and they do not fully understand the risks involved.
Originally, the Slash penalty for ETH2.0 started from 1ETH, but since everyone needs time to adapt to the rules in the early stage, the probability of making mistakes may increase, so the current penalty has been reduced, and it will definitely be adjusted as long as it runs normally in the future It starts with 1 ETH, and as long as many people are punished by Slash, the penalty will continue to increase. It should be noted that this penalty is taken directly from the 32 ETH you pledged, and the verifier cannot reset the entire verifier node by completing or replacing the original pledged coins. When the number of ETH is deducted below 16, the validator node will be automatically kicked out.
image description
There is a very serious problem in the pure PoS mechanism, Nothing at Stake (no stake). Take the fork as an example. If a node wants to split the community and redistribute power through the fork, the node will inform other nodes that the fork will not affect their interests, but will benefit them. Bewitched, they all agreed. Although the fork was finally completed, the community projects suffered heavy losses, and the final result was not what everyone wanted. But there is nothing the mainnet can do about it.
