everything can be fixed
Especially when the starting point is cut and paste, misleading, diversionary replies like this:
We have definitely been hit very, very hard by multi-pools. You can't expect that not to happen when the price doubles over night. We are checking into more things as well. The network is still there and working but blocks are a bit sluggish. Once again we are doing everything we can to make DigiByte the best it can be!
To extremely specific and concise technical issues like this:
Another post based on hard data. The issue began after Feb. 22. and has PROGRESSIVELY gotten worse.
Since you haven't had time to read all these posts, I thought I'd repost this since it is quite important.
And you might want to go back and read the last few pages.
This is whole network data.
current block: 132,795
DGB released days 142 * 1440(24*60) = 204480
I haven't checked the data myself but you have to factor in the multipools attacks from a while ago. They caused a lot of blocks to be mined very slowly and would've totally thrown the total coins minted out of balance. Also, remember that the minting of coins isn't actually balanced by the system, only the difficulty factor.
You need to check the data yourself. If you look at the blockchain, you'll see that the issue began with the implementation of DigiShield, and has nothing to do with the multipool attacks. Block discovery was perfectly in line with DGB coding until Feb. 22, 2014. Take a look at the blockchain up to that date and divide by the number of days that DGB had been in existence. http://explorer.cryptopoolmining.com/chain/DigiByte
The issue began back then and has progressively gotten worse.
I repeat: The issue began after Feb. 22. and has PROGRESSIVELY gotten worse.
- How would the issue progressively get worse if the number of multipools in existence is same as back then but with less than 50% the hashrate they had back then?
- Why wouldn't you look at a DigiShield-ASIC incompatibility thesis since the only thing that has also grown progressively since that date is the use of ASIC?
- To sum things up, why wouldn't you get serious with really troubleshooting the issue?
- And why were you not aware of the issue before now? (Why wasn't anyone aware of the issue?)
- Isn't this your coin that you intimately know? Don't you take responsibility for it?
Do I need to open a support ticket at Craptsy?
We've also been talking a bit about this on the "Whattomine - profitability website with basic api" thread (. . . if you're looking for troubleshooting and controlled testing ideas . . . my time is limited to being a contributor, not a Dev, and not even a full time hobbyist - anyone doing testing/troubleshooting, please post your hard data and initial assumptions).
https://bitcointalksearch.org/topic/m.7106535
It is quite entertaining. Do you have any solutions to offer for any of the problems facing Cryptocurrency right now? Are you ready to help improve things for everyone or are you in this for yourself?
If you are not happy with DigiByte or you have nothing to contribute in a positive manner or anything better to do with your time... Move on. Go attack another coin and spread fud there.
The question is which coin you are coming from... Or which exchange?... with your newbie account? It is flattering to be drawing this attention... Lol