Thread by @YoshiJaeger

Finally. My first #DigiByte update/AMA video is online. 🎉🥳🎊



There are huge news for $DGB, because several things happened in the recent months:

A small thread .. 🧵

The most time-consuming during the merge of 8.22 wasn‘t the merge itself. In fact I have been working several hundred hours to fix the functional tests and related issues in DigiByte Core. As I mentioned before, this is the first time we have working functional tests in #DigiByte

I wasn‘t very transparent with the progress because there was no end in sight when I completed almost half of them. Some really crazy and hard to debug bugs in DigiByte Core made it exceptionally difficult to fix some of the functional tests.

Sometimes it took days, even weeks, to UNDERSTAND and fix a single functional test.

My work yielded two separate PRs. The first PR will fix core issues and improve several network parameters, and RPC command outputs, etc. github.com/DigiByte-Core/…

Overall, this PR makes DGB more stable and reliable. Very important is also the second PR, that fixes the functional tests and allow for more innovation and progress in terms of features (such as algo changes) while making sure DigiByte Core remains stable (these are huge news).

The second PR can be viewed here:

github.com/DigiByte-Core/…

As you can see, these are 160 commits. It was a lot of work as some might imagine. Take a look yourself 😎

These two PRs will allow DigiByte to progress safely now, and will lead to more innovation and adoption.

As you know, several businesses started building on top of DigiByte. I feel there will come more.

The most important thing for businesses is that they can be sure the technology they are building on is safe, reliable and properly maintained.

This is the first time in history DigiByte has working unit tests, fuzz tests and functional tests.

Together with the new contribution guidelines and DIPs, this sets DigiByte on a level with Bitcoin‘s development process of atomic PRs with perfect continuous integration.

For all who have been waiting, I have also published the very first DIP (in fact it’s the second, but the first that will lead to a PR).

This DIP will allow the community and developers to choose new subsidy behavior parameters and introduce a fix in a very documented way.

This PR of the DIP is a work in progress, but it contains a very neat simulation script written in python to make sure we can choose very exact subsidy parameters, that will lead to 21B DGB in existence (no single satoshi more).

github.com/DigiByte-Core/…

I hope you like the announcements, I hope I didn’t promise too much.

In my opinion DigiByte now is more perfect than ever before.

The path is clear, and we have some amazing people in the community that will help leading DigiByte to the inevitable adoption it deserves.