![blocktrades update.png](https://images.hive.blog/DQmSihw8Kz4U7TuCQa98DDdCzqbqPFRumuVWAbareiYZW1Z/blocktrades%20update.png)

Here’s a quick update on what the BlockTrades team has been working on since my last report. 

My plan is to stick with the previously announced time of mid-December for upgrading all the Hive API nodes, but I decided it was best we delay hardfork 28 to first quarter of 2025. This means only API node operators will need to upgrade in December, and exchanges can upgrade later. 

I think separating this into two releases should reduce the pressure on everyone, since there’s more likely to be issues with the API node and non-hardfork hived changes (just because there are so many changes and the changes need to be tested against all the Hive apps out there), compared to the actual hardfork changes (relatively few at the moment).

This should also reduce the chance for potential issues when exchanges finally upgrade, since most of the hived changes will have been tested in production for a while by then.

## [Hived: blockchain node software](https://gitlab.syncad.com/hive/hive)

As part of the release of the HAF API node software suite, we’ll be releasing a new version of hived (which will be followed by a later release with the final “feature set” for hardfork 28). As a tentative date, we’ll be setting the hardfork date to February 8, 2025, but that may be overly optimistic.

### Recent improvements
* We optimized the time to split a monolithic block_log into 1M block size files from 38 minutes down to 13 minutes: https://gitlab.syncad.com/hive/hive/-/merge_requests/1406
* Fixed value in database_api::api_account_object::post_voting_power to correctly show voting manabar values at client side.

### In progress
* Continuing analysis of hived under transaction flooding conditions with large blocks (e.g 1-2MB blocks).
* Beginning rewrite of transaction signing algorithms (e.g. to allow more signatures, etc). This work will also affect how we manage 2nd layer lite accounts.

## [HAF: framework for creating new Hive APIs and apps](https://gitlab.syncad.com/hive/haf)

### Recent improvements

* Eliminated unnecessary ANALYZE calls to speedup HAF instance restart time: https://gitlab.syncad.com/hive/haf/-/merge_requests/547
* Upgrade to Postgres 17 and eliminated associated performance regressions: https://gitlab.syncad.com/hive/haf/-/merge_requests/550
* Eliminated problems in HAF instance upgrades: https://gitlab.syncad.com/hive/haf/-/merge_requests/533
* Fixed bug preventing using --skip-hived option in HAF container: https://gitlab.syncad.com/hive/haf/-/merge_requests/544
* Added automatic performance logging for HAF app block-processing times and keep the performance history in a table to simplify long-term performance analysis: https://gitlab.syncad.com/hive/haf/-/merge_requests/553
* Fixed a bug in updating last_active_time in apps with multiple contexts: https://gitlab.syncad.com/hive/haf/-/merge_requests/558
* Added a generic health-check that can be used by any HAF app’s block processor (i.e. the process that syncs the app’s local tables): https://gitlab.syncad.com/hive/haf/-/merge_requests/551

### In progress
* Adding API methods to allow a HAF app to request and wait on the creation of indexes on HAF’s own tables in a way that optimizes index creation time and avoids deadlocks.

## [Hivemind: social media API](https://gitlab.syncad.com/hive/hivemind)

We completed the switch to postgREST, including final optimizations I promised in my last post to fix the few performance regressions that we found. Every hivemind API call is much faster than before now. Here’s the latest API benchmarks:


Reference python times:
| Endpoint                                  | Max [ms] | Min [ms] | Average [ms] | Median [ms] |
|-------------------------------------------|----------|----------|--------------|-------------|
| condenser_api.get_discussions_by_blog     |   6703   |   166    |     2305     |     2396    |
| bridge.get_account_posts                  |   3344   |    26    |     864      |     825     |
| bridge.get_discussion                     |  22713   |    3     |     1935     |     215     |
| bridge.get_ranked_posts                   |   3409   |   205    |     971      |     955     |
| condenser_api.get_discussions_by_comments |   2676   |    4     |     587      |     574     |
| condenser_api.get_followers               |   136    |    20    |      38      |      31     |
| condenser_api.get_discussions_by_created  |   2899   |    85    |     638      |     308     |
| bridge.get_profile                        |   611    |   328    |     417      |     395     |
| condenser_api.get_discussions_by_feed     |   3146   |   1272   |     1748     |     1694    |
| condenser_api.get_blog                    |   4617   |   1198   |     3256     |     3496    |
| condenser_api.get_following               |   349    |   177    |     270      |     267     |
------------------------------------------------------------------------------------------------

PostgREST:

| Endpoint                                  | Max [ms] | Min [ms] | Average [ms] | Median [ms] |
|-------------------------------------------|----------|----------|--------------|-------------|
| condenser_api.get_discussions_by_blog     |   2383   |    46    |     603      |     643     |
| bridge.get_account_posts                  |   4099   |    9     |     218      |     188     |
| bridge.get_discussion                     |   3266   |    1     |     327      |      44     |
| bridge.get_ranked_posts                   |   449    |    58    |     228      |     226     |
| condenser_api.get_discussions_by_comments |   268    |    1     |      94      |     107     |
| condenser_api.get_followers               |    86    |    10    |      15      |      14     |
| condenser_api.get_discussions_by_created  |   745    |    32    |     201      |     130     |
| bridge.get_profile                        |   485    |   320    |     388      |     379     |
| condenser_api.get_discussions_by_feed     |   594    |   402    |     495      |     497     |
| condenser_api.get_blog                    |   1533   |   312    |     861      |     897     |
| condenser_api.get_following               |   219    |   189    |     204      |     204     |

### In progress
* Various optimizations
* Switch to pure SQL resulted in some changes when an error occurs for an API call, so we’re analyzing if we can make them fully compatible with old error messages.


## [HAfAH: account history API](https://gitlab.syncad.com/hive/HAfAH)

Fixed bug in account_history_api::get_transaction returning broken JSON when transaction has no signatures: https://gitlab.syncad.com/hive/HAfAH/-/merge_requests/165

## [Balance tracker API: tracks token balance histories for accounts](https://gitlab.syncad.com/hive/balance_tracker)

* Locally create docker image for postgREST url rewriter: https://gitlab.syncad.com/hive/balance_tracker/-/merge_requests/119
* Reduce unnecessary logging by rewriter by default: https://gitlab.syncad.com/hive/balance_tracker/-/merge_requests/123
* Fixed a slowdown regression in live sync with Postgres 17: https://gitlab.syncad.com/hive/balance_tracker/-/merge_requests/125
* Pass application_name parameter to postgres connection string for simplified database trouble shooting in tools like pgadmin: https://gitlab.syncad.com/hive/balance_tracker/-/merge_requests/126


## [Reputation tracker: API for fetching account reputation](https://gitlab.syncad.com/hive/reputation_tracker)

* Create docker image for postgREST url rewriter: https://gitlab.syncad.com/hive/reputation_tracker/-/merge_requests/47
* Split schema installation and HAF index creation into two phases to speed up block processor sync time: https://gitlab.syncad.com/hive/reputation_tracker/-/merge_requests/48 https://gitlab.syncad.com/hive/haf_api_node/-/merge_requests/36
* Reduce unnecessary logging by rewriter by default: https://gitlab.syncad.com/hive/reputation_tracker/-/merge_requests/52
* Pass application_name parameter to postgres connection string for simplified database troubleshooting in tools like pgadmin:
https://gitlab.syncad.com/hive/reputation_tracker/-/merge_requests/54
* Updated common-ci-configuration reference to get swagger versioning feature: https://gitlab.syncad.com/hive/reputation_tracker/-/merge_requests/50


## [HAF Block Explorer](https://gitlab.syncad.com/hive/haf_block_explorer)

### Recent improvements

* Elimination of random errors during application setup: https://gitlab.syncad.com/hive/haf_block_explorer/-/merge_requests/237 https://gitlab.syncad.com/hive/haf_block_explorer/-/merge_requests/236
* Improved functionality of search APIs: https://gitlab.syncad.com/hive/haf_block_explorer/-/merge_requests/233

## [WAX API library for Hive apps](https://gitlab.syncad.com/hive/wax)

### Recent improvements
* Fixed a bug in the health-checker component: https://gitlab.syncad.com/hive/wax/-/merge_requests/227

### In progress

* Creating a generic UI component for the health-checker.
* Creating an object-oriented interface for the Python version of Wax.
* Porting the code for preventing accidental leakage of private keys to Wax’s transaction construction code.
* Create documentation.

## HAF API Node
### Recent improvements
* Allow setting a different public hostname from the private hostname: https://gitlab.syncad.com/hive/haf_api_node/-/merge_requests/32
* Move rewriter creation to individual HAF apps and now use those containers: https://gitlab.syncad.com/hive/haf_api_node/-/merge_requests/34
* Fix reputation tracker health check: https://gitlab.syncad.com/hive/haf_api_node/-/merge_requests/35
* Add the ability to get email notifications when haproxy detects a service going down: https://gitlab.syncad.com/hive/haf_api_node/-/merge_requests/37

### In progress
* Testing replaying HAF API servers

## What's next?

I left notes on most of the remaining code changes that are planned in each application’s section, but other than those changes, our main focus in the next weeks will be testing all the apps together, especially under real world loading conditions (e.g. mirroring traffic from our production API server).

Then, finally, we’ll need all the apps devs to begin verifying their code against the new API server code. Limited forms of this testing can be done now by testing against api.syncad.com, which is where we deploy release candidates for the API server code.