Topic: [4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool - page 952. (Read 4382653 times)
October 20, 2011, 04:21:20 PM
lolz, 3 min or so after I joined, it finished that last block, and now on the new block @ 2 min.
October 20, 2011, 04:20:54 PM
One day and five hours. Longest. Round. Ever. :-)
October 20, 2011, 04:17:26 PM
Give it a rest already
The pool was down for a day
It only been back 2hrs
it's just miller time here on the US east coast
The pool was down for a day
It only been back 2hrs
it's just miller time here on the US east coast
October 20, 2011, 04:08:41 PM
The current block is at 3 hours 55 minutes and counting...
+ 1 day
October 20, 2011, 03:39:52 PM
For those wondering if they should give Slush another try, I'd like to remind them that getting Namecoins via merged mining helps to recover one's electricity cost, and maybe even eke out a 4 or 5% profit.
With other pools (most of them -- any that lack Merged Mining) you might very well be losing money with the current price/difficulty.
With other pools (most of them -- any that lack Merged Mining) you might very well be losing money with the current price/difficulty.
October 20, 2011, 03:25:23 PM
You completely missed the joke...lol
October 20, 2011, 03:23:42 PM
Me too, because one of my sites is suffering a pretty severe DDoS attack right now and I need somewhere to send the traffic to once I update my DNS records......
What was your pool's IP again ?
What was your pool's IP again ?
http://api.bitcoin.cz
or
http://api2.bitcoin.cz
each on port 8332
You completely missed the joke...lol
October 20, 2011, 03:21:34 PM
Me too, because one of my sites is suffering a pretty severe DDoS attack right now and I need somewhere to send the traffic to once I update my DNS records......
What was your pool's IP again ?
What was your pool's IP again ?
http://api.bitcoin.cz
or
http://api2.bitcoin.cz
each on port 8332
October 20, 2011, 03:19:50 PM
Me too, because one of my sites is suffering a pretty severe DDoS attack right now and I need somewhere to send the traffic to once I update my DNS records......
What was your pool's IP again ?
What was your pool's IP again ?
October 20, 2011, 03:11:37 PM
Yeah, I hope everyone comes back to Slush -- otherwise I'm going to have more work ahead of me to set all my miners to use a different primary pool.
Right now they're all stuck on Slush's pool since it's the primary, with its 697 GH/s.
The current block is at 3 hours 55 minutes and counting...
If more people don't return I'm going to have to switch pools.
Slush, is it likely that the problem is actually fixed permanently? Did you "do anything" or did the DDoS just take a break?
If you really believe in your pool still, we need to let people know that so they return.
Right now they're all stuck on Slush's pool since it's the primary, with its 697 GH/s.
The current block is at 3 hours 55 minutes and counting...
If more people don't return I'm going to have to switch pools.
Slush, is it likely that the problem is actually fixed permanently? Did you "do anything" or did the DDoS just take a break?
If you really believe in your pool still, we need to let people know that so they return.
October 20, 2011, 02:28:42 PM
Awesome! already switched my miners back over 
October 20, 2011, 02:28:12 PM
October 20, 2011, 02:18:52 PM
Slush: so happy to see you alive and kicking my old friend, I will bring my miners over and help solve this block (I just hope you stay alive)
(I just hope you stay alive) 
October 20, 2011, 02:03:08 PM
w00t, thanks slush!
October 20, 2011, 01:54:27 PM
Yes, longest round on my pool ever, but we're up again :-).
October 20, 2011, 01:40:37 PM
longest round I have ever seen... 
October 20, 2011, 01:39:30 PM
You back up for good? Or is this a temporary thing?
October 20, 2011, 01:36:47 PM
Botnet owners don't even need to get that e-mail. Someone will just post here "Hey, I just got an e-mail with this IP: ***".
October 20, 2011, 01:25:24 PM
If you pull from your DB of users, those who have hashed over a certain amount in the last couple weeks for instance... you could tell with a degree of certainty that these are all trusted people.
So... then you email all those users (I would be one of these people)...
Just email a private ip for the server to those users... or perhaps a domain name whatever... just something you don't post on here.
Botnets can mine at like 80-100 GH/s if they want I think. It is just terribly inefficient. But they don't care because they aren't paying for electricity or the pipes. So you might send out an email to the botnet because they could be one of your fastest miners? So... then you email all those users (I would be one of these people)...
Just email a private ip for the server to those users... or perhaps a domain name whatever... just something you don't post on here.
October 20, 2011, 01:24:53 PM
Slush... I have an idea...
Soooo...
Basically, you have a problem with public addresses for your pool.
If only you could ensure that no one knew how to find your pool unless they had trust... you could just use a static IP and have people mine there.
Here is one REALLY good litmus to determine whether or not a user should have trust... hashing.
If you pull from your DB of users, those who have hashed over a certain amount in the last couple weeks for instance... you could tell with a degree of certainty that these are all trusted people.
So... then you email all those users (I would be one of these people)...
Just email a private ip for the server to those users... or perhaps a domain name whatever... just something you don't post on here.
Sure, you'll lose a lot of hashing power, but it would let you continue to operate. I liked mining with your pool, I was doing quite well.
That way maybe you can operate in the short term as a private pool using trusted participants.
The reason I do not suggest that you allow ALL miners that have been working to get the address is that quite likely, your attackers have been mining the pools somewhat to ensure they were functionally down.
Soooo...
Basically, you have a problem with public addresses for your pool.
If only you could ensure that no one knew how to find your pool unless they had trust... you could just use a static IP and have people mine there.
Here is one REALLY good litmus to determine whether or not a user should have trust... hashing.
If you pull from your DB of users, those who have hashed over a certain amount in the last couple weeks for instance... you could tell with a degree of certainty that these are all trusted people.
So... then you email all those users (I would be one of these people)...
Just email a private ip for the server to those users... or perhaps a domain name whatever... just something you don't post on here.
Sure, you'll lose a lot of hashing power, but it would let you continue to operate. I liked mining with your pool, I was doing quite well.
That way maybe you can operate in the short term as a private pool using trusted participants.
The reason I do not suggest that you allow ALL miners that have been working to get the address is that quite likely, your attackers have been mining the pools somewhat to ensure they were functionally down.
And, if the bot net owner has an actual miner or two of their own? What then?
^ This.
Also, the internet's reputation for keeping secrets is "not too good". *snicker*
Jump to: