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:

Most recent DigiByte core v6.15.1 - Sept 21st, 2018
https://github.com/digibyte/digibyte/releases/tag/v6.16.5.1

Quote

Please upgrade immediately!

Updates correct Wallet Image to 6.16.5
Fix crash bug with duplicate inputs within a transaction
Fixes Private key import bug from old DGB wallets
Fixed new client sync bug

DigiByte Core v6.16.4 - August 26th, 2018
https://github.com/digibyte/digibyte/releases/tag/v6.16.4

Quote

Fixes rpc mining info response bug in 6.16.3
Fixes import issue with old private keys from 2014 era wallets.
Pulls latest BTC 0.16.2 fixes into DGB.
Tweaks RPC command getblockchaininfo to display all five algos difficulty.
Enables option to generate bech32 prefix segwit addresses "dgb1 address prefix" that was rolled out earlier this year in 6.16.2 but not activated.
Upgrades DigiShield/ MultiShield with optimizations and performance tweaks to further improve security.
Fixes weighing issue with sha256
It's not a hardfork.
Many other small enhancements & optimizations

DigiByte Core v6.16.3 Beta - August 10th 2018
https://github.com/digibyte/digibyte/releases/tag/v6.16.3

Quote

Fixes import issue with old private keys from 2014 era wallets.
Pulls latest BTC 0.16.2 fixes into DGB.
Tweaks RPC command getblockchaininfo to display all five algos difficulty.
Enables option to generate bech32 prefix segwit addresses "dgb1 address prefix" that was rolled out earlier this year in 6.16.2 but not activated.
Upgrades DigiShield/ MultiShield with optimizations and performance tweaks to further improve security.
It's not a hardfork.
Many other small enhancements & optimizations.

DigiByte Core v6.16.2 - March 26th, 2018
https://github.com/digibyte/digibyte/releases/tag/v6.16.2

Quote

Over 100,000 lines of code changed in this release.

Initial Sync Performance Increase (Relay 10,000 headers now vs 2,000)

Add Additional Dedicated Seed Nodes

Fix Peer Connectivity Issues

Add Three DigiByte GUI Themes (White, Black, Blue... can be set in wallet preferences)

Change DGB p2sh Address Prefixes from "3" to "S". This prevents confusion with Bitcoin p2sh addresses.

Add Support for future bech32 DigiByte Addresses (Future DGB addresses will start with "dgb1" all lowercase)

This is disabled by default and wallet will generate "D" addresses until more compatibility arrives in mobile and exchange wallets. For now add "addresstype=bech32" or "addresstype=p2sh-segwit" in your digibyte.conf to test these changes and generate these address types. WARNING: all other wallets do not yet support this address type.
Merge Improvements from Bitcoin Core 0.16.0

Merge Improvements from Bitcoin Core 0.15.0

There are several developers actively working on multiple other DGB projects please see here: https://github.com/DigiByte-Core

Thank you to everyone here who is actively supporting DigiByte! And we warmly welcome anyone new reading this to come join the DGB community! We have an awesome community!

Excellent rebuttal. It's a shame that it is needed against the FUD.

Good to hear that other potential algo solutions are being researched to permanently mitigate the ASIC problem. People have to realize that DGB does not have unlimited budgets and it takes time to research and implement these changes but if ASIC's can get kicked out of the game for good, it's worth to wait for it.