The initial post someone made was taking data from a pool not the block chain. We are booting up a laptop to look at the blockchain.
The first time I mentioned it was here (check out the time stamp) - with no response.
I'm curious. With DBG stuck on block 131993 for over an hour and a half now, I started looking at the block chain and I noticed that it's been taking progressively longer to find blocks, with only an average of 10.66 blocks found per hour over the last 24 hours.
Only an average of 19.25 blocks found per hour over the last 5 days?
I've quickly searched a bit, but I haven't found anything on this. Forgive me if I've missed it.
Add: 131994 was just found - just under 2 hours between blocks!
The second time was here - again, no response.
Reasonable expectations are an extremely important part of, if not perhaps even the most important aspect of, any endeavor, but equally so is the window of opportunity for its implementation.
Fear of making a mistake can paralyze projects, leading to over cautiousness and missed opportunities, while unconscious brazenness can lead to almost certain short term disaster. It's a balancing act that normally plays out over a considerable amount of time, and even then it's tough to get right. Accelerate things by a factor of 10, and we might begin to just begin to get an idea as to how much more difficult that balancing act will be within the present context.
I think I understand both sides of this highly charged issue. An algo change is not an overnight venture (unless it is stop-gap, cut and paste, and, as we know, that Digibyte is not), but the urgency felt by many is also well worth noting – the rate at which cryptocurrencies are evolving is increasing exponentially and I too share the worry that it will come too late. There's nothing like a great idea ahead of its time that gets beaten out by someone else who is quicker to bring it to market. Nothing like a good product that's too late! I mentioned earlier how an average of only 10.66 blocks were being found per hour over the last 24 hours, and 19.25 per hour over the last 5 days, and I'm not exactly sure what that is due to, but if it has anything to do with a dwindling of the widely distributed user base and an increase in ASIC mining, that would not be a good sign for time being on DGB's side (either way, there's obviously something wrong with that output for a 60 second coin, and very disconcerting considering that mining is the foundation that everything else rests on at this time . . . perhaps it's another completely unrelated issue to further complicate things . . .).
In any event, along with 'getting it right', I think we can probably also all agree that time is of the essence and there's no time to waste! We've got a supersonic balancing act on our hands and all eyes are on the Dev team. If English bookmakers were to place bets on this, I'd bet that the bet would be: “can they do it in time?” (Just to add a bit of "big game" pressure to the mix while we're at it.
)I want to wish the Dev team the best of luck with this very stressful 24/7 project you have on your hands, and to also thank you for keeping us up-to-date and in-the-loop. Rest assured that you can count on my/our help with testing and whatever else I/we might be able to do. Here's to getting a great job done in time!
The third was last night - quoted here within your response, and as you an see, there was no mention of anything other that DBG blockchain data in any of my posts.
As of 2014-06-02 21:03:42
Last 24 hours: only 410 blocks found of a supposed 1440 theoretical programed 60 second blocks.
Previous 24 hours: only 280 blocks found
Previous 24 hours: only 166 blocks found
What would be the explanation for this?
In order to be competitive with ASIS resistant coins (and the few still competitive scrypt coins), on a relative profitability basis, actually mining the coin, DGB would have to be valued at around 120 satoshi, and that, of course, is based on a 60 second block find basic assumption. With blocks being found at only around 1/4 of the rate of what should be the case . . . well, I'll let you all do the math. Blockchain Explorer: http://explorer.cryptopoolmining.com/chain/DigiByte
Something is very wrong with this picture.
The whole community (and beyond) is holding it's breath. 
