0%.....
Are we being 51%ed via a solo miner...?!?!
The banks bought up all of the new 14nm gear and are going to sink BTC?!?! RUN FOR THE HILLS!!!!!!!
Topic: [4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool - page 148. (Read 4382653 times)
December 12, 2014, 04:14:23 PM
December 12, 2014, 09:09:52 AM
Thanks MrTeal, I know that the 57% are 24h, but I stayed there 5 months and there never were such
long blocktimes in series. That was the question. WTF is happening in bitcoin network overall?
I switched two of my S3 to BTCGuild, but there it is nearly the same.
long blocktimes in series. That was the question. WTF is happening in bitcoin network overall?
I switched two of my S3 to BTCGuild, but there it is nearly the same.
December 12, 2014, 08:57:26 AM
Could someone explain to me the block time last days at slush? And the last block (8:09:29) now is void?
There are so many blocks about 6-8h. The actual block is about 18:15:00. WTF?!
Pool luck 57%?!
Somebody an explanation?
Slush lost the orphan race for that block.There are so many blocks about 6-8h. The actual block is about 18:15:00. WTF?!
Pool luck 57%?!
Somebody an explanation?
As for the 57% luck, all those quick blocks were more than 24 hours ago, so they aren't factored in.
December 12, 2014, 07:44:56 AM
I saw the block flagged at Blockchain.info as found by Bitminter.
(I think Bitminter found a block at the same time and the Chain was longer...)
(I think Bitminter found a block at the same time and the Chain was longer...)
December 12, 2014, 07:21:20 AM
Could someone explain to me the block time last days at slush? And the last block (8:09:29) now is void?
There are so many blocks about 6-8h. The actual block is about 18:15:00. WTF?!
Pool luck 57%?!
Somebody a explanation?
There are so many blocks about 6-8h. The actual block is about 18:15:00. WTF?!
Pool luck 57%?!
Somebody a explanation?
that +1
Block #333888 Duration: 8:09:29; Your shares:13007924 Validity: invalid
December 12, 2014, 07:07:50 AM
Could someone explain to me the block time last days at slush? And the last block (8:09:29) now is void?
There are so many blocks about 6-8h. The actual block is about 18:15:00. WTF?!
Pool luck 57%?!
Somebody an explanation?
There are so many blocks about 6-8h. The actual block is about 18:15:00. WTF?!
Pool luck 57%?!
Somebody an explanation?
December 12, 2014, 01:47:59 AM
Can anybody tell me what the average earnings per day have been over the last week? Thanks.
About 25,500 BTC or so.Sounds about right.
I've actually refined the calculations though, I'm now showing US$5.3 trillion per day.
LOL
December 11, 2014, 01:38:04 PM
Can anybody tell me what the average earnings per day have been over the last week? Thanks.
About 25,500 BTC or so.Sounds about right.
I've actually refined the calculations though, I'm now showing US$5.3 trillion per day.
December 11, 2014, 01:34:01 PM
Can anybody tell me what the average earnings per day have been over the last week? Thanks.
About 25,500 BTC or so.Sounds about right.
December 11, 2014, 09:24:22 AM
Can anybody tell me what the average earnings per day have been over the last week? Thanks.
About 25,500 BTC or so. 
December 11, 2014, 06:38:09 AM
Can anybody tell me what the average earnings per day have been over the last week? Thanks.
December 10, 2014, 11:28:37 PM
Very nice 3 blocks in a row after a 13 hour winter.
Sweeeeeeeeeet
Sweeeeeeeeeet
December 07, 2014, 09:00:40 PM
So with all this knowledge we all have and slush has. and the hardware and software we have. Could there not be like a failsafe timout. So if the pool notices someone hopping or adding and removing hash power constantly and not keeping it at a steady one. Decreasing the luck and the quantity of solving blocks in a 1-2 days.
I mean I'm sure there is away to track those kind of things. I'm actualy certian. So if someone from a certain IP is doing that.. The Server thrown a few hour timeout period. This would have to be over 2-4 times in a daily basis.
The server would learn who is hopping the most or who is adding and removing hashpower on a daily/weekly basis, which then tells the server who to watch out for and to throw a timeout on them if it happens to often.
It could work. I know it can
hash rate is jumping again that means the pool jumpers think where going to find a block soon!!YEAHHHI mean I'm sure there is away to track those kind of things. I'm actualy certian. So if someone from a certain IP is doing that.. The Server thrown a few hour timeout period. This would have to be over 2-4 times in a daily basis.
The server would learn who is hopping the most or who is adding and removing hashpower on a daily/weekly basis, which then tells the server who to watch out for and to throw a timeout on them if it happens to often.
It could work. I know it can
The chance of finding a block does not change. Jumpers have no way of knowing when it be found. Could be one minute (where they won't make much) or another 24 hours. You can only calculate luck to finding it AFTER it has been found. Like rolling dice. Each roll is independent of the last roll. That was Sathoshi's intention. The faster you roll the dice, more often your number will come up. So more hashing power is simply like rolling the dice faster, but you might still go many rolls without hitting your number.
finally somebody gets what luck is. tell this to cris and parker
December 07, 2014, 07:54:27 PM
So with all this knowledge we all have and slush has. and the hardware and software we have. Could there not be like a failsafe timout. So if the pool notices someone hopping or adding and removing hash power constantly and not keeping it at a steady one. Decreasing the luck and the quantity of solving blocks in a 1-2 days.
I mean I'm sure there is away to track those kind of things. I'm actualy certian. So if someone from a certain IP is doing that.. The Server thrown a few hour timeout period. This would have to be over 2-4 times in a daily basis.
The server would learn who is hopping the most or who is adding and removing hashpower on a daily/weekly basis, which then tells the server who to watch out for and to throw a timeout on them if it happens to often.
It could work. I know it can
hash rate is jumping again that means the pool jumpers think where going to find a block soon!!YEAHHHI mean I'm sure there is away to track those kind of things. I'm actualy certian. So if someone from a certain IP is doing that.. The Server thrown a few hour timeout period. This would have to be over 2-4 times in a daily basis.
The server would learn who is hopping the most or who is adding and removing hashpower on a daily/weekly basis, which then tells the server who to watch out for and to throw a timeout on them if it happens to often.
It could work. I know it can
The chance of finding a block does not change. Jumpers have no way of knowing when it be found. Could be one minute (where they won't make much) or another 24 hours. You can only calculate luck to finding it AFTER it has been found. Like rolling dice. Each roll is independent of the last roll. That was Sathoshi's intention. The faster you roll the dice, more often your number will come up. So more hashing power is simply like rolling the dice faster, but you might still go many rolls without hitting your number.
December 07, 2014, 03:42:02 PM
Wehey! I like the update to the dashboard .... we can now see the details about the current round.
Any chance of reloading my developer points then?
Any chance of reloading my developer points then?
December 07, 2014, 01:40:03 PM
So with all this knowledge we all have and slush has. and the hardware and software we have. Could there not be like a failsafe timout. So if the pool notices someone hopping or adding and removing hash power constantly and not keeping it at a steady one. Decreasing the luck and the quantity of solving blocks in a 1-2 days.
I mean I'm sure there is away to track those kind of things. I'm actualy certian. So if someone from a certain IP is doing that.. The Server thrown a few hour timeout period. This would have to be over 2-4 times in a daily basis.
The server would learn who is hopping the most or who is adding and removing hashpower on a daily/weekly basis, which then tells the server who to watch out for and to throw a timeout on them if it happens to often.
It could work. I know it can
hash rate is jumping again that means the pool jumpers think where going to find a block soon!!YEAHHHI mean I'm sure there is away to track those kind of things. I'm actualy certian. So if someone from a certain IP is doing that.. The Server thrown a few hour timeout period. This would have to be over 2-4 times in a daily basis.
The server would learn who is hopping the most or who is adding and removing hashpower on a daily/weekly basis, which then tells the server who to watch out for and to throw a timeout on them if it happens to often.
It could work. I know it can
December 07, 2014, 10:09:29 AM
So with all this knowledge we all have and slush has. and the hardware and software we have. Could there not be like a failsafe timout. So if the pool notices someone hopping or adding and removing hash power constantly and not keeping it at a steady one. Decreasing the luck and the quantity of solving blocks in a 1-2 days.
I mean I'm sure there is away to track those kind of things. I'm actualy certian. So if someone from a certain IP is doing that.. The Server thrown a few hour timeout period. This would have to be over 2-4 times in a daily basis.
The server would learn who is hopping the most or who is adding and removing hashpower on a daily/weekly basis, which then tells the server who to watch out for and to throw a timeout on them if it happens to often.
It could work. I know it can
Fluctuating hashrate has nothing to do with pool luck, gaining and losing hashpower will increase and decrease our chance of finding blocks but still does not affect our luck.I mean I'm sure there is away to track those kind of things. I'm actualy certian. So if someone from a certain IP is doing that.. The Server thrown a few hour timeout period. This would have to be over 2-4 times in a daily basis.
The server would learn who is hopping the most or who is adding and removing hashpower on a daily/weekly basis, which then tells the server who to watch out for and to throw a timeout on them if it happens to often.
It could work. I know it can
Luck is luck, ok. So go solo mining if the hashrate don't influence it.
1 Petahash , this is not cat pee .
If you are rolling it 6 times a minute, you'd expect to roll one 5 per minute.
If you roll it 12 times a minute, you'd expect to roll two per minute.
Adding or removing hashrate is akin to rolling the die more or less often, which changes the number of 5s you will roll. Luck on the other hand is difference between what you expect to roll (one 5 per six rolls) vs what actually happens.
When people leave the pool, we are less likely to find blocks, that's obvious. However, when we do find a block there is less people to split it over and so your payout per block is the same. Having a larger or smaller pool has no effect on expected payout, no effect on luck, but will affect variance.
Also, luck is a human made measurement of past performance vs the expected. "Luck" has no bearing on future events regardless of what superstitious people think. That is why casinos rack in the cash.
December 07, 2014, 10:00:32 AM
So with all this knowledge we all have and slush has. and the hardware and software we have. Could there not be like a failsafe timout. So if the pool notices someone hopping or adding and removing hash power constantly and not keeping it at a steady one. Decreasing the luck and the quantity of solving blocks in a 1-2 days.
I mean I'm sure there is away to track those kind of things. I'm actualy certian. So if someone from a certain IP is doing that.. The Server thrown a few hour timeout period. This would have to be over 2-4 times in a daily basis.
The server would learn who is hopping the most or who is adding and removing hashpower on a daily/weekly basis, which then tells the server who to watch out for and to throw a timeout on them if it happens to often.
It could work. I know it can
Fluctuating hashrate has nothing to do with pool luck, gaining and losing hashpower will increase and decrease our chance of finding blocks but still does not affect our luck.I mean I'm sure there is away to track those kind of things. I'm actualy certian. So if someone from a certain IP is doing that.. The Server thrown a few hour timeout period. This would have to be over 2-4 times in a daily basis.
The server would learn who is hopping the most or who is adding and removing hashpower on a daily/weekly basis, which then tells the server who to watch out for and to throw a timeout on them if it happens to often.
It could work. I know it can
Luck is luck, ok. So go solo mining if the hashrate don't influence it.
1 Petahash , this is not cat pee .
If you are rolling it 6 times a minute, you'd expect to roll one 5 per minute.
If you roll it 12 times a minute, you'd expect to roll two per minute.
Adding or removing hashrate is akin to rolling the die more or less often, which changes the number of 5s you will roll. Luck on the other hand is difference between what you expect to roll (one 5 per six rolls) vs what actually happens.
When people leave the pool, we are less likely to find blocks, that's obvious. However, when we do find a block there is less people to split it over and so your payout per block is the same. Having a larger or smaller pool has no effect on expected payout, no effect on luck, but will affect variance.
December 07, 2014, 08:29:05 AM
So with all this knowledge we all have and slush has. and the hardware and software we have. Could there not be like a failsafe timout. So if the pool notices someone hopping or adding and removing hash power constantly and not keeping it at a steady one. Decreasing the luck and the quantity of solving blocks in a 1-2 days.
I mean I'm sure there is away to track those kind of things. I'm actualy certian. So if someone from a certain IP is doing that.. The Server thrown a few hour timeout period. This would have to be over 2-4 times in a daily basis.
The server would learn who is hopping the most or who is adding and removing hashpower on a daily/weekly basis, which then tells the server who to watch out for and to throw a timeout on them if it happens to often.
It could work. I know it can
I mean I'm sure there is away to track those kind of things. I'm actualy certian. So if someone from a certain IP is doing that.. The Server thrown a few hour timeout period. This would have to be over 2-4 times in a daily basis.
The server would learn who is hopping the most or who is adding and removing hashpower on a daily/weekly basis, which then tells the server who to watch out for and to throw a timeout on them if it happens to often.
It could work. I know it can
Fluctuating hashrate has nothing to do with pool luck, gaining and losing hashpower will increase and decrease our chance of finding blocks but still does not affect our luck.
Luck is luck, ok. So go solo mining if the hashrate don't influence it.
1 Petahash , this is not cat pee .
December 07, 2014, 06:31:43 AM
None of that matters on Slush's pool. If a miner is away for more than 1.5 hours they are paid nothing of any future blocks found regardless if they hashed for 24 hours without a block being found. Only the active miners during the previous 1.5 hours of a block being found get paid. That is why I left Slush. I hashed over 24 hours and had to turn my rig off to do something. Was over 1.5 hours and I got paid nothing, even though I hashed over 24 hours with no blocks being found.
Does anyone know if this rule is applied on a per-worker or per-account basis ?
I have a few workers proxied through a local stratum proxy but presented as separate workers; am I better off having them mine as the same worker ?
Good question. Don't know if it is per account or per worker. Should be per account to be more fair. The algorithm is explained somewhere. Maybe it will say?
Jump to: