Pages:
Author

Topic: ★★DigiByte|极特币★★[DGB]✔ Core v6.16.5.1 - DigiShield, DigiSpeed, Segwit - page 27. (Read 3058935 times)

full member
Activity: 274
Merit: 101
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.

Solo mining is very much still possible with DGB, the way its setup has changed.


That´s very exiting to here.
Could you please Update the FAQ on Digibyte.io, Github and so on, there is still a World outside of telegram.


If anyones still struggling with solo mining Digibyte,
BSOD pool offer solo mining ports for Digibyte.

I've used them a bit for Scrypt and it works fine.

https://bsod.pw
newbie
Activity: 2
Merit: 0
I accidentally sent DGB to DOGE address.
Is there any way to recover the funds back?
member
Activity: 87
Merit: 10
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.

Solo mining is very much still possible with DGB, the way its setup has changed.


That´s very exiting to here.
Could you please Update the FAQ on Digibyte.io, Github and so on, there is still a World outside of telegram.
member
Activity: 122
Merit: 10

Wow, 43 posts, been around a while huh? BTC , LTC and DASH are "crap"? You have a lot to learn. Learn it on Telegram.


Your right, at this very moment they're at least better than DGB since they're more valuable. The one that is crap is DGB.
sr. member
Activity: 1078
Merit: 310
AKA RJF - Member since '13
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.

Wow, 43 posts, been around a while huh? BTC , LTC and DASH are "crap"? You have a lot to learn. Learn it on Telegram.
member
Activity: 122
Merit: 10
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.


There's a problem with your line of thought. DGB is not the single best solution for fast transactions anymore, it WAS.

The longer the dev team wait to implement changes, the worse it will be.

This coin had a great exposure and adoption back when it was trully decentralized. All the dev team had to do was to keep it that way. Sadly what really happened is that they got lazy (to say the least).

I don't even think a hardfork for new algos will save this coin anymore. You'll need to do that and something much bigger if you want to take one of the top 10 cryptocurrencies now.
hero member
Activity: 924
Merit: 526
GIF by SOCIFI
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.
member
Activity: 122
Merit: 10
YOU WANT....
YOU CAN'T...
YOU WOULD LIKE...
YOU DON'T....

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

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

Take your shill to your coffin.

He accused me of not helping DGB. I mined this coin for almost two years, back when very few people gave a shit about mining.

If there's an idiot here, it's you because you're the one giving the devs of this coin a pat on the back while they fool everyone lying about the nature of this coin.

member
Activity: 434
Merit: 30
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...... Smiley

Many answers and options are given... Take them, or leave.... But Stop making yourself look like an idiot please....
legendary
Activity: 1308
Merit: 1011
member
Activity: 122
Merit: 10
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.
legendary
Activity: 1722
Merit: 1051
Official DigiByte Account
The bigger issue with Bakkt is mass adoption and general interest in crypto, even is DigiByte doesn’t get listed it will bring many people into the crypto space via mainstream the whole market will feel it.
We have numerous community members in touch with every major platform out there. Please join the telegram discussions to see real-time discussions on much of what is being asked about on this thread: https://www.digibyte.io/digibyte-community
legendary
Activity: 1722
Merit: 1051
Official DigiByte Account
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!
sr. member
Activity: 616
Merit: 250
The bigger issue with Bakkt is mass adoption and general interest in crypto, even is DigiByte doesn’t get listed it will bring many people into the crypto space via mainstream the whole market will feel it.
sr. member
Activity: 1022
Merit: 391
Nobody cares about new pools and new exchanges.

What DGB needs is active development, improve decentralization like this was supposed to do at the beginning.

This project is mislead (or not) as a pump and dump scheme because development and devs are absent.


The theory that says devs are mining with ASICs is plausible and the only way for developers to prove they are honest is to implement algorithm changes ASAP.

If nothing is done soon, this coin will pump eventually, but it's gonna be the final exit pump and then it's gonna die.

I can understand that you are demoralized because maybe you have taken DGB to high levels but to say that the team does not develop you are just off the road; say also that it is a pump & dump currency means that you do not understand anything about the crypto market .... you know why:
because all the coins, from bitcoin to Ethereum, are pump & dump coins and you just look at a chart to figure it out: Bitcoin is losing 70% while ethereum and the others are around 90%.   Grin

In reality, what you call pump & dump are patterns that follow indices, stocks, commodities, crypto .... it's up to you to understand it, study it and put it into practice.

Here an article of the beauty and the unique characteristics of Digibyte!

https://cryptoglobalist.com/2018/10/18/digibyte-dgb-is-proof-enough-that-hype-is-still-the-main-driver-of-the-crypto-market-in-2018/?amp
legendary
Activity: 1722
Merit: 1051
Official DigiByte Account
Shocked

i must agree, coin is maybe fast but dev team is to slow, and not communicative

