Topic: [ANN] FlutterCoin FLT Proof Of Transaction Cash Back for Sending & Recieving - page 280. (Read 368097 times)

What everyone is failing to realize also is the blockchain is solving more than the expected # of blocks

block 10000 Block Time: March 15, 2014, 4:38 am
block 10811 Block Time: March 16, 2014, 4:31 am
expected blocks per 24 hours = 720
actual blocks=811

block 9871 Block Time: March 15, 2014, 12:29 am
block 11302 ("stuck" block were at) Block Time: March 17, 2014, 12:28 am
expected blocks per 24 hours = 720
actual blocks=1431

The blockchain is working.  Looking at these stuck blocks, difficulty is fine.

These are the possible issues:

- pool issue - pool with most of the hashrate stops mining correctly, possibly someone is exploiting the stratum exploit, they are setting them to a higher difficulty, and the block doesn't get solved, the other pools are having bad luck, and can't find the block (these smaller pools don't find blocks as often)

- The block interval is being calculated incorrectly.  In PPC it is said a POW block can be spaced between 10 minutes and 2 hours (would equate to 2 minutes and 24 minutes here) - but i can't see how this could ever be true even in PPC looking at the code where it does a min to determine the interval.  I am seeing no issue.

- Some party is pointing enormous hashrate and then dropping off on purpose to in effect stall the blockchain - this is doubtful though

- A major pool is having issues where it looks like they are mining, yet  their work is invalid for some reason - I really need pools to check their logs for rejected blocks - search for CheckBlock or ConnectBlock or if you see rejected shares.

Whats strange is that when block 11303 is found the hashrate will be far lower (understandable some people dropped off - but no way its 3/4 of the network) - then suddenly a little while later difficulty will rise.   There's no way this 3/4 of the network that supposedly dropped off just starts mining again within 15 minutes.  

This will drive me insane LOL

damn. our butterfly blocks are getting stuck in a crypto-spiderweb

just curious, has anyone seen a best share on their miner that would have solved the block?

No I legit didn't know, I thought each pool worked on a block, so when the block was finally solved, I thought it was odd that everybody solved at around the same time. Now I get it, but yet more confused than ever.

it's not your wallet. everyone is stuck there

Wow I guess I didn't understand how it worked. I thought each pool had a block that they worked on separately from other pools.

wallet stuck on block 11302. tried restarting it, but no go. any suggestions? 

Everything you've said is true, but that's not the problem occurring here. Difficulty isn't skyrocketing - that's not why these blocks are getting stuck.

Dude... seriously? The guy didn't say that the pools solve the same block, he was saying that all of the pools solve a block within a short time of one of the pools solving the stuck block. Probably not a good idea to be rude to your own community.

And anyway, why exactly do you think the problem is to do with difficulty? Difficulty is 32 right now and the block's stuck again. There's a 2GH/s net hashrate... no way is 90% of the network hopping off during a single block. Do you even know how mining works LOL?

Let me see if I can explain this for you.
All of the pools are racing to find the same block. when a block is found everyone discards their work and starts trying to solve the next block. when a multi-pool or someone with a farm hops on and mines through a few blocks super fast the diff. skyrockets and the multi-pool moves on to something easier. leaving the small guys to hash through the high diff. blocks untill the diff. drops back down far enough to meet the target time.
I have seen multi-pools completely kill coins where the difficulty retarget was 100 blocks and nobody hung around to hash through the weeks needed to bring the diff. back down.

I'm not a programer and don't totally understand how KGW works but have yet to mine a coin where it worked smoothly. Lotto coin has been around before KGW (I'm pretty sure) and they figured out how to adjust difficulty every block to maintain their block target time and I have seen the diff. jump from 3 to 20 in amater of a few blocks and then back down to 2 or 3 in one block after a hard block when a multi-pool jumps in and out.

hope this helps explain things a little better. (anyone feel free to correct me if I am wrong on any of these points)

Do you guys even know how mining works LOL??? (no offense) - all of the pools DO NOT solve the block at the same time - 1 pool or solo miner finds the block.

You keep saying the diff is too high... why? As was posted earlier, the difference between a "stuck" block and the previous block was .8 or something like that... other coins (like AUR) for example, I can understand a giant jump from 200-500 causing a long block time, but these changes are incremental, not severe.....

Hmm, that's weird. Nothing to do with difficulty then. You'd have to have at least a 90% dropoff in net hashrate to keep regularly getting blocks stuck for over 50 times the target. And with a net hashrate of about 2GH/s, there's no way that's been happening.

Could it be a stratum issue if all the pools are suddenly solving their blocks at the same time?

that's what we are trying to figure out. what's weird, is you will see ALL OF THE POOLS solve their block at right about the same time.

Is the problem with the difficulty though? Difficulty's only at 32 right now, but this block's been stuck for 90 minutes...

but why does each pool seem to solve a high difficulty block at the same time, when they have all been working on a block for hours? it really seems like once a block is found, it auto lowers the difficulty even for other pools who are still working on a block. thus enabling those pools to find a block too.

is that how it works? or if a pool is working on a block, the difficulty stays the same for that block/pool until that block is found?

but couldn't that easily be attributed to a sharp decrease in difficulty because of frustrated miners leaving to other coins? it has to have some impact, right?

when i said a "pool is stuck" i should have actually said "when a pool is hashing for a long time looking for a block because of high difficulty adjustment"

100% true - and likely though there ARE the right # of blocks found over say 4 hours...  even with the stall.

Its not the fool thats stuck - its that the difficulty is too high... This is like PPC or NVC, its not a straightforward 2 minute block time.

One thing to do is see how many blocks are found in say 2 - 3 hours that include a stalled block.  You will strangely see close to the right number of blocks actually found.

The blocks get solved really fast, some 2 a minute, etc.  There is more to the block time with PPC like coins.  I have been involved in a few coins, but they never saw this hashrate.

I am going some things to monitor the blocks etc on my end but no fix is in sight thats a slam dunk (don't want to rush and put something bad out you know?)