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?
Topic: [ANN] FlutterCoin FLT Proof Of Transaction Cash Back for Sending & Recieving - page 292. (Read 368097 times)
March 15, 2014, 01:57:09 PM
March 15, 2014, 01:50:47 PM
Seems that everyone need to pull the plug at once ton restart this baby
Who makes the first step
Who makes the first step
March 15, 2014, 01: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.
In any event they need to just fix the issue and politely ask people with large hash rates to mine elsewhere.
March 15, 2014, 01: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.
March 15, 2014, 01: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?
March 15, 2014, 01: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.
March 15, 2014, 01:18:10 PM
bitember and cloudminers are on different forks, AND BOTH FORKS HAVE SAME ISSUE...
March 15, 2014, 01:17:22 PM
uhoh....here we go again... lol....
March 15, 2014, 01:17:05 PM
alright guys whats happening with the blocks?
March 15, 2014, 01:12:38 PM
Looking good.
F8agGwd6RUoPRuxfveRqHzJHnSsBMR6A2T
F8agGwd6RUoPRuxfveRqHzJHnSsBMR6A2T
March 15, 2014, 01:09:23 PM
I take that back about btember, I'm on a cell phone lol.
Verify using block explorer...
Verify using block explorer...
March 15, 2014, 01:08:16 PM
Same bug again?
700% already... 
March 15, 2014, 01:03:38 PM
March 15, 2014, 01:03:22 PM
Bitember forked again?
@dev: Which pools are on the right fork?
March 15, 2014, 01:02:42 PM
Thanks, that's the way to go, that other pool had 75 of all hashrate
March 15, 2014, 01:01:13 PM
Anyone know how to get P2Pool setup?
March 15, 2014, 01:00:21 PM
Bitember forked again?
Yeah - for sure. These pools never learn LOL. That is 75% of the hashrate easy 51% attack.I cannot stress how important it is to monitor hashrate if your a pool operator.
March 15, 2014, 12:57:23 PM
What's appening? Last block 10405 March 15, 2014, 16:04:34 ? more than one our ago
ok, now we are at block 10406, Time: March 15, 2014, 17:37:15. 93 minutes between block 10405 and 10406, too much. Difficulty too high?
Diff readjusts every block not sure if that's the problem but that long time between blocks happens a few times a day earlier ones were only like 20 mins not this long though.
The stuck block was showing diff of 14 though... not that crazy.
Thing is though that is the difficulty of that block, if say 500mH dropped off after the last mined block, that could happen
March 15, 2014, 12:55:18 PM
Bitember forked again?
March 15, 2014, 12:54:37 PM
Jump to: