Last night I was try to run a steem node (v0.23.0) locally for power down operation, but I forgot that my signing key was configured in this node(v0.22.1).
(图源 ：pixabay)
After successfully modifying the power down period, I went to sleep.
Today, I suddenly found out that my local node signed blocks on steem (v0.23.0).
That's not what I want, I personally don't support steem v0.23.0 hard fork, and think it's very unreasonable.
So I decided to permanently shut down my witness node on steem.
PS: Don't do important operations when you are sleepy in the middle of the night!
中文版
因为硬分叉修改了Power down周期，为了修改自己账户的Power down操作，我打算在本地运行一个STEEM 0.23.0的节点，但是我忘记了我本地的节点上配置有我的出块密钥。
做完修改后，我就去睡觉了。
今天无意中发现，自己STEEM的见证人，竟然使用Vv0.23.0在STEEM上出块了。
这并不是我的本意，我个人并不支持STEEM v0.23.0 硬分叉，认为他很不合理。
所以我决定永久关闭我在STEEM上的见证人节点，感谢大家一直以来对我STEEM上见证人节点的支持。
——
教训: 半夜不清醒的时候少进行重要操作。
Yesterday's hard fork of Steem reports 0.23.0, but so does Hive, which many Hive witnesses reported on their last-signed block on the Steem chain. Honest mistake though, not much to worry about.
Thank you for your understanding， but it was really my fault. 😳
In order to avoid misunderstanding, I shutdown the witness on STEEM and posted this post to explain it, although it may lead to some hostility from other parties.
Congratulations! Full time hive now? 开心Hive也有中文的community。