2018-04-15 EOS GO
Sam Sapoznick 发文讨论BP期限的问题,感觉挺有道理的
Block Producer Term Limits(区块生产者任期限制)
Summary: Term limits (enforced rotation of position, such as employed for some political positions, e.g. the US presidency) are one method to combat the entrenchment of bad actors.
总体来说:任期限制(强制轮换职位,例如用于某些政治职位,例如美国总统职位)是一种对付不良行为者作恶的方法。
In an EOS.IO context, if BP term limits of n years length are imposed, some of the effects are:
在EOS.IO背景下,如果施加n年的BP期限限制,将会产生一些影响是:
Makes it considerably more difficult for any single entity or faction to monopolize one or more Block Producer slots.
使任何单个实体或派系垄断一个或多个BP位置变得相当困难
Imposes an ongoing infrastructure cost penalty on the blockchain equal to 1/n per year, where n is the duration of term limit in years. (E.g. a 4-year term limit requires 1/4 = 25% of the blockchain hardware & human resources to be replaced every year.)
在区块链上施加等于每年1 / n的持续基础设施成本损失,其中n是以年为单位的期限限制。 (例如,4年期限要求每年需要更换1/4 = 25%的区块链硬件和人力资源。)
Discourages any block producer from taking a long-term view of their participation. A BP's effective time horizon is limited to roughly n-1 years. (Though some argue that this is a positive, it is also a negative because term limits work against both good and bad actors.)
阻止任何区块生产者长期看待他们的参与。 BP的有效时间范围限制在大约n-1年。 (尽管有人认为这是积极的,但它也是一个消极因素,因为期限限制对好人和坏人都有效。)
"Lame duck" effects on BPs who are due to be removed in any given year: they have reduced incentive to work hard to preserve the quality of their operations and their reputation as their term limit approaches.
对任何一年将被移除的BP来说都会带来“跛脚鸭(lame duck)”的影响:他们减少了激励,就会变得没有动力保持其业务质量和声誉,因为他们的任期接近结束。
The shorter the term limit, the more incentive there is for a BP to try to think up "short term plays," i.e. manipulations to try to maximize profit before exiting the system. Longer term limits (or no term limits) open up the field for a longer-term steady-state mindset and operational attitude for BPs.
期限越短,BP就越有可能尝试去思考“短期行为”,即在退出系统之前尝试进行最大化利润的操纵。较长期的限制(或没有任何期限限制)为BP的长期稳定的心态和操作态度成为可能。
My current point of view:
I think EOS.IO software should offer configurable BP term limits as an optional feature, with a range from 1 to 100 years and the ability to disable term limits entirely.
我目前的观点:
我认为EOS.IO软件应该提供可配置的BP期限限制作为可选功能,范围从1到100年,并且可以完全不用限制。
For the first EOS.IO main public chain, if community consensus favors term limits I argue they should be not shorter than 4 years, to reduce both the capital costs and potential network-instability risks of too-high turnover rates.
A default setting of 7 years may be a suitable trade-off in the balance of stability vs. rotation of responsibility.
对于第一个EOS.IO主要公共链,如果社区共识支持期限,我认为它们应该不低于4年,以降低成本和周转率的潜在网络不稳定风险。
7年的默认设置可能是稳定性与责任轮换之间平衡的一个合适的数字。