Thread by @YoshiJaeger

#DigiByte Development Update Jan 4th, 2022:

While it may seem there is no progress in regards of DigiByte v8.22, the opposite is the case.

Why is it taking so long? Please allow me to explain.

🧵 1/7

$DGB

This is by far the most complex merge that was ever done for the #DigiByte Core codebase.

1) $BTC developers have gone mad with their codebase, which is a very good sign. The code's structure and quality has risen immensely. Many new features and bugfixes were introduced.

🧵2/7

2) We have to make 120% sure that the core features of DigiByte remain intact. We all want DigiByte's features such as DigiSpeed, DigiShield, MultiAlgo, etc. to stay perfect and bugfree.

Those are the things that make #DigiByte great 🔥
We can't afford introducing bugs.

🧵 3/7

That being said it's the first time since the existence of DigiByte that we are working on adapting ALL unit/functional/fuzz tests to resemble DigiByte's features and parameters
ELI5: Those tests are automated checks to ensure operability throughout this and future releases
🧵4/7

Many small-midcap #altcoins do not have those fixed because it's indeed difficult and exhaustive to debug, maintain and adapt the code that consists of seemingly infinite lines of code.
However, this time, me and others are here to make sure this will be done properly.
🧵5/7

TL;DR: This will be the MOST COMPLETE #DigiByte Core release ever.
It'll pave the way for adoption, progression and innovation. Keep in mind, three corporations decided to build their business on DGB already: @digiassetX, @Lifehash_ and @DigiCorpLabs. More to come for sure!
🧵6/7

Big thanks to everyone who supports this path of greatness.
Also big shoutout to @barrysty1e who has done a great job restructuring the Dandelion code. Exporting Dandelion to an external class was long overdue.

I have already reviewed his PR and we can merge it soon!! 👏

🧵7/7