I always take a look at the latest updates for BLURT because as a witness, I see that as part of my job. I must verify that the code that we will be running will be great for the platform(Its something that the steem witnesses failed at, and that caused multiple freezes during their hard forks).
I noticed something wrong with the latest one, we are disabling account creation and account claiming. At first I believed it was just a blockage of the RC based one, but as I dug closer I realized it was a full block of both ops.
There's also a grammatical error, it should be "this operation is been disabled..."
As we see, the op is being disabled outright. The code is here: https://gitlab.com/blurt/blurt/-/commit/fdece463c15a55c0205e946a9387902d09065f26.
Linked right to interesting part: https://gitlab.com/blurt/blurt/-/commit/fdece463c15a55c0205e946a9387902d09065f26#ec235cb23a2cdd6a5796068ab93b102106d9813a_1414_1414.
After noticing that, I immediately alerted @jacobgaddikan, who agreed that this was a problem and hopefully @baabeetaa will have a fix for it before HF2(which looks like its soon, 2020-08-08T00:00:00.000Z according to:
https://gitlab.com/blurt/blurt/-/commit/fdece463c15a55c0205e946a9387902d09065f26#a35ff94415082e8e90d12249d8dae0f79c4687e7_6_4).
I'd like for there to be more time between announcement of final code and the HF in the future so we can run a testnet and ensure that everything works as expected. We don't want to pull a Steemit Inc. in here, do we?
If you want a witness who cares for the platform and looks at the code being run, vote for me, yourking.
Good work!