Today we officially tagged the latest version of the Hive API node stack (v1.27.11). We’ve been running various beta versions of the new stack for quite a while on api.hive.blog, and its been easy to see that it performs much better than the old stack running on most of the other Hive API nodes. The release version of the API is now accessible on and we’ll switch to the release version of the stack on api.hive.blog tomorrow.

Originally I planned to release in December, but just before the holidays kicked into full gear, I found an issue with the HAF upgrade process during my testing. The HAF upgrade process enables a node to update its software without having to do a full replay (a full replay takes several days, whereas an upgrade completes in minutes or less typically).

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'll make a full report on our recent work soon, probably next week, but in the meantime I wanted to share the performance improvement we're seeing after switching hivemind from the python based server to postgREST.We've had several devs working on this task for a few months now; it was a big job as there was a lot of python code in the "server" portion of hivemind that needed to be replaced by SQL code in order for us to switch to using postgREST as hivemind's web server.

As promised last week in my previous post, here’s an update on the “frontend” work we’ve been working of for the past few months.Block Explorer User InterfaceThe block explorer project was created because I wanted us to have an fast, easy-to-deploy, open source block explorer that could be hosted in a decentralized manner.

I've been super busy for a while, so I fell behind a bit on reporting progress (it's been about 4 months since my last report...). Originally I was planning an earlier release of everything, but in the end we decided to push back the releases so that we could add more features that we considered important to completed.