Below is a list of Hive-related programming issues worked on by the BlockTrades team during the last week:
Hived work (blockchain node software)
This week we’ve been testing the first release candidate for hardfork 25. In addition to manual testing of node operation, we're also writing a few more tests to test consensus changes under stress conditions.
Although we haven’t found any bugs in the new consensus changes yet, we have made several fixes to long-standing bugs that we found as part of our manual node testing. Most of the bugs are related to startup issues and confusing log messages that might mislead a node operator:
- We fixed an error message that erroneously reported that a peer node was on an irreversible fork when it most likely was just ahead of the user’s node.
- We fixed a long-standing error that could cause a crash at startup if a node started receiving API requests before the node had fully initialized.
- hived now reports the peer count in warning messages when the blockchain thread is warning that it hasn’t received any transactions or blocks from the P2P thread in the last 30 seconds.
- Hived now delays connecting to seed nodes until the P2P network is initialized and ready to process peer requests. This prevent seed nodes from disconnecting because the user's node doesn't respond to them in a timely manner.
- ulog messages are now logged to stderr (console) for the node. Ulog messages are used by the P2P thread to report important issues that should be seen by node operators. In particular, the user now receives a console warning when the node startup is delayed while the P2P thread is trying to get access to the P2P port from the operating system (when a node is shutdown via Ctrl-C, the OS may take up to 1 minute to release the port, delaying recapture of the port when the node is restarted).
We’ve also updated hived nodes to begin reporting the Hive chainid of BEEABODE at startup (as a temporary measure, the node used to report a chainid of 0 at startup, then swap to reporting BEEABODE after they hit the genesis fork for Hive).
For the initial release of hardfork 25, hived nodes will still continue to allow connections from nodes with chainid of 0, despite reporting the new chainid, but after all Hive nodes have updated to the hardfork 25 code, we’ll change the code to reject connections from older nodes.
Second release candidate for hived soon
We’ll likely be publishing a second release candidate of hived in the next couple of days that contains the diagnostics and fixes discussed above (those changes have already been merged into the develop branch, so you can get them now for testing), plus one or two more small improvements that are still pending review.
Hivemind (2nd layer applications + social media middleware)
We’re continuing to work on a few hivemind tests, running performance tests, and preparing database migration scripts in preparation for a new hivemind release (should be sometime this week).
Modular hivemind (framework for hive applications)
We still didn’t have time to make the changes for the sql serializer last week due to the time spent fixing the various issues discussed in this post, but we will likely? complete that work in the coming week. Then we’ll be able to do a full performance test of the sql serializer in combination with a full sync of hivemind.
In the meantime, we’re doing preparatory work to create an example modular hivemind-based application that just supports the account history API.
Condenser (code base for https://hive.blog)
We’re testing condenser code against the testnet. We had some problems with condenser being able to broadcast transactions to the testnest which were ultimately traced to condenser using an older version of the hive-js package. It’s being updated currently and testing will continue. The same change will also be applied to the condenser wallet.
Hived testnet
We launched and began testing the new public testnet based on release candidate 1.
We’ve also setup an API node configured to draw data from the testnet. This API node should be used by Hive applications to begin adding code changes to support new features added by the hardfork, such as vote expiration reporting.
If you want to add a node to the public testnet, use this seednode:
p2p-seed-node = testnet.openhive.network:2001
To use the API node for the testnet:
API endpoint via jussi: https://testnet.openhive.network
hived direct http server: http://testnet.openhive.network:8091
hived direct websocket server: ws://testnet.openhive.network:8090
hivemind server direct server: http://testnet.openhive.network:8080
As mentioned previously, we’ve begun testing this testnet API node with condenser. You can visit it here: https://testblog.openhive.network
We will also setup a block explorer and a condenser-based wallet for the testnet soon.
Update: @ausbitbank added block explorer for testnet https://test.ausbit.dev/
We plan to leave this testnet running as a permanent testnet that apps can use to test against prior to making changes to their app operating on the mainnet. So Hive app devs are strongly urged to take advantage of this opportunity. As a side note, when doing so, please make sure to use the latest version of hive-js to make sure it's compatible with the testnet API node. We've also tested beempy successfully against the testnet API node.
Planned date for hardfork 25
I’m still projecting the hardfork will be in the latter part of June, probably in the last week.
I am eagerly waiting for it. Hopefully it will increase the engagement in the comment section.
yes me too
faster better stronger :)
I think Modular hivemind can be a big thing for dapps ( if I understand it right).
What about your sidechain? Will we see it this year? :D
I hope so. It will be built on top of modular hivemind tech, which I think we will be able to release in a month or so.
top!
@blocktrades please add maim net @telosnetwork and add popular hive engine tokens like LEO and others
Please
Posted using Dapplr
It's a decentralized platform, everyone doing anything on mainnet is more than welcome to join testing efforts on testnet.
Esperemos que todo siga para bien. Feliz noche
Something good is coming... thanks for the updates
Sweet. Gives me even more reason to get my testnet node up now. :D
Communities I run: Gridcoin (GRC)(PeakD) / Gridcoin (GRC) (hive.blog)| Fish Keepers (PeakD) / Fish Keepers (hive.blog)
Check out my gaming stream on VIMM.TV | Vote for me as a witness!
btw I have another question :)
There are plans for something like SMTs, so hive would be able to move rewarding to the second layer and become the first layer more efficient?
Because I have the opinion hive should be a gas/gov token. And we had a super long " mining period" already.
Rewards for each niche token also work better on the second layer because of possible revenue models, hive cant touch on the first layer.
Or is there no plan out in this direction?
Yes, we're planning to build 2nd layer tokens based on our 2nd-layer smart contract system.
That's good. As far I remember with a new token right?
If most actions comes for rewarding and Token mechanics from the second layers, do you think Hive will transform from a reward token to a government/gas token?
I ask because smart contracts would open new doors and hive can be the place for balances for example :)
BTW, I think the smart contracts would change a lot of things :) Really nice this is on the horizon :)
Yes, I think the above is quite probable.
Congratulations @blocktrades! You have completed the following achievement on the Hive blockchain and have been rewarded with new badge(s) :
Your next target is to reach 120000 upvotes.
Your next payout target is 1150000 HP.
The unit is Hive Power equivalent because your 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!