it s gonna be or already is an half year with the algo problem,  and only thing we know now it s that something gonna happen in January  Roll Eyes

and it s not just that, what about marketing ?
other coins they doing stuff  and talking about mass adoption ,  but if dgb thinks it s going to the top by it s own, even if it s the best coin in the world no body will care, the cheeps they following the media and so on

just like the usdT  thing   who can  people be so stupid, they here in crypto because they hear about decentralization, they don't like the banks...
but they use the usdt lol  Huh Grin

The majority of the community is on Telegram, over 16,000 people in the official chat. For the most part, Bitcointalk is no longer a very active or good place to have in-depth discussions on future developments. Please check here: https://www.digibyte.io/digibyte-community
member
Activity: 420
Merit: 13
Nobody cares about new pools and new exchanges.

Actually larger DGB holders/investors like me care about exchanges. IF you don't care about it, so it be, but don't put everybody in it.

What DGB needs is active development, improve decentralization like this was supposed to do at the beginning.

Me personally is more than happy with the developements, price chart and decentralization of DGB in 2018, it's at least ok. If you are looking for a truely decentralized coin just go with one that is allready present, Monero may fit your needs best, simple as that.

This project is mislead (or not) as a pump and dump scheme because development and devs are absent.

If that's your thought about DGB, why are you still here? Maybe you should check some other DGB channels to be more updated. I'am fine having Devs working on development instead of dealing and wasting time on bitcointalk with childish comments and posts like the one i'am replying to. Makes me wonder why i even waste that time, lol. Mostly because i'am with the breakfast coffee in good mood or such childish posts don't even deserve any attention, what's left for a dev wasting its time....

The theory that says devs are mining with ASICs is plausible and the only way for developers to prove they are honest is to implement algorithm changes ASAP.

Theory? Any proof for that? Why should someone change these perfectly working algos anyway, just because you or some people (mostly small miners) prefer it?
Makes no sense. From a holder point of view the only thing that matters that as much as possible tied hardware is attached to a given coin, in this case DGB.
Devs would act idioticly to risk whatever algo change without real security need while doing pretty good in this bearish market.

If nothing is done soon, this coin will pump eventually, but it's gonna be the final exit pump and then it's gonna die.

Uhmmm, if you anyway think this coin is an exit pump an algo change or whatever interest in DGB doesn't make sense from your point of view.
Why would i care about whatever if i'am publicly believe it's a scam coin? Doesn't make sense.
After you believe it's a scam (it's definatly not!), just sell your DGB and go buy some Monero or whatever coin that fits all your preferences, easy and simple as that.


full member
Activity: 274
Merit: 101
Nobody cares about new pools and new exchanges.

What DGB needs is active development, improve decentralization like this was supposed to do at the beginning.

This project is mislead (or not) as a pump and dump scheme because development and devs are absent.


The theory that says devs are mining with ASICs is plausible and the only way for developers to prove they are honest is to implement algorithm changes ASAP.

If nothing is done soon, this coin will pump eventually, but it's gonna be the final exit pump and then it's gonna die.



Most of the community are on Telegram, with updates posted regularly on medium and youtube.

The development this year has been nothing short of amazing.

Perhaps you should venture outside the walls of bitcointalk a little bit more.
member
Activity: 122
Merit: 10
Nobody cares about new pools and new exchanges.

What DGB needs is active development, improve decentralization like this was supposed to do at the beginning.

This project is mislead (or not) as a pump and dump scheme because development and devs are absent.


The theory that says devs are mining with ASICs is plausible and the only way for developers to prove they are honest is to implement algorithm changes ASAP.

If nothing is done soon, this coin will pump eventually, but it's gonna be the final exit pump and then it's gonna die.
member
Activity: 199
Merit: 11
Digibyte p2pool nodes:

for USA - http://p2p-usa.xyz:5027/static/ - SHA256D
            - http://p2p-usa.xyz:5023/static/ - QUBIT
            - http://p2p-usa.xyz:5025/static/ - SCRYPT
            - http://p2p-usa.xyz:5021/static/ - GROESTL
            - http://p2p-usa.xyz:5029/static/ - SKEIN

for EU   - http://p2p-south.xyz:5027/static/ - SHA256D
            - http://p2p-south.xyz:5023/static/ - QUBIT
            - http://p2p-south.xyz:5025/static/ - SCRYPT
            - http://p2p-south.xyz:5021/static/ - GROESTL
            - http://p2p-south.xyz:5029/static/ - SKEIN

            - http://p2p-spb.xyz:5027/static/ - SHA256D
            - http://p2p-spb.xyz:5023/static/ - QUBIT
            - http://p2p-spb.xyz:5025/static/ - SCRYPT
            - http://p2p-spb.xyz:5021/static/ - GROESTL
            - http://p2p-spb.xyz:5029/static/ - SKEIN
Pages:
Jump to: