Weekly progress update: hardfork date changed to Oct 6th

In my last post, I mentioned that Sept 22nd was the earliest I thought we could potentially execute the hardfork, but we knew our chances of hitting that date were 50/50 at best. Despite that, we wanted to get exchanges to begin their migration process for their wallets, as the upgrade to hardfork 24 requires a long re-index and would probably require a certain amount of assistance from Hive exchange support personnel. In theory, the new snapshot feature makes it possible to avoid this, but we didn’t expect that many exchanges would take advantage of such a relatively new feature since it would require trusting a third party to provide them with a snapshot, and so far that seems to be the case.

Originally we were planning to fallback to a date of Sept 29th if we decided 22nd wasn’t feasible, but I recently learned that Sept 30 – Oct 4th is a long Korean holiday, so to avoid conflicts with updates by Korean exchanges, we’ve decided to set the hardfork date to Oct 6th. This will also give more time for Hive dApps to do rigorous testing. The final release for hived HF24 is tagged here:
https://gitlab.syncad.com/hive/hive/-/tags/v1.24.2

Hived work

We made one change to hived in the past week to provide some additional voting power information needed by hivemind:
https://gitlab.syncad.com/hive/hive/-/merge_requests/114

The only other change to hived was to set the new hardfork date.

Hivemind work

We completed the implementation of reputation data collection in hivemind and the latest implementation (this is the third one) seems to have reasonable performance.
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/157

Work also continued on notifications:
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/148
We will have one remaining issue to implement for hivemind-based notifications: scanning of posts for account name “mentions”. This will likely be completed tomorrow.

Performance optimizations, fixes to API responses, and code refactoring and cleanup:
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/151
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/154
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/155
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/127
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/156
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/158
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/136
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/163
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/161
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/164
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/159
https://gitlab.syncad.com/hive/hivemind/-/merge_requests/142

  • Note for apps developers: we are intentionally planning to make a “breaking change” to the behavior of the list_comments API method, as the current behavior seems flawed. If you use this API call, please review this merge request for the new behavior and comment if you have any concerns about the change: https://gitlab.syncad.com/hive/hivemind/-/merge_requests/169

Condenser

We have been doing some limited testing using condenser (hive.blog software) to exercise our eclipse API node. Condenser uses a large variety of hivemind API calls so it makes a useful adjunct to our automated test system.

As a result of those tests, we also made one change to condenser itself:
https://gitlab.syncad.com/hive/condenser/-/merge_requests/106

This change resulted because of another potential breaking change to the Hive API: the get_profile API no longer directly reports post_voting_power. Instead, all frontends should use find_account API or a similar one that returns either database_api::api_account_object or condenser_api::api_account_object to get post_voting_power.

Plans for upcoming week

We plan to provide an updated full API node in the next day or so with the latest hivemind changes for apps testing. We’re also planning another full resync of hivemind (the fun four day process) to incorporate the latest changes such as reputation calculations and notifications, and we’ll update our eclipse API node again once that is completed, so that apps will have the latest changes to test against.

44 Comments