Bitcoin Forum
January 24, 2018, 06:18:16 AM *
News: Latest stable version of Bitcoin Core: 0.15.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Poll
Question: What type of pool payouts do you prefer?
Bitcoins - 3211 (80.4%)
Bank transfer / USD - 410 (10.3%)
Gold/silver coins and bars - 371 (9.3%)
Total Voters: 3990

Pages: « 1 ... 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 [1082] 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 »
  Print  
Author Topic: [150+ PH] SlushPool (slushpool.com); World's First Mining Pool  (Read 4322421 times)
btiAndy
Full Member
***
Offline Offline

Activity: 150


View Profile
February 08, 2016, 08:19:33 PM
 #21621

Yeah in hindsight now and thinking about this more clearly something really stinks about this explanation from Slush. He is really not coming clean at all here.

For months we have been watching this cycle and have made repeated attempts to communicate this pattern to him for explanation. Nothing. Now he is basically saying that this particular miner was "accidentally" withholding blocks and that the problem has been fixed...and in fact he knows it has been fixed as that same miner has since the repair cracked two blocks... just not right and not near enough.

Slush should have banned that miner immediately (there must be a way to do this) and made an attempt to recover lost funds to return to those of us who stuck with him for so long. I have been gone from Slush for a few weeks now (actually stopped mining all together as there is no suitable outlet for a small scale miner like me anymore), Slush has definitely soured me on BTC mining as a result though.

Really rotten.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1516774696
Hero Member
*
Offline Offline

Posts: 1516774696

View Profile Personal Message (Offline)

Ignore
1516774696
Reply with quote  #2

1516774696
Report to moderator
1516774696
Hero Member
*
Offline Offline

Posts: 1516774696

View Profile Personal Message (Offline)

Ignore
1516774696
Reply with quote  #2

1516774696
Report to moderator
1516774696
Hero Member
*
Offline Offline

Posts: 1516774696

View Profile Personal Message (Offline)

Ignore
1516774696
Reply with quote  #2

1516774696
Report to moderator
notabeliever
Hero Member
*****
Offline Offline

Activity: 658


View Profile WWW
February 08, 2016, 08:48:48 PM
 #21622

not happy

Pool url: pool.burstcoin.de:8080           
Reward Assignment address: BURST-GHTV-7ZP3-DY4B-FPBFA
jonnybravo0311
Legendary
*
Offline Offline

Activity: 1288


Mine at Jonny's Pool


View Profile WWW
February 08, 2016, 08:58:04 PM
 #21623

Yeah in hindsight now and thinking about this more clearly something really stinks about this explanation from Slush. He is really not coming clean at all here.

For months we have been watching this cycle and have made repeated attempts to communicate this pattern to him for explanation. Nothing. Now he is basically saying that this particular miner was "accidentally" withholding blocks and that the problem has been fixed...and in fact he knows it has been fixed as that same miner has since the repair cracked two blocks... just not right and not near enough.

Slush should have banned that miner immediately (there must be a way to do this) and made an attempt to recover lost funds to return to those of us who stuck with him for so long. I have been gone from Slush for a few weeks now (actually stopped mining all together as there is no suitable outlet for a small scale miner like me anymore), Slush has definitely soured me on BTC mining as a result though.

Really rotten.
As was explained earlier, you cannot simply ban somebody immediately.  You don't really know someone is performing a block withholding attack until a large number of hashes have been produced without a block solution.  Plenty of pools regularly suffer through long rounds - it is the nature of mining.  It goes to follow, then, that an individual miner also suffers the same.  Kano suggested 10 blocks earlier.  At that point, the chances of it being "luck" are exceptionally minimal.  Unfortunately, 250BTC have been lost to the miner.

Jonny's Pool - Mine with us and help us grow!  Support a pool that supports Bitcoin, not a hardware manufacturer's pockets!  No SPV cheats.  No empty blocks.
btiAndy
Full Member
***
Offline Offline

Activity: 150


View Profile
February 08, 2016, 10:02:06 PM
 #21624

Yeah in hindsight now and thinking about this more clearly something really stinks about this explanation from Slush. He is really not coming clean at all here.

