Quote from: benjamoyne on June 09, 2014, 09:26:07 PM

Quote from: tdcooper99 on June 09, 2014, 01:34:45 PM

Quote from: DigiByte on June 07, 2014, 06:50:30 PM

The mining pool list has been updated on the website. Let us know if we missed any pools or we have any that are not working: http://www.digibyte.co/

Folks... am I missing something? I still can't see where the hashrate is coming from? I just took 10 minutes and put a spreadsheet together using ONLY the officially listed pools on the above website (including P2Pool)... and first off... several still seem to be down, and a couple are at zero... but of the active ones, I can still only account for about 64MH out of the 474MH total, as of about 10 minutes before this post time.

Sorry if the formatting is all fukt... I'm sure there's an easier way to put a table in a post, but I couldn't work it out. So... does this mean that like 85% + of the DGB hashrate is with the multi-pools that are not listed here?

Pool Name    Pool Hashrate   Network Hashrate    % Network Hashrate
Blazing Hashes    7.9    474    1.67%
Coin Mine Pool    0    474    0.00%
Coinium Pool    0    474    0.00%
Crypto Pool Mining    0.9    474    0.19%
Dedicated Pool    0    474    0.00%
Leet Pools Mining    0    474    0.00%
Lucky Miners Pool    13.6    474    2.87%
Mining Pool Co    12    474    2.53%
More Coins Pool    25.7    474    5.42%
Palmetto Miners    0    474    0.00%
P2Pool     4.5    474    0.95%

While mining for the 24 hours yesterday, (its morning here in Australia now)
We seemed to have a low of 230-270, BUT that was with the 100 I was throwing at it.
So at the moment we seem to have a base line of 130-170

What I did notice was the blocks didn't slow after the Multipools had jumped off while I was mining.

Would have kept mining, but you lose 50% a day hiring scrypt rigs and that was with the block bonus at miningpool.co. Sad

It's got to be solo miners hoping to get lucky, because with less than 100 blocks found over the last 24 hours, a lot of luck is exactly what they'll need. Cheesy

http://explorer.cryptopoolmining.com/chain/DigiByte

BTW, if you look at the blockchain record, you'll see that there is no correlation at all between spikes in diff (multipool attacks) and when the blockchain freezes - the freezes happen just as often, if not more often, with low diff values than with high diff values. Recent 24 activity shows an hour and a half freeze after block 134028 with a diff of 61.964; one hour after 134093 with a diff of 39.951; over and hour and a half after 134116 with a diff of 44.569. That having been said, sometimes big 2 hour plus freezes do follow spikes (see blocks 134226 and 134101 for examples); however, you can also find blocks found at high diff values that just kept right on ripping (relatively speaking of course) with new blocks found right away afterwards (for examples, see blocks 134060 with a diff of 73.664 and 134029 with a diff of 82.619). As I said, no correlation what-so-ever.