Code refactoring of hivemind has been done for a while. A week or so ago we refactored some code in hived to make it easier to updates to the API without requiring as much boilerplate code changes. But in general, code refactoring is never done, you often find ways to improve the code when you work in it.
There hasn't been a lot of API restructuring. We've optimized the performance of the API calls and also brought some of the responses from the various API into greater conformity with each other (mainly in the face of error cases). But restructuring the API itself is a big task, because there's many 3rd party dapps that depend on the API, so any major changes in the API would require coordination changes to all the dapps. So we've limited our work of that type.
Now as part of our modular hivemind work, we're likely to start introducing new orthogonal sets of API calls depending on the configuration of the hivemind selected by the API node operator. For example, a simple "bare-bones" modular hivemind would only have API support for blockchain operation data and account information. And then we'll likely introduce new APIs for expanded versions of a module hivemind that have access to additional data like posts.
But that will probably have lower priority over the smart contract platform that will be built on top of the base module hivemind layer. Our priority for now is 1) get out the base layer modular hivemind and then 2) create the smart contract layer on top of that.
I'll check back on the dev count later, I need to go for dinner now. I think it's still roughly the same at the moment, around 10-12 devs.
"create the smart contract layer on top of that." ethereum +defi+no fees= hive to the moon ? :D
Thanks for the detailed reply🙂!
I know this is all very technical stuff (hard to break down in laymen's terms) and you are still working on the foundation, but investors like to hear more about timelines and near-term projects and priorities.
Maybe try to include more of that in future updates.
Edit: after rereading your post I see that you kinda did that in the last paragraph, but the details are not really exciting from an outsiders perspective. It reads like: "minor improvements/update coming soon - we are doing a lot of testing right now - nothing fancy in the near- to mid-term"
The performance results seem really good, but you are not highlighting it like that. I actually mearly missed it (didn't get it) in the first read.
There's a reason for that: I'm not really writing these posts for investors. These posts are primarily intended to communicate technical changes as we make them and they are mostly aimed at other developers.
I'm not directly involved in marketing for Hive, although I'm happy to share technical details with the various folks handling that (it's just a bunch of volunteers who are willing to commit their time right now, as there is no funded marketing proposal yet to compensate them for their work). Since the BlockTrades team is already contributing a lot on the technical side, I've always felt it was best for other people to handle marketing for Hive, although I'm happy to contribute technical info to help them in their endeavors.
In addition to these progress reports, I do plan to occasionally make roadmap reports for longer term plans by our team (note this is just for the work done by our team, there's other dev teams that have their own long term plans as well). My last such roadmap report was here: https://hive.blog/hive-139531/@blocktrades/roadmap-for-hive-related-work-by-blocktrades-in-the-next-6-months
I'll probably be making an update on our overall roadmap progress in a few more weeks (essentially a mid way progress report).