The key word you mentioned above is correct: "don't have Asics at the MOMENT,". A hard fork to a temporarily GPU algo, will not remain GPU for very long is not a long-term solution. Nor is it worth the security risks of a hard fork to the entire network. Work is being done on potential algo solutions that will permanently mitigate the ASIC problem. There are some promising ideas and leads. However, DGB does not have millions to poor into full time "algo" research. Something typical done by top research universities over the course of many years with government grants.

Once again, for those who have questions and ideas, the majority of active discussion occurs on Telegram and is publicly released on social media. Very few people actually check this thread anymore. The fact we are still here replying on this thread almost 5 years after DGB launched is a testament to active, continuous, committed development and communication with the public.

Please stop fudding and help contribute to the project. If people spent half as much energy trying to help improve things as they did attacking, spreading false information and armchair quarterbacking we would all be much further along.  Anyone can begin contributing to DigiByte. Please check here: https://www.digibyte.io/digibyte-community

To the individual accusing the "Devs" of hoarding ASIC miners and not changing the algo, this is completely and blatantly false. Solo mining is very much still possible with DGB, the way its setup has changed. The latest changes in DGB reflect the advancements put into bitcoin core from researchers in 2017 -2018.

To those accusing DGB of no active developments or improvements, please stop trolling and spreading false information. Or you really are living under a rock and need to look outside of bitcointalk. Over 120,000 lines of code have changed in DGB in 2018. We have released several versions of DGB with multiple significant improvements this year including: