[4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool

[trasla]

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.

Only theres no mechanism evening the payout-ratio for unlucky pools
(Of course there is no reason to jump to a pool thats found some lucky quick blocks, too.)

[1713518328]

1713518328

[n0creativity]

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.

Only theres no mechanism evening the payout-ratio for unlucky pools
(Of course there is no reason to jump to a pool thats found some lucky quick blocks, too.)

Very true... which is why I just stay here with Slush. My luck goes as this pool's luck goes.  I don't have time to be changing all my miners around like a day trader dealing in penny stocks.  I have my failover pools setup, but that's about it.

[bspurloc]

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 like this explanation cuz I totally stop paying attention to what I am reading and just accept it for fact. I just want BTC! trying to not try to understand how it works precisely! haha

[bspurloc]

Just got this emailed to me from Avalon.
http://imgur.com/a/fqpME

From those pictures, any drop in network hash rate is only temporary.

And it's back... Oh well.

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

scripts only require time to write them after that u sit back feeding your face

[dopamine]

What setting should I put for suggested difficulty if I own a avalon?

[n0creativity]

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

scripts only require time to write them after that u sit back feeding your face

Also true... although the tough part is writing a script that can accurately predict a pool's luck.  I'll get on that right after I finish writing the script that will tell me the next numbers in the lottery... 

[ibfr33k]

Send me a copy when you get it done 

[bspurloc]

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

scripts only require time to write them after that u sit back feeding your face

Also true... although the tough part is writing a script that can accurately predict a pool's luck.  I'll get on that right after I finish writing the script that will tell me the next numbers in the lottery...  

its not the luck you are after it is a block being found.
if u r on pool x for 5 hours and pool x doesnt score like slush where leaving nets u 0, and script sees slush just found a block, then move all to slush hoping for a quick block. win win if it happens with that kind of speed.
then u just decide what to do if the next block takes more than 2 hours or something.
what do these people care, they have 500gh/s+ and most likely have 1000's of btc.
many rich people are greedy and need schemes to milk every drop.


OH... also some have other pools set as the backup... so if other pools are being syn flooded then their SCRIPTS would move them to slush if slush was the backup.... regardless of luck

[bspurloc]

What setting should I put for suggested difficulty if I own a avalon?

if you owned an avalon you would know the speed. then in the miner setup pull down for DIFF u would select the speed and the associated diff. if you knew the speed and told us we could go to the miner settings and interact with the pull down to tell you too

[dopamine]

didnt see the drop down menu thanks 

[n0creativity]

Also true... although the tough part is writing a script that can accurately predict a pool's luck.  I'll get on that right after I finish writing the script that will tell me the next numbers in the lottery...  

its not the luck you are after it is a block being found.
if u r on pool x for 5 hours and pool x doesnt score like slush where leaving nets u 0, and script sees slush just found a block, then move all to slush hoping for a quick block. win win if it happens with that kind of speed.
then u just decide what to do if the next block takes more than 2 hours or something.
what do these people care, they have 500gh/s+ and most likely have 1000's of btc.
many rich people are greedy and need schemes to milk every drop.


OH... also some have other pools set as the backup... so if other pools are being syn flooded then their SCRIPTS would move them to slush if slush was the backup.... regardless of luck

And how, exactly, is that not just a method of attempting to predict luck?

1st off any decent mining app has failover capability not need for a script... if yours doesn't I suggest switching (cgminer is my personal pref).
I am happy being the tortoise rather than the hair but if I was going to attempt to outwit luck it would go something like this:
Personally I would consider mining constantly on a PPS or PPLNS and only switch to slush when the following condition occurs:

Take the last N rounds (probably 100) on slush, round them to the nearest 15 minute mark (so 18 would = 15, 24 would = 30, 65 would = 60, 207.6 would = 215,  etc...) and then take the arithmatic mode of that list, subtract 10 minutes and if any given round on slush hits that time mark, I would switch to mining Slush with the hope that Slush would find a block about 10 minutes after I switch over so I get paid full share on slush and all my PPS or PPLNS are making money.

But I would still be trying to determine how lucky the Slush pool is.

[trasla]

do i get this right, you are suggesting some kind of... reverse hopping?

at first, hoppers switched to a pool when a new round started, knowing they would still get paid enough for a finished block in the old pool.
After scoring has been changed to prevent this, and shares submitted later in the round gain higher scores, its time for hopping 2.0!
The average round time could either be calculated via the n last rounds, or just estimated by pool hash-rate, and neo hoppers pop in to provide well scoring late shares.

Next evolutionary step will be hybrid-hopping, just find yourself one pool with proportional distribution to join early in the rounds, and one with slush-scoring to join late in rounds

[TObject]

No need to even calculate anything, there is "Current shares CDF" right on the stats page. Jump to the pool when that number is high enough for your liking.

Just kidding. LOL

[pembo210]

18674    2013-06-21 00:55:36    1:07:59    16477367    2305    0.00358311    242516    25.52708500    90 confirmations left

18673    2013-06-20 23:47:37    1:05:06    15732349    2266    0.00386177    242509    25.25864857    83 confirmations left

18672    2013-06-20 22:42:31    1:18:33    19158866    380    0.00313452    242497    25.06230101    71 confirmations left

18671    2013-06-20 21:23:58    3:47:07    54211201    4360    0.00000000    242486    25.25275299    60 confirmations left

Anyone else get zero on #18671

[yamancool63]

18674    2013-06-21 00:55:36    1:07:59    16477367    2305    0.00358311    242516    25.52708500    90 confirmations left

18673    2013-06-20 23:47:37    1:05:06    15732349    2266    0.00386177    242509    25.25864857    83 confirmations left

18672    2013-06-20 22:42:31    1:18:33    19158866    380    0.00313452    242497    25.06230101    71 confirmations left

18671    2013-06-20 21:23:58    3:47:07    54211201    4360    0.00000000    242486    25.25275299    60 confirmations left

Anyone else get zero on #18671

Looks like you had a disconnect near the end of that round because of your low share count in the next round and steady reward.

[diskodasa]

.....Aaand this topic should be called [16000 GH/s] Slush's Pool (mining.bitcoin.cz); TX FEES + UserDiff; ASIC tested 

[bspurloc]

.....Aaand this topic should be called [16000 GH/s] Slush's Pool (mining.bitcoin.cz); TX FEES + UserDiff; ASIC tested 

the topic was changed to 12,000 so  am sure it will go to 16k sooner or later haha...

gotta love the post count anti OMG scammer count negater. 20+ posts and still 42. I will never get to 55 so I can collect BTC!

[diskodasa]

.....Aaand this topic should be called [16000 GH/s] Slush's Pool (mining.bitcoin.cz); TX FEES + UserDiff; ASIC tested 

the topic was changed to 12,000 so  am sure it will go to 16k sooner or later haha...

gotta love the post count anti OMG scammer count negater. 20+ posts and still 42. I will never get to 55 so I can collect BTC!

Yes, but you have to keep on 55th post for a week to be eligible for getting block solved! This is my 8 pseudonim, the other 7 are getting blocks.....

[pembo210]

...

18672    2013-06-20 22:42:31    1:18:33    19158866    380    0.00313452    242497    25.06230101    71 confirmations left

18671    2013-06-20 21:23:58    3:47:07    54211201    4360    0.00000000    242486    25.25275299    60 confirmations left

Anyone else get zero on #18671

Looks like you had a disconnect near the end of that round because of your low share count in the next round and steady reward.

Yeah, I tripped my circuit breaker 

[laserray]

.....Aaand this topic should be called [16000 GH/s] Slush's Pool (mining.bitcoin.cz); TX FEES + UserDiff; ASIC tested 

the topic was changed to 12,000 so  am sure it will go to 16k sooner or later haha...

gotta love the post count anti OMG scammer count negater. 20+ posts and still 42. I will never get to 55 so I can collect BTC!

16TH? It's now at 18.4TH... so crazy.