Below is a list of Hive-related programming issues worked on by BlockTrades team during the last few weeks:
Hived work (blockchain node software)
We finished implementing and testing the following hardfork 25 changes:
New operation and associated API calls to convert Hive→Hive dollars (HBD) as a means of improving upside pegging of Hive dollars. For more information, see https://hive.blog/hive-102930/@blocktrades/proposed-hardfork-change-to-stabilize-hive-dollar-s-tracking-of-usd-value
Hive dollars must be stored in a savings account to earn interest. For more information, see: https://hive.blog/hive-102930/@blocktrades/proposal-to-make-hbd-interest-payable-only-to-savings-accounts
Completed testing and created examples demonstrating functioning of new curation reward rules
New unit tests: https://gitlab.syncad.com/hive/hive/-/merge_requests/195
Fixed small issue that caused vote expiration to happen one block later than it should
Allow votes on posts after they have paid out (votes once again allowed on posts older than 7 days)
We also reviewed @howo support for recurrent transfers in HF25 and expect to merge those changes in tomorrow.
Other work on hived
Removed support for COMMENT_CONTENT_SUPPORT
Improved reporting and debugging capabilities of unit tests
Allow running a subset of the entire suite based on a filter
Updated get_config API call with new configuration variables
Proposal ids are now reported by proposal-pay virtual operation
Clear the memo key of hive.fund as requested by @smooth
Fix the version of hived reported when SMTs not enabled
Fix a problem with static builds and libreadline
Currently we’re using C++14 for the hardfork. We tested with C++17 and found one bug, which we fixed, but decided to delay making C++17 the standard version for builds since we’re getting close to hardfork time. After the hardfork, we’ll likely move to C++17 or C++20 for future development.
Hivemind (2nd layer applications + social media middleware)
Fixes and improvement to community mute functionality
Fixed pagination of bridge.list_community_roles
Modular hivemind
We’re making solid progress on modular hivemind, especially with regard to fork resolution handling. It looks like we’ll be able to avoid the need for a C extension to postgres and can instead rely on a “SQL-only” solution using “shadow tables” to save and restore changes to the tables that store data that can be changed when hived switches to a different micro-fork.
Condenser
We made several fixes to condenser and also reviewed some new features by @quochuy and @jpphotography.
Upcoming work
Hived code freeze and launch of testnet
We plan to merge in the remaining hived code changes (a few minor fixes + recurrent transfers support) tomorrow, then assist in launch of testnet on Wednesday.
We’ll test for two weeks, then hopefully be ready to merge the release candidate into the master branch, at which point we’ll give exchanges at least 30 days notice to update.
So if no problems, we can expect the hardfork in about six weeks from Wednesday.
Test latest hivemind changes
We’ll be running a full sync of hivemind with the latest changes, then test real world performance in a production environment on api.hive.blog, followed by a production release to the API nodes next week if no problems are found.
SQL Account history plugin for hived
We plan to complete the changes to the SQL account history plugin that pushes data to postgres (eliminating the need for hivemind to pull the data via RPC calls) in the new couple of days.
After the plugin changes are completed, we’ll run a simultaneous replay of hived with a full sync of hivemind to measure the speedup, and see if it matches our expected improvement in hivemind full sync time (we expect 2 days versus the current 4 days required).
Amusingly I was just thinking "it's been a while since I checked on BT to see if they have a new Hardfork Update post, I should check..." And here it is. Great work y'all are doing. I like the idea of putting HBD into savings. So much so that I already put mine in there! All 30 of them! 😅
When it comes to savings, some is better than none :-)
I am currently also close to 30. I currently have $26.632 HBD, and its current estimated value is ~$34.052 USD.
I will also put them into savings to earn interest on them.
I invite you for some !PIZZA.
Wow! You must love pizza! :)
Yes, I do.
!PIZZA
@mattbrown.art! I sent you a slice of $PIZZA on behalf of @xplosive.
Learn more about $PIZZA Token at hive.pizza
Thanks for the !PIZZA. I'll check it out. Just spotted your name in the top 50 daily users today. Well done.
@mattbrown.art, sorry! You need more $PIZZA to use this command.
The minimum requirement is 20.0 PIZZA liquid, and 0.0 PIZZA staked.
More $PIZZA is available from Hive-Engine or Tribaldex
@xplosive, sorry!
You can call the PIZZA bot a maximum of 10 times per day.
Nice work like always.
Some questions. RC delegations will come a bit after HF 25 right? I think it should come fast after because it allows power users to pay the transactions for users without share voting/inflation power.
It's a bigger deal we all think about. It makes hive 100x more open and better to scale. Today we don't have many reasons to power up millions. With this there will be a real usecase.
I think it's a really big deal.
Another question is, what do you think should have a community-driven marketing proposal?
IMO it should expand over web 2.0 with interviews to tech people like youtube and co. Hive is a niche in a niche. So marketing is needed, but we should have some reward mechanics for that work. Onchain posts are very good, but offchain are the masses we want to tell about hive :)
It's too early to say how long resource credit (RC) delegations will take, but I guess we'll have some idea in a couple of weeks. @howo is going to research this task.
I'm a little more skeptical of the immediate impact of RC delegation, however. In order for an app to want to power up to supply RC for a ton of users, it first has to gain those users. So I think that will be the primary challenge (creating an attractive app for the masses).
I'm not terribly involved in the marketing side of things, but there is a marketing proposal right now, and I know they are always looking for people to help out.
It sounds like you're talking about some kind of "grass roots" marketing proposal that pays out to people who market on other platforms. To some extent, I think we've seen large stakeholders already do this, by sending posting rewards to people who participate in such campaigns.
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 1115000 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
STOPSupport the HiveBuzz project. Vote for our proposal!
Thanks!
I'm not sure was anything decided on the power down period?
There's no change to powerdown time in HF25.
I think it is a bad idea. I rather you not until Hive surpass and maintain its fair value of 2b+ and user growth isn't based on advertisements nor marketing. Or if we do have it based on sustainable growth. Hive is strong enough to reduce the power down to 11 right now. Within 24 months It can probably be knocked down to 9. I think the floor should be 7.
We have to change our culture some and have not only more education on the design (stop shaming liquid Hive sellers). But be honest about the limitations and challenges we face and why we fight the way we fight... Otherwise, it is easy for any Joe Schmoe to come and dent sentiment.
Dan... let's make up. You tried my gangsta first.
I might be a free agent soon. I have some grievances to air concerning the CCP soon... ESG investing matters. Tron might be independent now... Justin & friends fight hard.
Research Methods is the only class I paid attention to. It is impossible to capture all the variables, let alone developing variables. Imagine ignoring a large hovering extraneous variable that is in fact the apex variable...
Example
Tron-USDT is now at 400B, they put my homie (unconfirmed) in entrepreneurial jail to seize control. Swap all the Yuan with the Venezuelan bolivar, or the Turkish Lira, and then stage something that causes an influx into the dollar.
Quite frankly I would contemplate suicide If I were the type to be driven by greed and selective ignorance. White women won't let me, but still, I'd live the rest of my days in misery. I'm going to lay down now. I don't feel so hot.
Pi-kaPika
Lol. Wut? Yes, get some rest.
Your efforts are appreciated.
Thank you
Hope all goes well with the testing, I know a lot of work has been done, and the halving of the replay time should help the developers and witness types, I am sure it will help us non-tech types also in quicker response to issues.
I listened to the dev talk, and want to say thanks for continuing with the keep it simple first then if need be we use a more complicated route.
I didn't think to mention it in the post, but the new code to reduce sync time also dramatically reduces cpu loading as well, so it should also enable an API node to be operated with lower power hardware.
I've seen a few post from witness and want to be witness or node runners talk about the power issues and cost of equipment, it seems you all are trying to keep node cost down for those that want to run one which in the long run for people like me is good, because we hate when nodes go down and funky things happen.
What is exactly modular hivemind? Can you (or anyone else who's willing) make a post in depth explaining it?
I roughly understood that it's an easy way to run a sidechain without having the data for other apps.
Modular hivemind is what is sometimes referred to as an "application framework", a code skeleton that can be built upon to create an app. In this case, it's an application framework for making efficient, responsive, and scalable Hive-based dapps that also properly support fork handling.
Here are some obvious fixes that you should also consider.
The Hive.blog site is extremely slow and is getting slower, improve speed.
The search function does not work - fix it.
Comments cannot be seen immediately after making, unless a refresh of the browser page - also needs fixing.
Votes cannot be seen immediately after making, unless a refresh of the browser page - also needs fixing.
Thanks.
Cg
The search function has already been fixed by @quochuy and will likely be deployed in the next day or so. I've tagged him here so he can consider the changes you've suggested above to cache comments and voting and display them before they get processed by hivemind.
I believe the comment/vote bug is already logged in our issue tracker. I will work on it asap.
This actually brings a tear to my eye. For five years I have been asking for the search function to be fixed. Thank you @quochuy!
Cg
thanks for sharing these updates, even i am not that into coding and the really deep technology behind it :)
Yok bisa yok