You are viewing a single comment's thread from:

RE: Giving Hive A Second Look

in #hive4 years ago

Just read your newsletter about Hive/Steem through the archive - https://www.buildblockchain.tech/newsletter/issues/no-91-steems-demise-and-hives-rise

Great writeup and summary of events, thanks for that! For completeness sake, ... if you decide to stay here (who knows, maybe consider crossposting your newsletter?), some small factual incorrectnesses:

  • For months after its launch, no one mined any Steem except for Steemit Inc. This is not the case, quite fast after the launch others found out how to mine as well, albeit documentation was kept at a bare minimum. And Steemit Inc had fired up a ton of Amazon CPUs for POWwing (I base this of Bitcointalk threads).
  • When you use Steem to vote for block producers, it becomes locked for a minimum of two weeks. Correct would be to say: In order to participate in governance one could lockup Steem to gain influence. That "locked up" Steem can then only be "unlocked" in 13 equal weekly "unlocks". So every week 1/13 of the original locked up liquid Steem can be released again, so it actually would take 3 months more or less...

Cheers!

Sort:  

maybe consider crossposting your newsletter

Yes! I did, and plan on continuing to do so. Might build a little script to automate it for me as well.

https://peakd.com/hive/@bendi/steem-s-demise-and-hive-s-rise-build-blockchain-issue-no-91

some small factual incorrectnesses

Ahh, thanks for these clarifications. Part of it comes from me not knowing the intricate details, but part of it also comes from trying to make it comprehensible-yet-terse for an audience that doesn't either. It's always a bit of a balancing act trying to do that, and it's lossy compression for sure.