For months we have been watching this cycle and have made repeated attempts to communicate this pattern to him for explanation. Nothing. Now he is basically saying that this particular miner was "accidentally" withholding blocks and that the problem has been fixed...and in fact he knows it has been fixed as that same miner has since the repair cracked two blocks... just not right and not near enough.

Slush should have banned that miner immediately (there must be a way to do this) and made an attempt to recover lost funds to return to those of us who stuck with him for so long. I have been gone from Slush for a few weeks now (actually stopped mining all together as there is no suitable outlet for a small scale miner like me anymore), Slush has definitely soured me on BTC mining as a result though.

Really rotten.
As was explained earlier, you cannot simply ban somebody immediately.  You don't really know someone is performing a block withholding attack until a large number of hashes have been produced without a block solution.  Plenty of pools regularly suffer through long rounds - it is the nature of mining.  It goes to follow, then, that an individual miner also suffers the same.  Kano suggested 10 blocks earlier.  At that point, the chances of it being "luck" are exceptionally minimal.  Unfortunately, 250BTC have been lost to the miner.

OK Fair enough, thank you for the explanation. I am not sure on the time frame though required for analysis with regard to Kano's explanation.I am sure I am sounding too simplistic and like a "Noob" but my question still stands, ..how long should it take to expose a withholding attack under these circumstances? At Slush this has been going on for at least 3 months in my practical opinion...we saw it repeatedly that when Slush dipped down to ca. 33 PH  the blocks started hitting, the minute we returned to 40PH+ all of a sudden performance went south. In simple terms, it seemed that when one big miner left the pool things would return to "normal", when he returned it went to hell.   just from a standpoint of analyzing a pattern of events should Slush not have been able to pick up on this pattern and figured out where the problem was?

Still curious...
btiAndy
Full Member
***
Offline Offline

Activity: 150


View Profile
February 08, 2016, 10:19:59 PM
 #21625

And one last thing, I must say I really enjoy reading your posts Jonny and I have learned a lot over the past few months from your posts...I just want to clarify my statement in my previous post regarding banning the offending miner; I did not mean ban the miner in advance...I think the bad part here is that Slush has stated he contacted this miner after discovering the issue and the solution was simply to "fix" the "unintentional" problem and let this miner continue mining without penalty...no matter if the act was intentional or non-intentional I think those of us who were affected by this problem should have been respected a bit more.

Of course I am speaking from a "blue-sky" customer service standpoint and nothing more, I am sure that legally Slush owes his miners no real duty of service and is not obligated  in any way to compensate miners for wasted time and hash on his pool...it is gambling in the end and we should all know that. I am just saying that for the common good this offending miner who has been supposedly identified by Slush as the cause of the withholding attack should have been removed from the mining pool as consideration to the other miners still there.
jonnybravo0311
Legendary
*
Offline Offline

Activity: 1288


Mine at Jonny's Pool


View Profile WWW
February 09, 2016, 03:21:17 PM
 #21626

To address the concerns in your first reply... it's a tough bit of analysis.  In an ideal world, if the pool at 40PH was experiencing the same luck as the pool at 33PH, then it would be apparent that 7PH was withholding blocks.  If all 7PH belonged to a single miner, you found your culprit.  Unfortunately, the problem remains: you must wait some period of time before you are relatively certain that the miner isn't just unlucky.  I'm not sure how many, if any, pool operators have written this kind of analytics into their code.  It's a pretty simple bit of analysis: count shares submitted by miner vs number of block solutions.  If number of shares is some percentage over expectations, flag as potential block withholding.

That doesn't solve it, but merely alerts the pool operator something might be amiss.  Now the pool operator has to take action.  What action the operator takes is really the basis of your second reply.  Personally, I don't agree with Slush's decision to allow the miner to continue on his pool without any kind of repercussions.  "Sorry, my bad!" just doesn't cut it.  Intentional or not, if a miner is going to write his own custom firmware, that miner should be testing it on a simulated environment, not forcing the public to assume the risks of untested code.  I'm glad for the miners on the pool that the problem was found and addressed; however, if I were a miner on the pool, I'd be seriously considering going elsewhere if neither the offending miner, nor the pool operator were held accountable in some fashion.

