Steem witnesses activated soft fork 0.22.2 on February 23, 2020, restricting a defined group of Steemit-controlled accounts from using their tokens for governance or specified asset operations. Participating witnesses described the change as temporary and reversible protection while the community sought clarity about Steemit Inc.’s new ownership and the future use of its historically accumulated stake.
The intervention mattered because Steem’s delegated-proof-of-stake system gave token-backed votes a direct role in selecting the witnesses responsible for producing blocks. Steemit Inc.’s large position had reportedly remained outside witness voting under an earlier community understanding. A change in control therefore raised a practical question: whether that informal commitment would bind a new owner when it had not been enforced by the protocol.
The soft fork converted that social understanding into code, at least temporarily. It also demonstrated the discretion held by an elected witness set. The same governance mechanism that could defend the network against concentrated voting power could be used to deny selected accounts functions normally associated with token ownership.
What version 0.22.2 changed
The collective witness statement identified five relevant accounts: misterdelegation, steem, steemit, steemit2 and steemitadmin. Nodes enforcing version 0.22.2 would reject 12 specified operation types initiated by those accounts.
The restrictions covered witness voting and delegation through a proxy, proposal voting, ordinary content voting, transfers, limit-order creation, movement into savings or vesting, escrow transfers and operations used to withdraw or route vested tokens. In Steem terminology, withdrawing vested tokens was commonly described as powering down.
The code did not delete the accounts, reduce their displayed balances or transfer their tokens to another holder. “Freeze” was therefore useful shorthand but incomplete. The fork instead made participating consensus witnesses decline particular transactions involving the named accounts. Its practical effect depended on adoption by the witnesses producing and validating blocks.
The statement’s authors said other users and ordinary transactions would continue without change. They also said exchanges did not need to upgrade because existing version 0.22 nodes remained compatible. Those were contemporaneous representations by the fork’s proponents; this reconstruction did not independently reproduce the network or test every transaction path as it operated on February 23.
The ownership uncertainty
TRON Foundation and Steemit had announced a strategic relationship on February 14, 2020. Contemporary accounts conflicted over the deal’s description. The public announcement called it a partnership, while Steemit co-founder Ned Scott stated that he had sold Steemit to Justin Sun.
The February 23 witness statement treated TRON Foundation as Steemit Inc.’s new owner and major stakeholder. It argued that the restricted stake had been earmarked for developing the Steem ecosystem and kept out of governance under a longstanding, good-faith understanding. The statement did not identify a legally binding agreement carrying that commitment into the transaction.
Accordingly, the event-day record supports the existence of the restriction and the witnesses’ stated security rationale. It does not establish that the new owner had attempted to vote the affected stake before the fork, that a takeover was already underway, or that either side’s interpretation of ownership rights was legally correct.
Why the precedent mattered
Soft fork 0.22.2 exposed a tension inherent in token-weighted governance. Witnesses acted to prevent one concentrated position from potentially dominating elections, but they did so by coordinating restrictions against specifically identified accounts. Community members could respond through witness votes, yet voting influence itself was distributed according to stake.
The episode was therefore not simply a software release. It was an institutional decision about which prior commitments the protocol should enforce, who could translate those commitments into code and how quickly elected block producers could intervene when ownership changed.
Later context
Later records show that the dispute escalated on March 2, 2020, when exchange-controlled STEEM was used in witness elections that displaced the incumbent group. A community-led fork, Hive, launched on March 20. Those outcomes were not known on February 23 and do not alter the narrower event-day finding: Steem witnesses had activated a targeted, reversible restriction while control of Steemit’s stake remained contested.
The complete source packet and revision history are retained with the newsroom record.
Automated systems may have assisted with source organization and drafting. Coinburn is accountable for the published text and maintains a revision record.
This article provides news and analysis, not investment, legal or tax advice. Digital assets are volatile and may result in total loss.

