Edit: I'm now running v0.22.1

in #witness-updatelast month (edited)

Updated March 5th, 11:00am AST:

Versions v0.22.0, v0.22.1, v0.22.5, and v0.22.4444 are essentially the same thing when it comes to consensus code. Version v0.22.5 was created by whoever controls the 20 witnesses who were put in consensus via exchange stake, not community voted stake. v0.22.4444 was created to be consistent with v0.22.5 in terms of consensus, but it also has some negative cultural meanings to some people, so I've moved my witness back to v0.22.1.

I hope we can find a path forward that benefits the Steem community and creates a reasonable outcome for the new owner of the Steemit stake which takes into account the commitments made about that stake to the community since the beginning of this blockchain.

Updated Post:

Edit: I'm now running v0.20.4444

I'm now running v0.20.4444 from https://github.com/Gandalf-the-Grey/steem/releases/tag/v0.22.4444

------------------------------------------------------

            STARTING STEEM NETWORK

------------------------------------------------------
initminer public key: STM8GC13uCZbP44HzMLV6zPZGwVQ8Nt4Kji8PapsPiNq1BK153XTX
chain id: 0000000000000000000000000000000000000000000000000000000000000000
blockchain version: 0.22.4444
------------------------------------------------------

It's the same thing as v0.22.1 (so, essentially, the same thing we presume is v0.22.5) with a slight change to change the version number to make it clear I do not support a centralized takeover.

To make this point clear, see https://steemian.info/witnesses

Notice the total voters column on the right. Is that really consensus?

I disabled my witness as a protest. Now I'm running v0.22.4444 so those who get their tokens off an exchange can vote for a witness who actually wants to protect their property from centralized power grabs like this.

Please see my post linked to below which includes a video with more information as this was unfolding this morning.

Original Post:

I've disabled my Steem witness (for now)

My intentions as a Steem witness are to help protect the decentralized nature of the Steem blockchain and the user content it secures. I do not support the current chain fork put in place by a small group of exchanges against the intentions of the Steem community as demonstrated by those who continued to show support for the witnesses who implemented the temporary soft fork 22.2.

If you don't think exchanges should control the Steem blockchain, don't store your tokens there. Your stake in Steem on centralized exchanges was just used to take over the Steem Blockchain.

I'll continue to monitor the situation and adjust accordingly.

Sort:  

Dude, the community needs the community-selected witnesses to be running their nodes so that the community can vote on them and be represented. How long can Justin Sun keep control over all that stake and use it to vote for his witnesses? Not very long. We need the real witnesses to be up and running so we can support them. I hope you will re-activate your witness. The community resilience is VERY high and it will take a lot more to destroy it. First we have to think about what changes to the governance mechanism will prevent any single large stakeholder from centralizing the chain. And then we can think of how to implement those governance changes.

Dude, the community needs the community-selected witnesses to be running their nodes so that the community can vote on them and be represented.

I agree with your point here, but currently anyone supporting 22.2 is on a fork. Their efforts are useless. If I continue to run a node on that code, it's just off on a separate fork, not the real chain. I'd have to run 22.5 to get back into consensus but that doesn't exactly send a good message for voters who disagree with 22.5.

That said, I may use 0.22.4444 which @gtg is using, an unmodified version of 22.1 with just a slight change to the version signal.

How long can Justin Sun keep control over all that stake and use it to vote for his witnesses? Not very long.

I wish this were true, but people need to take their tokens off exchanges for this to really happen.

We need the real witnesses to be up and running so we can support them. I hope you will re-activate your witness.

If tokens remain on centralized exchanges, it won't matter.

The community resilience is VERY high and it will take a lot more to destroy it.

I hope so, but "hope" doesn't go very far when it comes to Byzantine Fault Tolerance. Code is law and humans choose which code to run and who to vote for.

If I continue to run a node on that code, it's just off on a separate fork, not the real chain. I'd have to run 22.5 to get back into consensus but that doesn't exactly send a good message for voters who disagree with 22.5.

Isn't this the crucial point. If the Steem community all says we are only going to accept 22.2 (whatever version restricts the STINC stake) as the real chain. Users, and the services they user, determine what protocol they would like to follow. In other words, can the actual productive portion of the Steem community agree that we'll stay on the pre-attack software version and let there be a fork.

people need to take their tokens off exchanges for this to really happen.

It seem to be pretty obviously that binance will not allow that, the Steem wallet will be 'on maintenance' for now.
Or did they change the power down time to 'one week' already?

Which exchanges are powered up and now voting???

binance
huobi

I'm curious to see where things go from here. A bit anxious I have to admit.

Appreciate ongoing updates with what is happening on the back end, for us less technical supporters.