Steem and the 2020 Hive Fork: Lessons for Blockchain Social Media
Steem proved that a blockchain could support frequent posts, votes, and token rewards, but its history is more useful as a governance case study than as a template to copy. The network's stake-weighted control concentrated influence, and a 2020 dispute over that control led much of the established community to launch the independent Hive chain. Steem still exists, but descriptions of its original ecosystem should be read in that historical context.
How Steem connected publishing to token rewards
Launched in 2016, Steem stored social actions on-chain and let applications such as Steemit present them as a familiar publishing feed. Its economic system combined liquid STEEM, influence-bearing Steem Power, and Steem Backed Dollars (SBD), whose price mechanism targeted rather than guaranteed a US-dollar value. Authors and curators received newly issued tokens according to stake-weighted votes and protocol rules.
That design removed payment-card fees from tiny rewards and made each reward auditable, but it did not make quality objective. Large stakeholders could direct more of the reward pool, users could coordinate votes, and token-price swings changed the real value of a payout. A product considering the same model should ask how it resists vote buying, self-voting, collusion, spam, and wealthy accounts dominating discovery.
Delegated proof of stake made governance the security boundary
Steem used delegated proof of stake (DPoS): stakeholders elected a small set of witnesses to produce blocks and approve network changes. This supported fast, fee-free user actions, yet it also meant that control of voting stake could quickly change the active witness set. The crucial security question was therefore not only whether nodes ran correct software, but who could coordinate enough stake to govern the chain.
Applications also depended on infrastructure outside consensus: web front ends, image hosting, account recovery services, exchanges, and developer funding. Calling a publishing product decentralized is therefore incomplete unless it explains which parts users can replace and how they recover their content and keys if an operator disappears.
The 2020 control dispute and Hive hard fork
In 2020, Justin Sun's acquisition of Steemit Inc. brought control of a large token position into dispute. Community witnesses and Sun-aligned participants made competing governance changes, and exchange-controlled customer tokens were temporarily used in witness voting. Whatever one's view of the participants, the episode exposed a concrete DPoS risk: custodians may possess governance power that depositors did not expect them to exercise.
Community developers announced Hive in March 2020 and initialized it from Steem's state while excluding Steemit Inc.'s disputed stake from the new chain. From then on, Steem and Hive were separate networks with separate governance and assets; an account name or old history on both chains did not make their later transactions interchangeable. Many projects and community members moved to Hive, while Steem continued as a distinct, smaller ecosystem.
What builders should take from Steem
Token rewards can bootstrap activity, but they also attract behavior optimized for rewards rather than good conversation. Before adopting such a system, define who may change reward formulas, how delegated votes are disclosed, whether custodial balances can vote, how users export content, and how a contentious fork treats balances and identifiers. Those are product and governance requirements, not details to postpone until a crisis.
For primary material, consult the Steem Bluepaper, the current Steem developer portal, Hive's contemporary launch announcement, and the Hive developer documentation.
Published · Updated