Below is a list of Hive-related programming issues worked on by the BlockTrades team during the last week or so:
Hived work (blockchain node software)
We released a second and third release candidate earlier this week with several fixes and improvements for testnet-based testing:
But we found some more issues associated with those release candidates and we also decided to reduce the vote powerup delay to one day for the testnet (this value is configured for 30 days in the mainnet) to simplify testing scenarios where accounts stake their coins and then vote in new witnesses. So we’re about to tag a fourth release candidate for hived (probably will be tagged tomorrow).
We’ve actually launched a new testnet with an untagged version of the planned release candidate to get the testnet jump-started quicker (we're simulating a transition of the code from HF24 rules to HF25 rules in this release and the transition test is scheduled for tomorrow so we wanted to get the testnet up as fast as possible). We haven’t tagged the new code yet as 1.25.0.rc4 because some of the automated tests failed when we changed the vote powerup delay for the testnet, but we’ll tag it after we have committed updated tests. As part of the changes to the tests, the response checking will be modified to test for the configured delay value rather than a hardcoded value, to avoid a repeat of this issue in the future.
I’ll add a link here to the new release candidate after it’s tagged.
Hivemind (2nd layer applications + social media middleware)
Earlier this week, we merged develop branch changes to master and released a new 1.25.0 version of hivemind (so just pull from the head of the master branch to get the new version), and now we’re assisting API node operators as they upgrade to the new version. Note that the old version and the new version are broadly API compatible: most of the changes in the new release consist of bug fixes and performance improvements.
Currently the API nodes for api.hive.blog (@blocktrades), api.deathwing.me (@deathwing), and api.openhive.network (@gtg) have been updated to the new release.
Also, to eliminate the multi-day hive sync requirement for anyone setting up their API node for the first time, @gtg has provided a hivemind database dump for the new release that can be used to quickly initialize a new API node: https://gtg.openhive.network/get/hivemind/
Modular hivemind (Application framework for Hive apps)
We’ve been working on the documentation for modular hivemind’s internal architecture this week and doing individual code reviews. We have a meeting scheduled Monday to do a group code review. After that meeting, I should have a better idea as to when we can expect an initial release of the software, but from what I’ve seen so far, I’m thinking we could make it available for beta testing next month.
An early draft of the documentation for the architecture is here: https://gitlab.syncad.com/hive/psql_tools/-/blob/23239a592bd77b3b2cefc648e5c25880e0f76ffb/src/hive_fork/Readme.md
We’re seeing more apps join in and hookup up test sites to the testnet. Note that as a regular Hive user, you can typically login with your normal credentials and test via these sites.
For example, you can login to either of these blog sites on the testnet
https://testblog.openhive.network (hive.blog-like testing site)
https://testnet.peakd.com/ (peakd-like testing site)
You can also browse the testnet with this block explorer: https://test.ausbit.dev/
New testing tool for testnet
We’ve also created a new tool to convert an existing block log to a testnet block log to ease creation of more realistic “real-world” testnet-based test scenarios. The new tool is undergoing testing now.
Tentative date for hardfork 25 is June 30th
Release candidate 4 has the hardfork scheduled for June 30th. Assuming we find no further issues by late next week, we’ll make that date official, create an official release by merging the develop branch to the master branch, and notify exchanges of the need to upgrade their wallets.
Seems like testnet is getting less obscure and easier to test. This was my first time interacting with a preHF testnet anyway 😃
I think people are underestimating the benefits and potential for the sw architecture around modular hivemind. It is my hope that is spawns several similar projects. The idea that we could spin up a hived, choose our plugins, and function as an api node for whatever dapps or generic VMs is exactly the right direction
Yes, I agree. I really want to get started building apps on top of it as soon as possible.
Pretty exciting stuff. Will be good to get past this one ... so we can focus on the next one!!
Our next main focus will be on the app framework for building new Hive-based apps (no hardfork required for this work), although we will be taking a look at potential improvements to hived still, of course.
Oh cool. I am sure it is a balance of alternating hard fork required work and non-hard fork required to minimize the burden on exchanges by allowing enough time between hard forks but still making progress on the blockchain.
I did things on the testnet that happened off the testnet.
The powerdown and posts have also effected on the real net.
If you used keychain, you probably had your node set to a mainnet one(its what I did).
Oh, I guess I would have to change nodes, huh?
Yup, can do it in prefrceces, select your node and scroll all the way down to add node. Check the testnet button. Public node for testnet is https://testnet.openhive.network, chain id is
Yeah for hive keychain it's very important to change things. Using peaklock login on peakd no configuration needed but also using active key on peaklock is more of a pain.
My computer illiteracy strikes again!
Exciting to see the hardfork work coming to fruition and hopefully the date can remain for the end of June.
By the way, unrelated to this, it would be great to see if you want to support this proposal to make Hive the database of choice for the Podcasting 2.0 industry: https://peakd.com/proposals/181
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 1170000 HP.
The unit is Hive Power equivalent because your rewards can be split into HP and HBD
Your next target is to reach 94000 upvotes.
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
Check out the last post from @hivebuzz:
Support the HiveBuzz project. Vote for our proposal!
Wow how amazing that there is a new tool for testnet, every time new tools that can be used easily, I love that.
Awaiting June 30th like..
testing speed to comment
Informative and thank you 😊