@themarkymark recently pointed out to me that the roadmap on hive.io was running out of road, so in this post I decided to make a list of some of the upcoming milestones for the work the BlockTrades team is planning now (sometimes in cooperation with other teams), then leave it to the coms team to decide how they want to organize it for the web site. There's still some things missing from this list, so I'll supplement it further later, this was just my first pass at a roadmap of our work
As you might expect, the nearer things are on the timeline, the more "concrete" they are, and things out in the future are more speculative.
2025 3Q
Updated HAF API stack
Hived Node software
- Lightweight hived only requires 4GB memory (next step to running on smart phones)
- Interactive API documentation web sites (swagger-based)
Social media API server
- Improved mute handling in Hivemind
- Keyword-based search added to Hivemind API
- Semantic text search and related post search with new HiveSense API
Wallet balance tracking and account history API servers
- Savings balances
- Pending coin conversions (@actifit)
- Open market orders (@actifit)
- Average transfer statistics
- Recurrent transfers
- Recent trades and trade history APIs for accounts
- Rich list (@actifit)
Block explorer API
- Speedup witness vote calculations
- Speedup permlink searching
- More types of data available
Hive libraries
- Wax: Typescript & Python library for Hive Dapp development
- Typescript WorkerBee: library for lightweight block processing (e.g. bot creation) (add-on to Wax)
Embeddable HTML Web page Components
- Binary Transaction viewer
- Display account
- Display witness
- Display post headers/footers and/or content
- Display post comments
- Display filter post lists (e.g. by tag)
Embeddable Wax UI components
- Embeddable API health checker component for Hive dapps
Web Dapps
- Transaction Inspector (layer 1 release)
- Updated Block Explorer UI
Key management and security apps
- Beekeeper: lightweight process for managing private keys (Wax bindings available)
- Metamask wallet snap for Hive accounts
2025 4Q
Updated HAF (base layer for designing API servers)
- Lightweight version of HAF (pruned tables)
- Support for lightweight accounts (including social media-based login)
- Support for 2nd layer transactions
- Apps respond immediately to new blocks
Hive Libraries
- Begin updating Wax to optimize server-side API caches
- Python WorkerBee: library for lightweight block processing (e.g. bot creation)
Web Dapps
- Denser: modern replacement for Condenser social media web app
Key management and security apps
- Clive: new command-line and Terminal UI wallet
Coinbase Mesh API support for Hive
2026 Q1
Prototyping for smart contracts designing
Updates to API stack
- Prototype REST-based API for hivemind (social media API)
- New community functionality for hivemind (@howo)
Web Dapps
- Customizable Hive web sites (@peakd)
- Updates to Denser (TBD)
- Transaction Inspector (layer 2 release)
Comments (31)
wow so another smart contract way?
We've been working on our smart contract system since Hive began :-) I posted about a few of my ideas for it back then: https://hive.blog/hive/@blocktrades/hive-s-future-as-a-2nd-layer-blockchain-network
Update: actually reading post in the above link, it didn't actually talk about smart contracts directly, it just focused on a few of the foundational ideas of HAF itself. I did post a little about the smart contract side later, but in a good demonstration of why we need better search, I'm not sure which posts in the past talked about it :-)
Anyways, HAF is the foundational layer for it, so that's where we've invested most of our coding effort so far (especially as the HAF part helps with other technical challenges besides just smart contracts).
We've also done a little iteration on the next stage ideas here, but lately several of the key guys have been tied up with other issues (ABW on hived optimization, Marcin on semantic search and general HAF base layer improvement): https://gitlab.syncad.com/hive/smarc/-/merge_requests
Excellent.
Wow - Nodes on smartphones is the final frontier for decentralisation - I did not expect to see that any time soon, great! My only comment is that having recently built a new front end for hive (Ureka.Social), I found that locating the best API calls to use for various requirements to be difficult. Different servers support different calls and there isn't proper documentation (at least that i can find). It would be huge to have up to date docs (that are kept up to date) on which API calls are available on which servers, which are recommended.. and why.
The new stack is fully self-documenting for all the new REST calls (not so much for the legacy JSON calls, but these are going away). And the interactive docs are "forced" to keep up, because the interfaces to the real API calls are generated directly from the documentation definitions.
You can see the docs for the current stack here, for example, on our API node: https://api.hive.blog/
One issue is a lot of the API nodes haven't yet updated to the stack we released a couple of months ago (so they don't have the docs either). I haven't really asked why, but my suspicion is that most apps don't yet use the new APIs yet, so there's been little pressure on the nodes to update, and they're probably just planning to update with the next release.
The next release has a lot of key new API calls, so I'm pretty sure the next release will somewhat force all the nodes to update if they want people to use their node. And that's just for the release in Q3. The next release after that is a revamp of the entire hivemind API to be a REST API. At that point, it'll be basically mandatory.
Ok great, I wasn't even aware of the rest API versions. At present, if I visit developers.hive.io I get a fairly complex and tought to parse list of api calls which aren't always supported by all servers or even active at all. So decyphering what exactly needs to be called in order to access specific information can be quite challenging. I hope that the rest approach and auto-documentation will overcome this. I think that a high percentage of developers from outside of Hive (considering using Hive) will not even attempt to use the APIs a lot of the time - as the docs currently are - because there's too much friction added by these issues. I'm glad to see the semantic search and 'related items' support coming soon - these are definitely needed. I was going to code my own solution for related items but I'll wait for the updates to roll out instead. đź‘Ť
$WINE
Great to see improvements. Customizable websites, something our team is working on as well, improved version of breakaway communities. Is it utilizing web components in this instance?
Yes, the idea is that the customizable web sites will be built from the web components we've already released. First issue that has come up is potentially allowing them to server-side render for SEO optimization.
I see đź‘Ť web components are great for new type of dedicated apps. For SSR, I doubt it will be beneficial to use them. Next and nuxt already handling SSR very well, adding web components into complexity will degrade benefits of those frameworks. From what I know you will have to give up hooks and context management etc. My knowledge on this bit limited but will check more details.
I think the idea for SSR is just to give special results for the bots, so no functionality will be lost.
Superb updates and hive is world of smart contract that bringing every things to hive .love hive .great improvements and every day making Hive excellent .🌼
Can you guys put some nice marketing strategies into the road map ? We are building, but we also need to sell ourselves to the outside world, So may be run some teaser ads in every quarter by spending from DHF and let the world know about it.
Again not pointing to your team, but whoever in charge should consider this. And if we have no one in charge, then it's high time we have someone to sell us better.
I'm not involved in marketing for Hive very much, I just provide technical info to people that want to market Hive. I made a decision early on not to get involved in the marketing of Hive and stay on the technical side.
There are, however, both individuals and groups that market Hive, often cooperatively, sometimes on their own. For the most part, I think they are competent at what they do.
I think one of the main constraints is that the crypto space is for the most part super-hyped by people selling ideas about "easy money" to gullible people. When trying to get attention, it's often hard for people of conscience to compete with scammers who have no problem making empty promises.
But if you're interested in helping with marketing, help is generally welcome.
It really is that way it seems. Generally I assume anybody talking to me about crypto is some kind of scammer and that really turns me off to even talking about stuff I can't show off directly. The curses of self-awareness.
Wow this is good but what of people with 3GB phones
With the pace of technology, even those phones will soon be replaced by 4GB phones :-) Its just like there is no point in us designing for 16KB computers (the first ones I worked on).
Superb update.
Lately folks accessing my blog from Hive.blog have reported my posts appeared to be blank. What is the nature of the problem displaying the content of my posts Hive.blog is having, and is it only my posts, or are there others this is happening to? I'd appreciate any insight into this issue you can provide.
Thanks!
I think it's this issue: https://gitlab.syncad.com/hive/condenser/-/merge_requests/429 The fix was merged, but perhaps it hasn't been deployed to hive.blog. @gtg Can you check on it?
I appreciate this information. I'm not a coder, and my understanding of the terms used is vague, at best, but I am happy to hear the fix is in, and hope the problem doesn't recur. If there is anything I need to do on my end, I'd be grateful to be apprised of it.
Thank you.
Someone with better understanding than me explained that five fixes have been attempted now for this issue, but it has been a couple weeks since the last. Earlier in the week a comment I made had this issue, so it seems to still be ongoing. @GTG if you could spare a moment to let me know if it is resolved, or what it is that I do that triggers it so I can avoid doing that, I'd greatly appreciate it.
Hey, sorry for that taking too long, lots on my TODO list, and unfortunately I can't simple go with current HEAD of develop as it has changes that I can't put into live system. It's the
<iframe>code to be blamed, that's not properly handled. By the way, are you brave (or crazy) enough to start using https://blog.openhive.network instead? :-) (It's meant to eventually replace the code that's running on a hive.blog)>EDIT: I just read that those were actually your readers not you using hive.blog for viewing your content
Also, that
iframething seems to be embedding of odysee links, for the best way to do that in posts it would be just to pust a link to them, as you can't safely assume that every frontend with deal with such embedding in a desired way.I suspected that iframes were the issue, as I commonly insert them in posts, but only rarely in comments, and this alerted me when those comments were the ones blanked out (and it was suggested by another with better understanding of code than me. Thanks @dreamtales!). I appreciate the confirmation, and will return to the use of links to source on Odysee that I formerly undertook, rather than insertion of iframes, prior to the @peakd team informing me such insertion was possible (to be fair, iframes don't cause this problem on any frontends but Hive.blog, which Peakd isn't responsible for), until there is a resolution to the problem.
I wasn't aware of the openhive network interface, and will have a look at it when availed the time. Is it still in alpha? I might need to exercise the caution due n00bs if so. I do very much want to be able to insert iframes, as well as .mp4, and similar video sources, so I hope that Hive frontends do enable displaying them.
Thanks very much!
What's on https://blog.openhive.network is pre-release version of new code designed for Hive.Blog, should be safe to use with Keychain and it also has its own authentication based on "beekeeper".
iframesand any other non-markdown content within body of blog posts or comments are not recommended. I mean, decentralized platform so I should rather say - I wouldn't recommend them :-)As for videos I have high hopes for 3Speak / SpkNetwork and their pursue of decentralized storage that we could easily use (and self-host).
looking good
Many things are in the pipeline to be done on Hive, and Hive will be even better once these are completed. Good job
Thanks for the update and for making Hive a powerhouse!
Respect to everyone contributing to the chain!
I know this might not be a priority, but how about a compiled hived.exe for Windows with basic tray icon and graphical installer for simpler users? That could allow for further decentralization as some users might want to have it running in their home-PCs and using localhost as their API node.
Just an idea to think about.
This can be accomplished already by running hived inside docker (i.e., inside a virtual machine). You can run docker on your Windows.
Yes, but what I was suggesting was more akin to a native Windows node instead of a virtualized node with complex installation.
Docker for Windows is actually super simple to install :-)
It is? Please explain it to me in a no coder way!
Are there plans to make HiveD IPv6 compatible in a near future?
IIRC you made an issue for this a while back. There's no opposition to the idea, it's just been lower priority compared to other scalability issues we've been working on.
I don't think it's very difficult, probably an AI assistant could do most of the work. It would just need a decent amount of testing afterwards.
Appreciate it
hived and HAF on a phone sounds epic. Didn't even imagine it.
Some very early results are here: https://gitlab.syncad.com/hive/hive/-/issues/556#note_216668
Thank you @blocktrades ....appreciate hearing from you.
Thanks for your hardworking 🙏
Something great to come... it make hive more interactive and User Friendly... 👍🏻
Thanks for the update, BlockTrades team. It’s exciting to see Hive focusing more on performance and scalability.
As a new user, I'm really looking forward to faster load times and better onboarding.
Will there be more updates for mobile optimization too? That would be great for users like me in regions with slower connections.
Keep building, we’re watching with hope! 🙌
Yes, the work we're planning related to API optimization will definitely be beneficial for mobile users.
Thank you a lot🌸❤️
Give my post like🙂
Quick question right here: why did you guys shutdown the web for trading HBD powered by you (blocktrade)?
Details here: https://hive.blog/blocktrades/@blocktrades/blocktrades-ending-its-cryptocurrency-trading-service-as-of-june-30th-2023-today
I haven't seen that before but thanks for notice me.
Wow, omg
You are your team are doing great work on hive blockchain, I so much appreciate the update
Thank you for the update. This helps me with looking into future project work. Much appreciated.
!PIZZA !PIMP
$PIZZA slices delivered: @fjworld(2/20) tipped @blocktrades
Come get MOONed!
i see greats updates coming soon, i would like interact with the API to captura my transactions information :D
That looks like a nice roadmap. Would it be possible to have multiple users transactions? I mean, the same transaction amount made to a list of users... Keep up the great job!
If you mean create a single transaction that contains multiple transfer operations that pay out to different users, you can do that now. It is easy to do programatically from a library like Wax.
If you're looking for an app to do it, instead of a library, I know at least Clive can do it.
Thanks for answering. I see there are some options using the CLI but of course those aren't friendly to normal users. I can't understand why it's not been implemented in a GUI already. Guess that if you need something like that, you need to do it yourself. I asked for it to Key Chain devs but they showed no interest. I will pick the thread of your mention about Wax library when I have some time to stop by. Cheers
Note that Clive isn't really just a CLI, it has a TUI (which is basically just a GUI that will also work on terminals).
Yes, a TUI is something at least, but not for average users though. It would surely fit my needs anyways, thanks for pointing me on that way ;)
This is a spine of steel, and we are grateful for it.
But even the most brilliant lattice of light and logic needs something older to stir it into life. A soul. A fire. A song.
While these APIs and lightweight nodes stretch toward speed and scale, elsewhere—beneath the noise—others have heard a different call.
The Brotherhood does not build instead of this roadmap.
We build alongside it. Within it. Beneath it.
Where this map ends—our path begins.
We’re not drafting code (yet), but we are drafting myth.
Not protocols—but prophecy.
We are the ones tending the ember.
The ones whispering in forgotten tongues of oaths and realms and ledgers carved in flame.
And when these APIs rise—like temples of glass and light—we’ll be there to fill them with stories that matter.
Mark my words:
There is more to Hive than function. There is more to freedom than bandwidth.
You have built the citadel.
We are building the song that will echo through it.
@blocktrades great and excellent
Great plan! I'm really inspired by Hive's future thinking. Lightweight nodes for mobile, smart contract prototypes — all of which are taking Hive a step further.