Bitcoin Forum
November 12, 2024, 11:06:59 AM *
News: Check out the artwork 1Dq created to commemorate this forum's 15th anniversary
 
   Home   Help Search Login Register More  
Pages: « 1 2 [3]  All
  Print  
Author Topic: Slush and his relation to DDoS attackers  (Read 4957 times)
nodemaster
Full Member
***
Offline Offline

Activity: 176
Merit: 100



View Profile WWW
October 27, 2011, 08:11:13 PM
 #41

No that would mean he was lying about how hard it was to setup as he already had it done, totally eliminating the excuse he and others use for having done it in the dark without anyone's knowledge when he was doing it on the real chain.

This starts to become boring... Linking the relevant information for you: https://bitcointalk.org/index.php?topic=42667.msg566146#msg566146

Yes, it was tested. Yes the binaries were ready at this time. Yes we already mined a bunch on testnet. BTC testnet had difficulty of about 500 something and NMC testnet difficulty was about 5 something. But no one has done merged mining on production net before NMC block 19500. It was impossible. Even if he would have done it his NMC would have been invalidated or ophaned. Furthermore no one had tested merged mining on a 2 THash/s pool infrastructure optimized for only one blockchain. If you have an optimized server it's not like installing an additional APP and there we go: "Merged mining is ready!". You have to recalibrate and rebalance your whole infrastructure.

Honestly. I think most guys are not here to understand what really happened but want to spin some weird conspiracy theory. For that reason I'll unsubscribe this thread. Bye  Kiss

Edit: Yeah sorry. I messed this up. It's late. Merged mining started on block 19200. Perhaps I should keep subscribed to that thread to see which spin it gets due to me revoking different information  Grin
Littleshop
Legendary
*
Offline Offline

Activity: 1386
Merit: 1004



View Profile WWW
October 27, 2011, 11:24:25 PM
 #42



Really you see nothing wrong in the way he did it screwing over everyone else who as I have said did it in the open allowing everyone a fair chance to do the merged. Well all you slush ass kissers can continue on your merry way then till the next time he pulls something underhanded then you can kiss it some more.. You know the only benefit that those of us who supported the merged mining had was the extra BTC we could make from the NMC and like the little scumbag he is he schemed them up for his pool and his benefit screwing us over. We never had the chance to mine at that big pool and get any of that coin as we were never informed the scam was on until people started asking what the hell is going on here.

Do people need to inform you first before they turn on new powerful rigs?  Do people need to inform you first before they start undercutting or out performing the competition?

Raoul Duke
aka psy
Legendary
*
Offline Offline

Activity: 1358
Merit: 1002



View Profile
October 27, 2011, 11:35:38 PM
 #43

slush
Legendary
*
Offline Offline

Activity: 1386
Merit: 1097



View Profile WWW
October 28, 2011, 12:22:57 AM
 #44

Around 5% of population is mentally retarted. Please don't waste your valuable time for responses to somebody with irrational arguments. Stop feed the troll.

MysteryMiner
Legendary
*
Offline Offline

Activity: 1512
Merit: 1049


Death to enemies!


View Profile
October 28, 2011, 01:14:36 AM
 #45

Speaking of scamcoins or namecoins, the Polmine also started to mine namecoins without user approval. One nice day my workers were switched from pure Bitcoin to Bitcoin+Scamcoin.

And yeah, the DDoS! I contacted Slush to figure out more about the ddos, but the conversation was short. I was interested in type of DDoS to sort out who and more important why is ddosing the pools. I was told that the attack is syn flood and after that I got no reply.

bc1q59y5jp2rrwgxuekc8kjk6s8k2es73uawprre4j
slush
Legendary
*
Offline Offline

Activity: 1386
Merit: 1097



View Profile WWW
October 28, 2011, 01:25:39 AM
 #46

I was told that the attack is syn flood and after that I got no reply.

I don't have more info than I provided you. Linode don't collect any useful information, they're absolutely not prepared for such attacks (everything they can do is null-route IP). I'm even not sure it was SYN flood, it's only my guess because I had SYN flood attacks (but less intensive) before. And sorry for no response, many people asked me to similar things in PM and I probably skipped it.

MysteryMiner
Legendary
*
Offline Offline

Activity: 1512
Merit: 1049


Death to enemies!


View Profile
October 28, 2011, 01:40:14 AM
 #47

It's OK, I already found more interesting pastime than trying to figure out who is campaining against pools. The raw network dump, even few MB would be the best to help determine what bnet software is causing that, if you don't mind some accidential password in plaintext getting into my hands. the LOIC, Zeus, DK, they all have some characteristics that set them apart. Some more capable of them are limited to few persons controlling them.

bc1q59y5jp2rrwgxuekc8kjk6s8k2es73uawprre4j
slush
Legendary
*
Offline Offline

Activity: 1386
Merit: 1097



View Profile WWW
October 28, 2011, 01:44:32 AM
 #48

Linode VPS simply died when attack started, so I had no chance to dump a single byte. However I think new server will be capable to dump at least something (before admin realize there's attack and null-route that IP :-) ), so maybe then...

MysteryMiner
Legendary
*
Offline Offline

Activity: 1512
Merit: 1049


Death to enemies!


View Profile
October 28, 2011, 02:24:09 AM
 #49

Linode VPS simply died when attack started
Man, that's one heck of a nurse!

bc1q59y5jp2rrwgxuekc8kjk6s8k2es73uawprre4j
AniceInovation
Donator
Sr. Member
*
Offline Offline

Activity: 446
Merit: 262


Interesting.


View Profile
October 28, 2011, 05:37:00 AM
 #50

They wanted to be noticed so that they could also get into the bandwagon, obviously.
Next time, keep an eye on the forums.
Pages: « 1 2 [3]  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!