Hardfork 24 progress (HF date: Oct 6)

blocktrades

(79)

Published in

HiveDevs

Words

0

Reading

0 min

Listen

Play

2020-09-28 22:49

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

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).