Get Mystery Box with random crypto!

1/ Here is a video update on #DigiByte v8.22.0 as well an over | Jared Tate

1/ Here is a video update on #DigiByte v8.22.0 as well an overview of the added complexities of core #blockchain protocol development. Short summary, we are working on it, this is most comprehensive upgrade ever for $DGB & we have ran into unforeseen bugs.



2/ When #Bitcoin first started it had 3,000 lines of code in 4 files. Currently $BTC core code has over 620,000 lines of code & DigiByte has over 700,000. In comparison the core Linux Kernel has only 63,000 lines of code. There is a massive amount of changes to review in 8.22.

3/ So far the DGB 8.22.0 upgrade has added +281,194 lines of code & removed −92,818 lines of code removed. This massive update to roughly half the DGB code base has led to some elusive bugs we are working through which has taken more time than expected.

4/ The main issue we have now is with Dandelion. There was a ton of mempool rework done between BTC v0.17 (our 7.17.3 base) & latest BTC v22. Effectively a completely rewrite of dandelion is needed to be compatible with DGB v 8.22.0 & BTC v22. This has caused some very...

5/ hard to track down random crash bugs that are a serious problem for sending & receiving stem pool dandelion transactions in 8.22. This complexity is the same reason BTC devs abandoned adding dandelion to v22 & v0.21. Here is the current crash bug:

6/ The next big changes are a completed set of tests which we have never fully had in a DGB core client.
@YoshiJaeger
has been doing a great job rounding these out, but these are very time consuming. This is an extremely under appreciated part of releasing a stable DGB client.

7/ All in all in it is important to remember all devs are volunteers & all of us are working on other stuff to pay the bills & most of our day gigs are actual use cases built on top of DGB that will further benefit DigiByte in the long run. Many good things on the horizon.

8/ I know there is some frustration where some say nothing is happening but that's simply not true. DGB is in a stronger development position than it ever has been before. Despite what some say, I do not control the development of DGB, any code changes require multiple reviews.

9/ I want to thank everyone for supporting DGB & to further reinforce I truly believe DigiByte's best days lay ahead. I encourage everyone to get involved and help however they see fit. Thank you all!