Can someone possibly explain why I can no longer mine on Slush's pool, is this error related to the DDOS? Im using GUIMiner with these flags ( -v -w 256 -f 40 ) on my HD7970. I get the below then it just hangs, I can mine my backup fine but since earlier today I cannot mine slush.

Can someone possibly explain why I can no longer mine on Slush's pool, is this error related to the DDOS? Im using GUIMiner with these flags ( -v -w 256 -f 40 ) on my HD7970. I get the below then it just hangs, I can mine my backup fine but since earlier today I cannot mine slush.

Can someone possibly explain why I can no longer mine on Slush's pool, is this error related to the DDOS? Im using GUIMiner with these flags ( -v -w 256 -f 40 ) on my HD7970. I get the below then it just hangs, I can mine my backup fine but since earlier today I cannot mine slush.

Can someone possibly explain why I can no longer mine on Slush's pool, is this error related to the DDOS? Im using GUIMiner with these flags ( -v -w 256 -f 40 ) on my HD7970. I get the below then it just hangs, I can mine my backup fine but since earlier today I cannot mine slush.

in simplest terms.... if u want a more exacting reason just hold on I'm sure someone would love to say no I'm wrong its this.

when a block is found it needs to be communicated it was completed, when delays occur to do that another may complete it also, causing 1 of them to be invalid.1 or 2 a week seems the norm more than that means it should be looked at more closely.

in simplest terms.... if u want a more exacting reason just hold on I'm sure someone would love to say no I'm wrong its this.

when a block is found it needs to be communicated it was completed, when delays occur to do that another may complete it also, causing 1 of them to be invalid.1 or 2 a week seems the norm more than that means it should be looked at more closely.

Basically right on the money. I would just word it differently.

When a block is found, it has to be reported to the network. Even though that reporting is very quick it still takes time. And in rare instances, another pool/miner will think they found that same block in the time between the original pool/miner finding it and the network getting the report. When that happens, the second pool/miner to find it will get it marked as invalid.

Actually, if i got right how it works, the time when the block is found does not determine which one is invalid.It depends on which block will have the next one based on it.

Lets say one pool finds block 17a and one finds 17b. This has to happen in a small time frame, because if either pool had known about the 17 block, it would have stopped working on nr 17 and started working on 18. But it does not matter which one was found first. Both pools relay the found block, so we have some nodes who get notified about 17a first, and disregard messages about 17b cause they already know a valid 17 block, and some the other way round. Some nodes (pools) now work on 18 based on 17a, some work on 18 based on 17b.As soon as a node finds 18, others get notified and start working on 19. This chain contains either 17a or 17b, the one contained is valid, cause the chain with the other one will not get any longer, cause pools will not work on a 18 based on it, but on a 19 based on the longer chain.

That said, the statistics page on slush pool probably just counts down the block numbers for the number of confirmations needed.In theory, one could check whether the block is actually contained in the longest chain and display "invalid" way before the 100 has counted down.

Actually, if i got right how it works, the time when the block is found does not determine which one is invalid.It depends on which block will have the next one based on it.

Lets say one pool finds block 17a and one finds 17b. This has to happen in a small time frame, because if either pool had known about the 17 block, it would have stopped working on nr 17 and started working on 18. But it does not matter which one was found first. Both pools relay the found block, so we have some nodes who get notified about 17a first, and disregard messages about 17b cause they already know a valid 17 block, and some the other way round. Some nodes (pools) now work on 18 based on 17a, some work on 18 based on 17b.As soon as a node finds 18, others get notified and start working on 19. This chain contains either 17a or 17b, the one contained is valid, cause the chain with the other one will not get any longer, cause pools will not work on a 18 based on it, but on a 19 based on the longer chain.

That said, the statistics page on slush pool probably just counts down the block numbers for the number of confirmations needed.In theory, one could check whether the block is actually contained in the longest chain and display "invalid" way before the 100 has counted down.

I've never heard it described that way before. And if that's true, then the chain forks after every block found....

Why should the chain fork after every block?If a block is found, nodes get notified about it, stop working on the block they were working on and start working on the next one. With enough time between new blocks found, a fork would never occur.A fork does only occur, if any node finds a block and another nodes finds the same before getting to know about the first.

Though the first block is not necessarily the one who wins, probability is on its side, of course, because if its found earlier, more nodes might hear about that one first, and thus more pools will be working to expand the chain based on the early block instead of the later one. But if a node with fast connection to the one who found th later block heard about it first, and gets a (lucky) quick hit with the next one, the early block will be invalid.

Why should the chain fork after every block?If a block is found, nodes get notified about it, stop working on the block they were working on and start working on the next one. With enough time between new blocks found, a fork would never occur.A fork does only occur, if any node finds a block and another nodes finds the same before getting to know about the first.

Though the first block is not necessarily the one who wins, probability is on its side, of course, because if its found earlier, more nodes might hear about that one first, and thus more pools will be working to expand the chain based on the early block instead of the later one. But if a node with fast connection to the one who found th later block heard about it first, and gets a (lucky) quick hit with the next one, the early block will be invalid.

Yeah, I didn't actually mean every block found, but with every invalid block anyone ever finds, the chain forks. Even if it's only for a short while.

Yes, every invalid block is a fork, thats why it is invalid - it is not part of the longest chain.Those forks are usually just one block long, though.The chance for both sides of the fork to grow longer at the same time again is quite low.

On another note, I love how when slush starts finding blocks the hashrate jumps by 1,000 or more. I see it in my head like the idiots at the casino who watch someone hit jackpot on a slot machine and stand in line to play it because they think its "hot". I'm the guy who goes over to the machine they just lost on for an hour and make some quick money while the machine evens its payout ratio.

~~~~~~~~

Software is like sex: it's better when it's free... Linus Torvalds

~~~~~~~~~~~~~~~~

If I helped ya, feel free to drop me some coins... 1JF91kFQWnVAkwG1chn2fnrzotNyg1TxDQ

On another note, I love how when slush starts finding blocks the hashrate jumps by 1,000 or more. I see it in my head like the idiots at the casino who watch someone hit jackpot on a slot machine and stand in line to play it because they think its "hot". I'm the guy who goes over to the machine they just lost on for an hour and make some quick money while the machine evens its payout ratio.

This. I can imagine how much time they waste monitoring pools all the time