Hardfork 24 progress (HF date: Oct 6)

in #hive-139531last month

Below is a summary of HF24 work by BlockTrades team in the past week.

Hived work

We haven’t made any changes to hived this week since we updated to v1.24.2 with a hardfork date of Oct 6th. But we and the other witnesses continue to do testing, especially of the new features. We’re also working with exchanges to ensure their wallets get updated. The official hived release is here:
https://gitlab.syncad.com/hive/hive/-/tags/v1.24.2

@gtg found two issues with hived 1.24.2, one of which still needs further investigation (a snapshot reload problem for a node with rocksdb account history plugin enabled), but neither problem is consensus-related, so they can be addressed independently of the hardfork as a developer becomes available to work on them (probably this upcoming week):
https://gitlab.syncad.com/hive/hive/-/issues/77
https://gitlab.syncad.com/hive/hive/-/issues/78

Hivemind work

The remaining notification and reputation implementation work was completed in the past week. Numerous fixes, code -refactoring, logging, and optimization changes were also made:
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/165
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/166
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/168
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/172
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/171
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/178
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/179
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/180
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/174
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/183
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/186
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/189
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/191
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/193
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/192
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/194
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/196
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/198
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/199
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/201
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/197
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/202
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/200
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/204
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/206
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/209
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/205

Changes that impact API behavior

In a few cases, we made changes to the responses of API calls where the current behavior wasn’t always very logical. It’s unlikely that this will have any negative impacts on apps, but apps developers should review and especially test any code that uses these API calls:
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/169
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/176
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/203

Plans for upcoming week

The upcoming week will be devoted to continued testing, both by creating new API tests and by apps developers testing their apps against our eclipse API node located at:
https://beta.openhive.network (jussi, hivemind, hived v1.24.2)

We’re still experiencing one reputation-related performance issue during live sync with this version of the API node, so it’s lagging behind about 3-6 minutes relative the head block of the blockchain. We hope to have this issue fixed tomorrow.

The current eclipse API node that we are making available for testing was created by running manual updates of its database as we made changes and fixed bugs, so we’ve also begun syncing a new API node starting from block 0, to verify that the two eclipse API nodes (the manually adjusted one and the pristine one that was synced from block 0) perform the same (this will take ~4 days to complete).

Sort:  

As an advocate of decentralizing blacklists, have you considered providing one, or do you know of anyone intent on providing a stripped down blacklist focusing on spam and scams alone?

I hope there will be alternatives available to enable folks to moderate the shock of the spam overload that will affect them as seek to eschew the extant centralized lists.

Thanks!

I wasn't planning on it, as I think there's probably plenty of people who will be willing to take on such a task, and my preference is always to let others help out where they can. But if no one else does it, I wouldn't mind doing it, since it shouldn't be super difficult to do. Still, all-in-all, I doubt it will be necessary.

Thank you for keeping our community updated

Thank you for updating. Greetings

Thanks for keeping Hive up to date, that builds a lot more trust. Greetings. 👊

Thanksgiving @blocktrade for info.

Happy Hanukkah

Congrats on your efforts for better Hive blockchain :)

Great work that you guys are doing in the background to improve Hive and seriously appreciated!

Thanks for keeping hive up to date, great job!

Thanks for the update. Just want to clarify about the 30 day delay about powered up HIVE. If you already have HIVE powered up then you power up 10 HIVE for example, it will take 30 days for that HIVE Power to then be used in witness voting?

Will it also affect a users ability to delegate that 10HP to another user or voting/curating or proposal voting or is it only on witness voting?

It will affect witness/proposal voting, but not voting on posts.

Brillo, thanks for clarifying 👍

this is very great, thanks for keeping us up to date

Great work, there is hope!