Hive launched as a community-led fork of Steem

Hive launched at 14:00 UTC on March 20, 2020 as an independent blockchain forked from Steem, giving a group of developers, block producers and users an exit from a governance conflict that had divided the social-media-oriented network.

The official launch plan described Hive as a delegated-proof-of-stake blockchain created from Steem’s code. Contemporaneous reporting later on March 20 said the fork completed successfully, while Hive’s official development record identifies March 20 as the network’s launch date.

This was more than a routine software upgrade. Steem continued operating, while Hive began producing its own history from the fork point. Transactions, governance decisions and content created on either network after that point would not automatically appear on the other.

Why the split mattered

The immediate dispute followed Tron founder Justin Sun’s February 14, 2020 acquisition of Steemit Inc., the company behind Steemit.com and holder of a large quantity of historically mined STEEM. That stake carried substantial influence in Steem’s delegated-proof-of-stake governance system, where token-backed votes help select block-producing witnesses.

Steem community members had attempted in February 2020 to restrict the stake’s governance power. The ensuing conflict intensified when exchange-controlled STEEM was used in witness voting. Binance and Huobi subsequently withdrew those votes, but the episode exposed a structural question: could users meaningfully resist concentrated stake when control of block production depended on token-weighted elections?

Hive represented one answer. Rather than continue contesting governance exclusively inside Steem, its organizers copied the established ledger and created a separate network under different initial rules. The launch did not prove that Hive was decentralized; it demonstrated that a community could use an open-source chain split to reject an existing distribution of governance power.

What moved to the new chain

Hive’s launch announcement said existing Steem accounts, content and account histories would appear on Hive. Eligible stakeholders were assigned corresponding balances: liquid STEEM became HIVE, Steem Power became Hive Power, and Steem Dollars became Hive Backed Dollars. The stated distribution ratio was one-to-one for the corresponding assets.

The distribution was not universal. Organizers said accounts holding the Steemit Inc. “ninja-mined” stake and accounts they determined had supported Steem’s centralization would not receive the initial token allocation. That exclusion was a consequential governance choice made by the fork’s organizers, not a neutral mechanical property of copying a blockchain.

Hive also imposed a 30-day delay before newly vested stake could be used to vote for witnesses or proposals. Organizers presented that rule as protection against another rapid governance intervention involving recently powered-up exchange balances. Other uses of vested tokens were not subject to the same delay, according to the launch record.

Exchange support and its limits

Exchange participation mattered because customers holding STEEM in custodial accounts could not independently control the corresponding fork allocation. Huobi’s March 19 notice said it would take a snapshot at the planned fork time and distribute one HIVE for each eligible STEEM held by customers. Binance announced comparable support, according to CoinDesk’s March 20 report.

Those commitments supported access to the fork but did not establish immediate HIVE liquidity, a market price or universal exchange recognition. Listing, deposit and withdrawal schedules remained separate operational decisions. No price or percentage-performance claim is included in this reconstruction.

What the record establishes

The surviving evidence establishes that Hive launched on March 20, 2020, inherited Steem’s pre-fork account history, and then operated as a separate network. A later CoinGecko first-quarter report independently recorded successful activation at 14:00 UTC.

The record does not establish that every copied balance was immediately accessible, that every exchange distributed tokens on the same schedule, or that either resulting chain had achieved an uncontested form of decentralization. Those questions require account-level distribution records, exchange completion notices and continuing governance data beyond the launch event itself.