Continued progress on Hive-Engine Issues

Its one of the things we are working on (yes I know I said I would "take a break", and that is for sure "coming soon" 😅, just gotta let the pipeline run its self through a bit), is "how we work together". Being social is probably the hardest part of developing new technologies, and finding a team to work with, developing work flow with such a team, figuring out the things that you don't know, knowing who to ask and in what way to ask about them - all these things are social phenomenon that "need improvement", and I hope that by documenting my process and progress, we are not JUST getting things fixed, but also encouraging others about how things get fixed and how working together happens.

So as I mentioned in a previous post, we are getting some funding from the BEE DAO through this proposal, and we did so good that we would continue to push on to other issues. Read more about that at the bottom.

First, an update:

12 days ago I reported on our PR from ISSUE 31- FIX, which was the original intent to deliver for the above grant proposal.

Not only has it been accepted now, I am also delivering on the payments! First I paid @mirafun 160 dollars, in two parts:

Payment 1

Payment 2

This 160 includes scoping and research, as well as the development of the solution and testing. Some of this time spent was figuring out how to work with hive-engine, which we are getting some good experience with now.

I also sent myself ~90 dollars, as being a project manager is not "free", it takes a lot of time and effort to coordinate all of this:

The magic sauce: @borniet

What I believe to be the magic bullet we found, to make this fast and cheap, was my brilliant idea to reach out to @borniet. @mirafun could have spent hours and hours spinning up a node to test this fix on, but instead we reached out to a node runner @borniet, who was happy to work on something to help the development of hive-engine with his @botlord node.

After testing our fix for issue 31, he even was so motivated as to go on and help @eonwarped test another fix having to do with the "comments contract", I am happy to say that we "helped" get that fixed as well by creating a spontaneous "test net of the willing", and I have just including those additional costs here under the same proposal framework.

@borniet's @botlord node is now up and running again, currently ranked 17th on the official validators list:

So go ahead and give @borniet your workerbee votes here, he is eager and helpful guy with such things, and we might definitely work with him again!

Payment to @borniet

For his help, and time, we have sent @borniet a payment of 500 BEE, at his request, which he preferred over HIVE or swap.HIVE. I think he might be doing something with BEE, but that of course is his own personal choice!

Thus concludes the saga of Hive-Engine Github Issue 31

And there remains some budget left, and now that all the payments have been made and the pull request accepted into QA branch with other recent fixes, we can move on to "the next thing".

Of course we have not been sleeping...

But that is a story for another day!

Freedom and Friendship