Jonny's Pool - Mine with us and help us grow!  Support a pool that supports Bitcoin, not a hardware manufacturer's pockets!  No SPV cheats.  No empty blocks.
bctmke
Sr. Member
****
Offline Offline

Activity: 294


View Profile
February 09, 2016, 03:54:14 PM
 #21627

I am just glad I left the pool a few months back before I realized how bad it was (I had happened to get lucky and come across Kano's pool and I liked the transparency far better so I switched over).

NXS is on the move!   Come subscribe to our subreddit  https://www.reddit.com/r/nexusearth/
Come mine NXS at http://nxsminingpool.com
welshy82
Member
**
Offline Offline

Activity: 112


View Profile
February 09, 2016, 06:02:07 PM
 #21628

7 hours a block

Current Round Duration   05 hrs at 46.70 Ph/s

Current time   2016-02-09 18:01:05
Current Round Start:   2016-02-09 12:46:51
Current Round Duration   05:14:21
Current Shares CDF:   74.35%
Current Bitcoin block, difficulty:   397583, 144116447847
Pool Luck (1 day, 7 days, 30 days):   91%, 125%, 95%
Total Shares in the Round:   196092066752
Pool Effective Hash Rate (30 min average):   46.70 Ph/s

time to leave slushes and goto kanos pool
ohmygod21
Full Member
***
Offline Offline

Activity: 224


View Profile
February 09, 2016, 06:38:32 PM
 #21629

7 hours a block

Current Round Duration   05 hrs at 46.70 Ph/s

Current time   2016-02-09 18:01:05
Current Round Start:   2016-02-09 12:46:51
Current Round Duration   05:14:21
Current Shares CDF:   74.35%
Current Bitcoin block, difficulty:   397583, 144116447847
Pool Luck (1 day, 7 days, 30 days):   91%, 125%, 95%
Total Shares in the Round:   196092066752
Pool Effective Hash Rate (30 min average):   46.70 Ph/s

time to leave slushes and goto kanos pool

just now pool luck 124% / 1 day with no block found so there is a serioussssssss problem

jumped from 91 % at 124 % with no block found between your post welshy

Someone is stealing blocks for sure .

Edit1 , now just founded a block and 124% > 127% /day

Edit2 redrop to 96% /day , 1 hour later -_-


I m done with this pool , just leaving to kano after the end of my last rent .

disclaimer201
Legendary
*
Offline Offline

Activity: 1442


View Profile
February 09, 2016, 09:10:16 PM
 #21630

I have to say I now agree with previous posters that something is fishy. We need more transparency and the issue has been going on for far too long. I have some dark thoughts/fears that the mining pool could have been hacked in the recent past (this would not be for the first time) and that the ominous miner is Slush himself to mine back lost funds. Not sure if that would make any sense though  Huh
bittalc1
Full Member
***
Offline Offline

Activity: 166


View Profile
February 09, 2016, 09:58:20 PM
 #21631

I have to say I now agree with previous posters that something is fishy. We need more transparency and the issue has been going on for far too long. I have some dark thoughts/fears that the mining pool could have been hacked in the recent past (this would not be for the first time) and that the ominous miner is Slush himself to mine back lost funds. Not sure if that would make any sense though  Huh
We all can speculate, but its not fair that we lost all that electricity and not earning shit because of this operator wants to keep things in dark. From the start i mined there but after i saw that the luck is 150℅ and we found two blocks only!! I mean WTF we are not sheeps we can see the deal here! Some fucktard is stealing and hideing his trails...
welshy82
Member
**
Offline Offline

Activity: 112


View Profile
February 09, 2016, 10:05:04 PM
 #21632

i would of thought he would come on and at least say something about what has happend rather than ignor everyone and not giving a explanation
welshy82
Member
**
Offline Offline

Activity: 112


View Profile
February 09, 2016, 10:08:19 PM
 #21633

slush was Last Active:   October 06, 2015, 01:18:06 PM
bittalc1
Full Member
***
Offline Offline

Activity: 166


View Profile
February 09, 2016, 10:20:42 PM
 #21634

slush was Last Active:   October 06, 2015, 01:18:06 PM
T
Yea i mean that is the deal. From us he is earning ~50K $ monthly and he has some serious mind condition that he is not able to come to this forum and give some small explanation. I mean wtf my mind is not stupid enough to understand his explaining that he wont participate in this forum that is making a lot of money for him.

Edit: my mind also cant process the last bullshit that some random miner done the bad luck in last months!!!
btiAndy
Full Member
***
Offline Offline

Activity: 150


View Profile
February 09, 2016, 11:02:47 PM
 #21635

I notice Slush has not bothered to update anything on Facebook since his announcement either. I am still shocked that there is not more anger about the fact that this "unintentional miner" is being allowed to continue on mining as if nothing has happened...dheinz57 said it right, offending miner should be responsible for his custom firmware no matter if t was a genuine mistake.

ShrykeZ
Hero Member
*****
Offline Offline

Activity: 650


View Profile
February 09, 2016, 11:09:53 PM
 #21636

I notice Slush has not bothered to update anything on Facebook since his announcement either. I am still shocked that there is not more anger about the fact that this "unintentional miner" is being allowed to continue on mining as if nothing has happened...dheinz57 said it right, offending miner should be responsible for his custom firmware no matter if t was a genuine mistake.



I am more shocked that people are still happy to continue mining here after all the obvious problems that have been on going for a prolonged time.
krisgt30
Sr. Member
****
Offline Offline

Activity: 266


View Profile WWW
February 10, 2016, 12:37:36 AM
 #21637

According to the calculators that seem to be the standard here, on the current difficulty at 40ph, this pool should be generating a block every 4 hours (3 and change on last difficulty). Looking back at the historical block timestamps, I highly doubt all those 8+ hour chunks with no blocks were all bad luck at that hash rate. To be quite honest, it is WAY more than 250BTC that was withheld. I wouldnt be surprised if it was in the thousands per year.

www.bcmonster.com Bitcoin Mining Pool - [PPLNS / pays TX]  / Easy Live Dashboard / Help us get up to 1PH. Donate: 1QGZQBhXMo2jVc45wLEsp2bn5agF8SZSuY
kano
Legendary
*
Online Online

Activity: 2338


Linux since 1997 RedHat 4


View Profile
February 10, 2016, 12:41:52 AM
 #21638

According to the calculators that seem to be the standard here, on the current difficulty at 40ph, this pool should be generating a block every 4 hours (3 and change on last difficulty). Looking back at the historical block timestamps, I highly doubt all those 8+ hour chunks with no blocks were all bad luck at that hash rate. To be quite honest, it is WAY more than 250BTC that was withheld. I wouldnt be surprised if it was in the thousands per year.
Yes the 250BTC is the absolute minimum to have LOW confidence that someone is withholding.

Not finding a block for 10 Network diff is very rare.
0.99995460007024  1000.000%  1 in 22026.5

That would of course mean he was paying attention to individual miner block statistics and caught them out VERY early.

Pool: https://kano.is Here on Bitcointalk: Forum BTC: 1KanoPb8cKYqNrswjaA8cRDk4FAS9eDMLU
FreeNode IRC: irc.freenode.net channel #kano.is Majority developer of the ckpool code
Help keep Bitcoin secure by mining on pools with full block verification on all blocks - and NO empty blocks!
simonpeter35
Jr. Member
*
Offline Offline

Activity: 37


View Profile
February 10, 2016, 01:56:37 AM
 #21639

Let's move on.

What is the best pool, beside Kano. On the comparison page, Kano only have 6 blocks.
ohmygod21
Full Member
***
Offline Offline

Activity: 224


View Profile
February 10, 2016, 12:07:01 PM
 #21640

actually 2 blocks - 14 hours . at 46 - 48 ph lol

another day with mega rounds Cheesy

edit : just cracked a new block : time between last : 8 h 30
Pages: « 1 ... 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 [1082] 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!