So I just noticed this:

42859886 - 42842300 = 17586

The head blocks of our blockchains are 17586 apart during this snapshot. Because we both use the same tech, this implies that Steem has missed 17586 more blocks than Hive since inception.

Wow, I knew Steem was unstable...

But I really had no idea it was this bad. This puts things into perspective.

• 17586 blocks is 52758 seconds
• 52758 seconds is 879.3 minutes
• 879.3 minutes is 14.7 hours

That means in that in less than 2 months Steem has been down for almost 15 hours. This is wholly unacceptable, and due to the fact that many of the witnesses are not running the same code.

When a witness who doesn't support the freezing of accounts posts a transaction to the blockchain with operations from said frozen accounts, it's up to the other witnesses freezing those accounts to act and nullify that block. This causes rollbacks in the chain that we see the results of here.

OH, SWEET IRONY!

This means that the entire reason stated for freezing the accounts:

To protect the security of the chain...

is not only false, but actually the opposite is true. Justin Sun has turned the blockchain into a Steeming shitpile via freezing these accounts.

Steem is anything but secure.

Not just because he can freeze anyone's account for any reason, but because these missed blocks make the chain highly unstable.

But it doesn't stop there.

Because there are rumors that a new soft fork is going into effect (22.9999 whatever) that will freeze even more accounts. Which means there will be even more of a chance that blocks get missed. Unreal.

Conclusion

Wow... just wow. That is all.

Return from WOW: 17586 Block Difference Between Steem and Hive to edicted's Web3 Blog