Quote from: DGBfanster on October 18, 2018, 06:58:25 PM

Quote from: DigiByte on October 18, 2018, 04:42:49 PM

Quote from: DGBfanster on October 16, 2018, 02:38:10 PM

Quote from: DigiByte on October 15, 2018, 06:23:47 PM

Quote from: TheIrishman on October 14, 2018, 07:52:49 PM

Quote from: carlo_0000 on October 13, 2018, 06:55:08 PM

so we have still no news about the algos switch ?

why they keep so silent? are they gonna add 1 algo POS or not ?

it s gonna be 6 month and no news about that

Forget about that. The DGB devs and their friends have no intention of sharing the money they've been making with their ASICs, which they certainly got before most average DGB users.

This is complete and utter FUD. Please go cause problems elsewhere. A hard fork to a new algo takes a tremendous amount of work at this point. And as mentioned previously, the Algos we had planned on switching to in January of 2018 now have confirmed ASICs as well. So, in summary, switching from one ASIC algo to another is not wise or secure. However, research is being done into some very innovative ways to get around this problem. We very much watch DigiByte to stay as decentralized as possible.

Finally you came out of the woodwork.

Custom equihash algos don't have Asics at the moment, take a close look on those, as a developer you should've known about that. The amount of silence on the dev team along with the broken promise of changing algos only shows incompetence really.

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:

I used to contribute to Digibyte, WHEN I WAS ABLE TO MINE IT! Now I can't mine it because this is ASIC centralized crypto just like BTC, LTC, DASH and other crap like those.

I don't want to go to Telegram, I just want to see actual changes to the coin that are not new pools and new exchanges and new circlejerk

1 year has gone and nothing has improved on the code.

If you call this FUD, you sir are a big scammer. This is reality, not FUD.

YOU WANT....
YOU CAN'T...
YOU WOULD LIKE...
YOU DON'T....

Newsflash: the world doesn't turn around YOU......

Many answers and options are given... Take them, or leave.... But Stop making yourself look like an idiot please....