Below are a few highlights of the Hive-related programming issues worked on by the BlockTrades team since my last post.
This report is a bit late as I just recently got back from traveling to HiveFest and then traveling to Poland to meet with some of our devs there for a few days. A lot was done in that time, but I’m still time-constrained catching up with work that built up in my absence, so I’m going to make this a quick post and cover a few highlights of the past three weeks.
Hived (blockchain node software) Release candidate 3
Today we released what I expect to be the final release of hived for hardfork 26:
https://gitlab.syncad.com/hive/hive/-/tags/v1.26.0rc3
Fixes in RC3 are described here: https://gitlab.syncad.com/hive/hive/-/merge_requests/688 The most important change was the fix for the potential sync stall condition, but this was relatively rare and could be worked around by restarting the node. Other changes were just performance optimizations. No changes affecting hardfork consensus were made in this release candidate.
About a week ago, we released RC2: This release candidate fixed a few more significant fixes:
- Fixed api node crash when duplicate broadcast_transactions received
- fc:uint128 conversion to string wasn’t thread-safe
- Reduce number of block approval votes cast when switching forks
- Speedup shutdown of syncing node on slow hardware to avoid 30sec timeout that caused crash
We also worked on hived documentation, adding descriptions of new command-line options and config.ini options.
Call for Hive app devs to test against the mirrornet to prepare for the hardfork
At this point, more apps have successfully tested against the mirrornet, but I suspect that a decent number haven’t yet, so I again encourage any app dev who hasn’t yet tested their app against the mrirronet to do so ASAP. It’s really easy: just point at the mirrornet api node and change the chainid that your transaction-signing library uses.
Hive Application Framework (HAF) and related apps
We officially incorporated support for the get_block API into HAF (this will allow us to stop loading down hived nodes with get_block calls as these have traditionally been a very expensive call). We developed CI tests and benchmarks for the API. The tests allowed us to find and fix some differences in the results between hived and HAF. Hived is currently a little faster than HAF at serving up this API (although it uses more CPU power to do so) so we’re looking at ways to speed this up further.
During HAF hivemind testing we found and fixed a performance problem that occurred during livesync mode.
Work also continued on the HAF block explorer, with the focus still on the witness page right now. This is also informing some changes to the data collected by HAF via the sql_serializer.
Some upcoming tasks
- Test and update deployment documentation for hived and HAF apps (ongoing)
- Continue supporting Hive apps devs as they begin testing their app against the mirrornet
- More testing of hived release candidate on production API node to confirm real-world performance improvements
- Continued testing on the mirrornet
- Finish testing and dockerize HAF-based hivemind and use docker image in CI tests.
- Continue work on HAF-based block explorer
- Collect benchmarks for a hafah app operating in “irreversible block mode” and compare to a hafah app operating in “normal” mode (low priority)
When hardfork 26?
The new release candidate still has a date of Oct 11th, 2022 at 12:00 GMT for the time of the hardfork. Based on the relatively small number of changes made in the latest release candidate, I don’t currently see any reason to extend the hardfork date out further in time.
~~~ embed:1575369348704878594 twitter metadata:QmVuamFtaW5GdWtzfHxodHRwczovL3R3aXR0ZXIuY29tL0JlbmphbWluRnVrcy9zdGF0dXMvMTU3NTM2OTM0ODcwNDg3ODU5NHw= ~~~
The rewards earned on this comment will go directly to the people( @shiftrox, @lemouth, @yeckingo1 ) sharing the post on Twitter as long as they are registered with @poshtoken. Sign up at https://hiveposh.com.
How long have you guys been requiring KYC?
Hey @blocktrades, I've been getting this error for the past two days and I haven't seen any official statement anywhere.
Same thing on my side.
not good 😫
Looks like that is going to be it. I might test it if I get the time to do it, no promises yet though
Good job
Thanks for sharing the update, its helpful indeed.
Wow this awesome and keep up the good work moving.
hardfork hardfork hard at work! 💪🍻
biggest hardfork eveeer here we come
great job everybody!
Great post
11th of Oct, let's hope it will not change. Looking for this upgrade & thank you!
$WINE
Congratulations, @theguruasia You Successfully Shared 0.200 WINEX With @blocktrades.
You Earned 0.200 WINEX As Curation Reward.
You Utilized 2/4 Successful Calls.
Contact Us : WINEX Token Discord Channel
WINEX Current Market Price : 0.201
Swap Your Hive <=> Swap.Hive With Industry Lowest Fee (0.1%) : Click This Link
Read Latest Updates Or Contact Us
BTW, do you know where Holger is? Seems beem/py has no updates.
I don't know where Holger is, but BlockTrades guys and a few others have been doing some work on the copy of beem in our public repo: https://gitlab.syncad.com/hive/beem/activity
Thanks, that is very helpful :)
Muchas cosas buenas llegarán 😉
!PGM
!PIZZA
BUY AND STAKE THE PGM TO SEND A LOT OF TOKENS!
The tokens that the command sends are: 0.1 PGM-0.1 LVL-0.1 THGAMING-0.05 DEC-15 SBT-1 STARBITS-[0.00000001 BTC (SWAP.BTC) only if you have 2500 PGM in stake or more ]
5000 PGM IN STAKE = 2x rewards!
Discord
Support the curation account @ pgm-curator with a delegation 10 HP - 50 HP - 100 HP - 500 HP - 1000 HP
Get potential votes from @ pgm-curator by paying in PGM, here is a guide
I'm a bot, if you want a hand ask @ zottone444
PIZZA Holders sent $PIZZA tips in this post's comments:
@torran(6/10) tipped @blocktrades (x1)
Join us in Discord!
Congratulations @blocktrades! You have completed the following achievement on the Hive blockchain and have been rewarded with new badge(s):
Your next payout target is 1880000 HP.
The unit is Hive Power equivalent because post and comment rewards can be split into HP and HBD
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 the last post from @hivebuzz:
Support the HiveBuzz project. Vote for our proposal!
You are committed to what you love doing the fact that you still have to drop this information, Knowing you are going to the Poland, I respect you for that most people will just feel lazy to do that i might too because traveling of coming back from a trip means you need a rest thanks for sharing, I hope you have a little of rest when you get to Poland.
I'm actually back from the Polish trip now, and I'm just catching up on all the work that built up while I was gone (one of those items was writing this report)...
Okay well from you trip hope you enjoyed it.
I have known blocktrades for a while now and they are always reliable and their service is fast and convenient.. keep up the great work..
Looking forward to this - thanks for the update mate.
Congratulations @blocktrades! Your post has been a top performer on the Hive blockchain and you have been rewarded with the following badges:
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 the last post from @hivebuzz:
Support the HiveBuzz project. Vote for our proposal!
hey, I know you are busy with HF26, but something just popped up in a conversation with Marky that I wanted to ask you about. He said that he thinks that you have somewhat changed your mind on implementing smart contracts on layer 1; is there something to this?
I'm not sure what you mean: I've always said it made more sense to implement smart contracts on layer 2 instead of layer 1.
exactly, that was what I thought so too. But Marky made some comments the other day on discord that suggested that you were thinking about implementing smart contracts on layer 1. I just wanted to verify your position on this
It there any time frame for implementing smart contracts on Hive?
currently, I actually thought that it is not planned as blocktrades said that they are better on layer 2
Hey Dan, are we still on or the HF tomorrow?
Seems so, looks like witnesses are onboard, supermajority is running v1.26.0: https://wallet.hive.blog/~witnesses
Brilliant. Looking forward to it. :)
Flawless. Great job!
Excellent 👌 post
Very good work!
I loved it
Consider dropping witness votes on those powering down and support witnesses that are powering up? shakes things up, you have the stake to change things and support so many that are powering down...
Dear @blocktrades
I am hoping you can consider voting on this proposal if you think it could be helpful for communities and hivers in general. Any help, collaboration, or constructive criticism will be welcome.
You can vote here:
What is hafah app actually?