HF28 v1.28.0
HardFork is not something that we do very often. That's because Hive is pretty much feature-complete on Layer1 and already a perfect tool for a variety of use cases where a fast, secure, and decentralized ledger is needed. We are doing lots of work on Layer2 (not in the scope of this post), but from time to time there are certain upgrades and fixes needed at the very core.
As discussed during the Core Devs panel at HiveFest 10 (Kuala Lumpur) earlier this month, the code for HardFork 28 is ready.
If you missed the panel, here’s the recording:
Time is set for 2025-11-19 13:00:00 UTC, if all goes well over the next three weeks and witnesses/stakeholders give it a go, it will go live at that time and once a supermajority of the top elected witnesses decide to run that version.
Test your stuff now
There’s still time to test your apps against the upcoming version using the mirrornet API node before we go live.
- API endpoint:
https://api.fake.openhive.network - Chain ID:
42 - Keys: in most cases you can reuse your mainnet keys
- Notes: treat it like a mirror/fake network; double-check you’re pointing at chain-id 42
For background, see my earlier posts about the mirrornet. If you already know what you’re doing, just switch your client to the endpoint above and run through your usual flows.
Changes
Based on the GitHub comparison, there were 4,036 commits and 5,197 changed files (331,273 additions, 648,056 deletions). That's of course simplified view on the master branch and only for hived repository itself. I'm not even including libraries, submodules or tests. Here's a simple visualization of a Hive consensus node source code tere and the changes that were made between version 1.27.0 and 1.28.0. I simplified it and smoothed it out for the sake of making it prettier (timestamps are normalized, and HEAD directory tree is used as base for init). Then of course image processing that took 77GB of raw, 60fps, 4k input and produced 10MB blog friendly webp output.
You are welcome ;-)
Read the highlights in the release notes
Known bugs (unlikely to block the HF)
Nothing so far that should stop us from proceeding with the upgrade. Current items on the radar:
- Snapshot loading/dumping issues - fixes will land in the next minor release.
- Claiming account creation tokens - that's more concerning at the moment; I've experienced similar issues on the mirrornet before, but at that time we were blaming the specifics of the environment, where multiple block producers were sharing the same state. That's under investigation. Kudos to @engrave and @techcoderx for spotting that behavior on the mainnet (and paid with battle scars by @engrave)
Consensus witnesses: please keep an eye on the https://openhive.chat/channel/witness channel and on-chain communication. Test your backup nodes first for few days and check the logs before running it on block productoin node, unless you know what you are doing. Especially if you haven't tested it on the mirrornet before.
That’s it for now. Please test, report anything odd, and get ready for HF28.
Lol, no! And just for the record, bug with claiming tokens is fixed. Thanks to @small.minion for spotting source of the issue, many people analyzed the code before and missed it.
I know, I know, I'm aware of your list ;-) Sure it can be better and we are going there one block at a time. I just mean that it's already awesome :-)
Good job @small.minion!
I have managed to get it running on my back up node on the main net. I haven't encountered any issues so far.
My main node is replaying now. Hopefully it all goes smoothly. :)
As a new witness, and as my first hard fork, (and not being ranked very high) I feel like I can accept this level of risk to my block production history and risk any missed blocks. Anything I learn, I'll inform others. I haven't learned anything so far :)
I prefer a couple of missed blocks now rather than a halted chain later ;)
That's the spirit! :-)
I see no visualization!
Maybe webp isn't supported by your browser or was errorenously cached? Hard to guess.
The link is here
(
https://images.hive.blog/DQmRtu6jM9RQZsGgPsSiughPE6VeMcYiBqUuzf7WgRmgYtR/hived-1.28.0.webp)Please note that the file itself is 10MB so it might take a while to download on slower connections (or if provider or some other intermediary is "optimizing" network bandwidth by compressing assets it might get broken).
¡Qué bueno es ver que vienen mejoras como estas! Aunque no tengo conocimientos técnicos, me emociona mucho saber que todo esto puede hacer que publicar sea más fácil y rápido. A veces uno quiere invitar a un amigo a usar la plataforma, pero se complica porque hay que entender muchas cosas para poder participar. Si ahora será más sencillo, ¡seguro más personas se animan!
Gracias de verdad por compartir esta información, se nota que hay mucho trabajo detrás. Un gran abrazo para todos los que aparecen en el video y para el amigo @gtg que nos trajo estos detalles. Me costó entender por la falta de conocimiento en esta área y hablo solo español
Thanks for sharing , that was a great video. I am excited about the upcoming updates and their potential major impacts.
!PIZZA
@tazi, doufám, že jsi tohle zaregistroval ;)
Ano, mám v kalendáři ;)
Budu ten týden v ČR, tak se budu snažit být ready...
Super. Vím, že ostatní už to testují ;)
Já se tentokrát k testování nedostanu... Respektive uvidím, jak se bude vyvíjet práce tady (opět CH) a pokud vyjde čas, testovací server mi doma běží... Uvidíme.
how helpfull wil it be to run a node on a pi4 or a proxmox VM on my home connection ?
For the network? In the range from not really to not at all ;-)
I would make sense only if you yourself want to use it somehow.
Awesome panel! Thanks for sharing that, and the rest of stuff in the post I guess.
I need to go watch the whole stream soon once workload has let off a bit :D
I haven't been in the loop on this... What does Hard Fork mean in this case? Does this mean like how Steemit was Hard Forked and Hive was created? Is there gonna be a new Hive or?
HardFork means a change of rules, for example making something that wasn't accepted before will be valid now, or what was allowed previously, now will be forbiden.
In Hive world it doesn't mean creating a parallel new chain, it's just an upgrade where (usually) the other fork becomes obsolete and cease to exit.
Ah I see. Ok thank you for the info.
That the HF28 code is ready is good news. We now wait for what the majority decides.
Actually you could do way more than waiting. You are a Hive user, with non-zero HIve Power, which is similar to owning a shares in a company, except in our case there's no company, but community driven blockchain platform.
You could vote for witnesses (like me), who keep the platform running. There are up to 30 witnesses that you can vote for, here's the list: https://explore.openhive.network/witnesses
You are, as a Hive user, a decision maker! :-)
great, is there a TL;DR for the major changes?
Yes, release notes: https://github.com/openhive-network/hive/releases/tag/1.28.0 are something you are looking for or the video above from Core Dev Panel played at x2 speed.
Hmm, Signature Flexibility looks like it might be very relevant for me. Is this just to allow redundant ECDSA signatures, or could this allow adding signatures of other types?
I'm looking into piggybacking hash based signatures into transactions for a proof of concept ("Adding extra custom_binary operation to transactions" section). If I could add my own hash-based sigs as redundant signature that would simplify my attempts to piggyback hash based signatures quite a bit.
Unfortunately it's not the signature flexibility you are looking for ;-)
What will be the change for us mortals? I heard vote power will always be 100% but limited amount of votes per day...
Yes, it will be more intuitive for voter, in reality it doesn't change much from user perspetive. Optimal is to vote up to 10 (100%) votes (or 20x 50%, or 40x 25%) per day, and to vote with same value to every post you would have to vote every 2.4 hour. After the change you won't have to be a bot in order to cast optimal, 100% votes.
You really should discuss the key access changes more. There are definitely accounts who don't have all keys who have no idea they will be locked out of wallet. It is silly anyone wouldn't just open new account when they don't have master key? Yes really foolish. But there are probably a few who have no idea if the key they'd been using since 2017 is even wallet key or a higher authority they'd worked until now. Foolish choice but kinda lame how badly this has been discussed and shared. Those people deserved 13 weeks to power down in worst case so they don't forever loose access. Nobody mentioned this key thing anywhere, only in this clip. It's gonna affect more people than u think. Regardless how dumb it was to not start over as soon as they learned system, they deserved more time. Oh well
That’s at least what it pretty clearly says in this clip. If I’m mistaken please let me know.
But that doesn't lock them out of their account.
What scenario you have in mind?
Just to clarify, Master Password is just a concept of a secret that keys are derived from.
From what I understand you are worried that someone is using owner key instead of active without even being aware of. In such scenario it will stop working because owner key is no longer allowed to be used to do the active key's job, but in such case user still can use the owner key to set a new active key.
If however, a user have lost his owner key, there's nothing that could help, and nothing that upcoming version changes in the situation.
No, I’m saying there’s many without master, but they’re been fine using lower keys yes there is. Giving him the info that this change was coming at least 13 weeks prior so he can power down. Again there’s now 4 accounts on discord effected by this. That tells me there’s more. They were incredibly foolish not starting over , but for 6 years lower keys worked for wallet and they’ve been fine functionally. This should have been the big headline but most people do not even know.
Again it’s on them for whatever dumb reason it they chose the inconvenience of starting over instead of how important it was to get a new account to have a master key, but I’m just saying knowing active daily accounts are out here who don’t but function wise they just use posting and some random higher key for years to move value, I just think this should have been better announced and I understand why people are pissed off.
You've misunderstood the change. This change cannot result in you losing funds or being unable to powerdown. I don't know what 4 accounts you're talking about, but they are just confused.
Than they misspoke in this clip, because word for word you can no longer use higher authority keys for other actions. That is what was said, again not a issue for me, but as dumb as it was there were accounts who don’t even understand there keys and are missing half of them , then they hear a week b4 this is changing. I’m with u that is beyond foolish! But just wish this wasn’t so confusing. They say in clip , now you say no not case?
Let me make sure I’m saying it right, and yes nobody’s saying this account was not incredibly foolish! - One guy doesn’t even know what key he’s been using for wallet, he just knows it works. He hears after fork higher authority keys will no longer work so he’s concerned, he’s also missing master key since 2018. Whatever is working now will still work? He wrote down wallet & posting, and has just never started over which he should have but anyway that’s the case I’m talking about.
PS- I appreciate the direct reply 👍
Much thanks!
Will it be 10 votes fixed per day or the amount depending on your HP stake?
Rules are same for everyone, regardless of HP. HP impacts only amount of rewards that such vote can assign.
Ok thanks, that's clear, hopefully front ends will be ready for this change
I am confused. Will I still be able to vote < 100% or will 10 100% votes be the only option?
I couldn't find this being mentioned anywhere in the release notes: https://gitlab.syncad.com/hive/hive/-/releases/1.28.0
Edit: found it under
1.27.7notes, sounds like it should be added in 1.28.0 as well.Always love seeing a good gource render.
I just got my main node switched over to 1.28.1 after letting my backup node replay the chain a couple days ago.
It's getting really fast and super simple to maintain witnesses these days. love it!
yeah... ;-)
Exciting times ahead for Hive! Always great to see the dev team keeping things evolving smoothly.
Are light accounts rolling out in this fork or are we holding off for the next one?
They are not part of current changeset, and AFAICT their implementation doesn't require consensus changes so I suppose we can expect them before the next hardfork.
automagically
nice one @crimsonclad :D
N/p. It's a favourite of mine~
lol. :)
$PIZZA slices delivered:
bhattg tipped gtg
@geneeverett(6/20) tipped @gtg
Come get MOONed!
I enjoyed the video
I hope you continue to reap success. Very interesting. Congratulations.
Great work!
Congratulations @gtg! Your post has been a top performer on the Hive blockchain and you have been rewarded with this rare badge
You can view your badges on your board and compare yourself to others in the Ranking
If you no longer want to receive notifications, reply to this comment with the word
STOPCheck out our last posts:
Wow! Thanks for sharing that to us. I am very excited on your next update!
can't wait..
Congratulations @gtg! Your post has been a top performer on the Hive blockchain and you have been rewarded with this rare badge
You can view your badges on your board and compare yourself to others in the Ranking
If you no longer want to receive notifications, reply to this comment with the word
STOPCheck out our last posts:
Did this go through?
HardFork 28?
Scheduled to happen, see https://hive.io