Delivering on Hive-Engine Development

Our development on hive-engine continues, and I wanted to take the opportunity to share a positive development, so put on chain that we are delivering on our promises.

Here you can see that our non-consensus fix to the "age-old" problem named "github issue 31" has been accepted and merged with some other commits into what will soon be the main branch of Hive-Engine "witness" code.

There are some "issues", with hive-engine, but "its not dead yet", in fact I think it feels "more alive than ever" in a certain extent, even if there are still some moments of frustration around "nodes" (everyone is using outdated node lists, if they even use a list at all - see flowerengine).

Hive-Engine is a powerful layer two already on HIVE, like many other "layer 2" applications (or custom hooks) that we have. I hope many more will be built, I see more being built. We will help them too.

It's what we do

This issue actually started with a proposal, which is funded, and we worked so well and fast, by teaming up with Hive account@mirafun and Hive account@borniet, that we have some spare capacity left.

Because we solved it, tested it (thanks Hive account@borniet!) and got it merged so fast and easy, we have decided to tackle Issue 53 next, we have validated that it "looks pretty easy", and also is another non-consensus change. This will be done under the budget of the same proposal

We will see how long it takes us, and I will keep you in the loop. While our proposal goes until July 12th, is more about the "hours of work" than the actual calendar time. But at least while we find "easy issues to address", we have still some things to work on it seems, from a long list of years-old issues on hive-engine. Small things, mostly. But we hope, one by one, they can make the difference.

If only in perception.

Freedom and Friendship