Bring on newnewsteem: HF22

in #newnewsteem5 years ago

Goodbye HF21. You will be missed. I wonder if this will be the shortest lived hardfork in Steem's history...

One thing that's nice about having another team put together a hardfork and have it not go perfectly might be a reality check. Blockchain is hard. It would be great if we could do this a little better, but it's hard. Tiny technical details on a million edge cases can stop the chain. Best intentions and lots of review can't catch them all. It happened to Steemit. It happened to blocktrades. Most don't think blocktrades folks are idiots. Maybe we can cut steemit a little slack. Blockchain pimpin' ain't easy.

In a few days hopefully this whole thing will be forgotten. I'm still very hopeful for what's to come. Getting content discovery, a new trending, better behaved bidbots, and a proposal system is a nice fork.

HF22

Anyway, I'm building HF22 now. Hopefully it doesn't force a replay on me. I got my hot dice and lucky charms out (metal, not the cereal). Wish me luck.

newnewsteem starts in 13-14 hours assuming the other witnesses get the memo. We just did a hardfork and had a fairly smooth transition with the exchanges. Hopefully this goes ok too.

Edit

Got 22 up and running. No replay required. 3 down, 14 more witnesses to go...

Sort:  

We wait and watch and try to help with HF21 testing for over two months, yet HF22 needs no testing, and we can just throw it up on-line and go live with it.

The stated reason was that steemit could not delegate to new accounts. Did Steam Monsters have any problem with delegations? I certainly did not I was able to delegate some steem with no crash and burn.

That being the case, what was in HF22 that was changed from HF21? other than steemit could not delegate to new accounts part being fixed.

It's basically a bug fix

I wonder if this will be the shortest lived hardfork in Steem's history...

Looks like a few were shorter...

0   "2016-03-24T16:00:00",
1   "2016-04-25T17:30:00",
2   "2016-04-26T18:00:00",
3   "2016-04-27T13:00:00",
4   "2016-04-30T15:00:00",
5   "2016-05-31T17:00:00",
6   "2016-06-30T14:00:00",
7   "2016-07-04T00:00:00",
8   "2016-07-04T01:00:00",
9   "2016-07-14T00:00:00",
10   "2016-07-15T12:00:00",
11   "2016-07-17T15:00:00",
12   "2016-07-26T15:00:00",
13   "2016-08-15T14:00:00",
14   "2016-09-20T15:00:00",
15   "2016-11-08T16:00:00",
16   "2016-12-06T16:00:00",
17   "2017-03-30T15:00:00",
18   "2017-03-30T15:00:00",
19   "2017-06-20T15:00:00",
20   "2018-09-25T15:00:00",
21   "2019-08-27T15:00:00"

I am reading this twice, but I am afraid I don't quite understand. 🤣 But hoping for the best with newsteem, which already looks so.

The fork yesterday caused a problem with the delegation ability. This is something that happens at the base layer, hence requires another hard fork.

If they did not do it now, they would have to add it to the next fork, expected in the Spring. The problem with that is that new accounts would not receive the delegation from Steemit to operate.

11 AM EDT tomorrow the new fork goes into place.

Oh, I see. Thanks for your explanation.

I'm just wondering, if the system could be changed in a short period of time, what took it so long and let the steem price suffer before the system change? Well, just asking.

Glad I held off on the good job stinc post.
It will be good practice for 'em.

To listen to the audio version of this article click on the play image.

Brought to you by @tts. If you find it useful please consider upvoting this reply.

If Trump read this will say " fake news. Sad!" Lol
Come on, put the new Steem-Engine outside ;)

Posted using Partiko Android

Sorry! Is really true! Ahahaha downvote revenge 😂😂😂

Posted using Partiko Android

This Fork has Got to Be Good For STEEMMONSTERS I Can Feel It @aggroed

Wish me luck...

Viel Glück ;)

Maybe do more forks and not try to throw the whole kitchen sick in there. This bloated fork was sure to burp.