Quote from: MarcusDe on September 05, 2014, 08:36:57 AM

Quote from: vpn01 on September 05, 2014, 05:42:12 AM

Quote from: MarcusDe on September 04, 2014, 09:33:17 AM

2014-09-04 09:09:13 9dc7dc470c695386373e0f2d568cd504891187c60e09a2ba610944ad8945a13b 478620 9 10.71 DEHoTUEbm4ZixpLcuC85Q6i3J16VSRf9rL
2014-09-04 02:59:59 715ebf55665544f2ced3b5bc27e17fa2fd47549c5c0ea64774d21b203c973d36 476247 2 11.14 DEHoTUEbm4ZixpLcuC85Q6i3J16VSRf9rL

Okay.... 2300 blocks in 6 hours? WTF is going on with this network?
6,6 blocks / minute with network set (in theory) to make block every minute and diff changing every block?

maybe one man or somebody solo ??

For me its more like...
Pool is connected to 20 or more nodes which aren't even at top of blockchain, dont know REAL last block, we mine something, then some other part of network (with big miners) connects to it / after restart pool connects to other nodes, pool thinks that whole work is bad, so shows orphans. LOL. Its logical that this started after gpool shutdown, where 2000+ miners were disconnected.

Gpool shutdown ,but the pool status show that it has 1840 miner keep on mine at gpool,so hard to say what is going on. but i remember 3hours ago the miner status is -1.