Steem Witnesses Activated a Fork Restricting Former Validators’ Accounts

Steem witnesses activated software version 0.22.888 at 14:00 UTC on April 4, 2020, imposing transaction-level restrictions on a named group of accounts associated with former Steem witnesses and the newly launched Hive chain. The code and contemporaneous reporting show that the measure blocked affected accounts from operations including transfers, vesting withdrawals, witness voting and proposal voting when transactions reached nodes running the fork.

The intervention mattered beyond the value of the tokens involved. Steem used delegated proof of stake, in which token holders elected a small set of “witnesses” to produce blocks. Soft fork 0.22.888 demonstrated that those block producers could coordinate to deny selected accounts ordinary asset and governance functions without changing the balances recorded in those accounts. It turned a dispute over control of a social-media blockchain into a direct test of what ownership and censorship resistance meant under delegated governance.

A fork after a fork

The April 4 action followed two months of escalating conflict. Tron founder Justin Sun’s acquisition of Steemit Inc. had been announced on February 14, 2020. Existing Steem witnesses then restricted the company’s large stake, while exchange-held tokens were later used in a witness vote that displaced the incumbent group. A large part of the original community responded by launching Hive as a separate blockchain on March 20.

The account that announced 0.22.888 on Steemit presented the restrictions as temporary protection against people it said had threatened Steem during the Hive split. That rationale was a contemporaneous claim by the fork’s advocates, not an independently established finding. The announcement described criteria tied to running Hive-related software, voting for witnesses that supported the split, or operating associated accounts.

The implementation record is more precise about effect than motive. The referenced code named 11 accounts and filtered a range of signed operations. A contemporaneous CoinDesk report published on April 5 counted eight accounts holding an aggregate 17.6 million STEEM as effectively frozen. The difference between 11 identifiers in code and eight accounts in the reported token total is a limitation of the surviving record; the article should not collapse those two measurements into one.

What “frozen” meant

The fork did not erase balances or transfer tokens to another owner on April 4. Instead, upgraded witnesses declined specified transactions from targeted accounts. That included transfer and limit-order operations, starting or routing a vesting withdrawal, moving tokens into savings or vesting, voting on posts and proposals, and changing witness votes or a witness proxy.

Because this was witness policy enforced through node software, “freeze” was practical shorthand rather than a claim that every copy of the ledger had been rewritten. A contemporaneous technical account noted that transactions might still reach a witness running older software. The effective restriction therefore depended on adoption by the active witness set and on how the network treated blocks containing disallowed operations.

That distinction is central to the institutional lesson. Delegated proof of stake did not eliminate governance discretion; it concentrated operational discretion in elected block producers. Supporters characterized the measure as defense of the remaining chain. Critics described it as retaliation against Hive supporters. The verified fact on April 4 was narrower: witnesses adopted code designed to prevent selected users from exercising normal token and governance functions.

What was knowable on April 4

By the end of April 4, the activation time, targeted operation types and named accounts were visible in public code and community records. Independent reporting published on April 5 and April 6 corroborated the restriction and quantified 17.6 million STEEM across eight affected accounts. Those later reports are used only to confirm the April 4 event; their subsequent market observations are not imported here.

No reliable event-day price series with a defined venue, cutoff and methodology is necessary to establish the development, so this reconstruction makes no STEEM price, market-capitalization or percentage-of-supply claim. What the record supports is a governance event: a coordinated witness-level restriction that made control of block production immediately consequential for control of assets.