Live AMA, LiskHQ Answered to Questions About Consensus (Part3)
The non-stop AMA brought so many other interesting questions:
1) In the new dPoS proposal how you’ll prevent big whales from taking more than one forging slot?
One account can only have 1 forging slot. But a very large holder could have two accounts and have enough tokens so that both are forging delegates. This is not really avoidable and in my opinion more of a feature of PoS than a bug.
If a whale gets half the slots, he must have 50% of the voting LSK tokens. But you could argue that it is fair if 50% of the LSK tokens get half the forging slots.
2) Why did you chose 30 days for the fail-safe ban? isn’t it too long?
30 days is a conservative choice. It is meant as a fail-safe, if a whale loses their key, for instance. In most cases, voters should react fast enough to vote somebody out who is not forging.
3) Max said yesterday we will have enough scalability with the new block size of 15kb. Could you give more details about the current or future performance of the Lisk blockchain?
With 15kB blocks the Lisk blockchain allows for around 120 balance transfer per block or 1 million balance transfers per day. The proposed voting system should also significantly increase the number of Tx/s that are possible because vote weights do not need to be updated when balances change. But we will need to do some benchmarking once we have the implementation.
4) How much standby vote weight overall do you expect after introducing the new consensus?
We expect around 1M LSK in total standby weight. This is difficult to estimate because I don’t really know how much people will keep voting with the locking in place.
LiskHQ is planning to do soon another AMA and answer to many other questions, stay tuned!