kache
Full Member
Offline
Activity: 140
Merit: 100
Bored
|
|
March 15, 2014, 06:18:10 PM |
|
bitember and cloudminers are on different forks, AND BOTH FORKS HAVE SAME ISSUE...
|
|
|
|
Makitaki
Member
Offline
Activity: 103
Merit: 10
|
|
March 15, 2014, 06:24:56 PM |
|
bitember and cloudminers are on different forks, AND BOTH FORKS HAVE SAME ISSUE... They show the same current block 10435. The Bitember's dashboard doesn't auto refresh, hit F5 from time to time.
|
|
|
|
logi
Newbie
Offline
Activity: 31
Merit: 0
|
|
March 15, 2014, 06:32:13 PM |
|
bitember and cloudminers are on different forks, AND BOTH FORKS HAVE SAME ISSUE... They show the same current block 10435. The Bitember's dashboard doesn't auto refresh, hit F5 from time to time. Might be the same block number, but bitember reports network hashrate and pool hashrate as identical, so they are on a separate fork. Any clue if cloudminers is on the proper one?
|
|
|
|
thekidcoin (OP)
Sr. Member
Offline
Activity: 308
Merit: 250
FlutterCoin Developer
|
|
March 15, 2014, 06:43:21 PM |
|
bitember and cloudminers are on different forks, AND BOTH FORKS HAVE SAME ISSUE... They show the same current block 10435. The Bitember's dashboard doesn't auto refresh, hit F5 from time to time. Might be the same block number, but bitember reports network hashrate and pool hashrate as identical, so they are on a separate fork. Any clue if cloudminers is on the proper one? This doesn't necessarily mean a fork, I've seen similar things happen on other pools and it was due to crons fuckup or some such, wasn't actually a fork. That being said, this coin had a ton of forks before it was posted here, so I wouldn't be surprised if it started happening again. The only forks that occurred were because of lopsided hashrate. These things don't just happen without reason. These delays are likely hashrate/difficulty related. They could be forked also. The fork is purely hashrate related. You can't run a pool with 75% of the hashrate. Not only does it cause forks, but if it goes down the block chain stalls as the difficulty target for the next block it way too high.
|
1MYL967PR52xiNtqSP9WphRvPzKZDjBdxn
|
|
|
thekidcoin (OP)
Sr. Member
Offline
Activity: 308
Merit: 250
FlutterCoin Developer
|
|
March 15, 2014, 06:46:33 PM |
|
They could be stuck because of the check pointing - all forks will die eventually they would error out with invalid checkpoint.
In any event they need to just fix the issue and politely ask people with large hash rates to mine elsewhere.
|
1MYL967PR52xiNtqSP9WphRvPzKZDjBdxn
|
|
|
ozie
|
|
March 15, 2014, 06:50:47 PM |
|
Seems that everyone need to pull the plug at once ton restart this baby Who makes the first step
|
|
|
|
organizer
|
|
March 15, 2014, 06:57:09 PM |
|
Well, there seems to be an issue if you ask me, i don't recall seeing something like this happening before.... except on a very high diff coin like AUR or something recently... could the diff being displayed way inaccurately?
|
|
|
|
Piotrsama
|
|
March 15, 2014, 06:58:09 PM |
|
In any event they need to just fix the issue and politely ask people with large hash rates to mine elsewhere.
Or increase minimum donation/fee, it usually does the trick
|
|
|
|
Mightymoo
|
|
March 15, 2014, 07:03:05 PM |
|
Working again
|
|
|
|
organizer
|
|
March 15, 2014, 07:07:56 PM |
|
Working again
Under diff 13, seems to work fine... 2x now @ 13, it hangs... let's see if it happens again!
|
|
|
|
Piotrsama
|
|
March 15, 2014, 07:08:11 PM |
|
The MH/s only gets recalculated after each block? Is that normal for every coin? When it was stuck: 15:59:04  { "blocks" : 10435, "currentblocksize" : 37199, "currentblocktx" : 51, "difficulty" : { "proof-of-work" : 13.00103144, "proof-of-stake" : 0.00024414, "search-interval" : 1 }, "blockvalue" : 4108000000, "netmhashps" : 564.03035187, "netstakeweight" : -1.#IND0000, "errors" : "", "pooledtx" : 51, "stakeweight" : { "minimum" : 0, "maximum" : 0, "combined" : 0 }, "stakeinterest" : 1000000, "testnet" : false }
Just after: 16:03:56  { "blocks" : 10439, "currentblocksize" : 1758, "currentblocktx" : 2, "difficulty" : { "proof-of-work" : 8.62573516, "proof-of-stake" : 0.00024414, "search-interval" : 1 }, "blockvalue" : 8353000000, "netmhashps" : 189.98589953, "netstakeweight" : -1.#IND0000, "errors" : "", "pooledtx" : 2, "stakeweight" : { "minimum" : 0, "maximum" : 0, "combined" : 0 }, "stakeinterest" : 1000000, "testnet" : false }
|
|
|
|
|
homeiss
Member
Offline
Activity: 118
Merit: 10
|
|
March 15, 2014, 08:15:39 PM |
|
Anyone know how to get P2Pool setup?
+1 We need this!
|
Pass the Flutter: F7PjYAf7stemsejKHWarkjC1sb5FqbsnhZ
|
|
|
seattletu
|
|
March 15, 2014, 08:20:57 PM |
|
so are there any pools that are fucked up right now, or are all the pools on the same chain?
|
|
|
|
Mightymoo
|
|
March 15, 2014, 08:23:36 PM |
|
so are there any pools that are fucked up right now, or are all the pools on the same chain?
All on same chain
|
|
|
|
cloudminers
|
|
March 15, 2014, 08:28:19 PM |
|
According to the Block Crawler the current nethash is 2068.26355306 mH/s. This should mean that all the current pool's are in the clear.
Is just checked the pool's and they are +/- 600mH/s
|
|
|
|
Mightymoo
|
|
March 15, 2014, 08:30:39 PM |
|
According to the Block Crawler the current nethash is 2068.26355306 mH/s. This should mean that all the current pool's are in the clear.
Is just checked the pool's and they are +/- 600mH/s
bitembers at 890 mhs
|
|
|
|
thekidcoin (OP)
Sr. Member
Offline
Activity: 308
Merit: 250
FlutterCoin Developer
|
|
March 15, 2014, 08:30:57 PM |
|
Who said earlier another coin had stalled blocks today? 365 coin or something?
I am investigating something, definitely a major issue (not with FLT), not sure though if it could effect our network itself though.
|
1MYL967PR52xiNtqSP9WphRvPzKZDjBdxn
|
|
|
tic-tac-totoro
|
|
March 15, 2014, 08:32:10 PM |
|
Who said earlier another coin had stalled blocks today? 365 coin or something?
I am investigating something, definitely a major issue (not with FLT), not sure though if it could effect our network itself though.
I believe it was darkcoin
|
|
|
|
thekidcoin (OP)
Sr. Member
Offline
Activity: 308
Merit: 250
FlutterCoin Developer
|
|
March 15, 2014, 08:32:41 PM |
|
According to the Block Crawler the current nethash is 2068.26355306 mH/s. This should mean that all the current pool's are in the clear.
Is just checked the pool's and they are +/- 600mH/s
bitembers at 890 mhs I'm in car, can't see the pools,did any pool actually fork???
|
1MYL967PR52xiNtqSP9WphRvPzKZDjBdxn
|
|
|
|