Topic: Slush and his relation to DDoS attackers - page 3. (Read 4969 times)

this is what you get from a strong btcg "supporter" to lazy to look for himself the real facts happened lately

Trollololol

Oh c'mon. What's your point? It's one thing to say slush should have done an opt-in beta as eleu suggested or to say it was a rash decision to post about some other pool having some correlation to the source of the DDoSes. Perhaps it was emotional and written with way too less sleep. We can talk about that and I guess the two persons in question already did that with the nessecary professionality. At least they are not mud-wrestling on the forum. However this are things you might criticize and all other may contribute to this discourse if you think its still nessecary.

But IMHO its something else to oppose slushs reputation and his integrity regarding payouts of his pool. It doesn't seem opportune to accuse someone of something which can be falsified with a look at the block explorer.

So then, without the NMC bounty, did you use BTC or cash to pay the Botnet OP to attack other pools in order to buy you enough time to be the first big pool to get merged mining completed and made public ?

While an opt-in beta system would've been the better route to go, I highly doubt slush ever intended to hide/keep the NMC that was generated.  Even if nobody noticed it beforehand, you can be damn sure once he announced merged mining on his pool people would've gone back to previous blocks he mined to check.


Quit trolling.

There's nothing like "secret merged mining", firstly learn how it works. Example of merged mining block on my pool: http://blockexplorer.com/rawblock/00000000000007f894490c7659ea6e257c75b51d067e78ba4adda05b07dbce27 You can see that coinbase is different (much longer, because cointains namecoin data) than block found without merged mining (deepbit): http://blockexplorer.com/rawblock/000000000000013b4c307a3b99f4bd7761c58349356f3fd64a1102ac513ab610

I must be an idiot to think that nobody will notice my pool is doing MM. Which is pretty strong evidence that you're wrong :-).

Also there are many people who had an information about planned merged mining. And also about my plan to give away all those coins to people. Mainly vinced (main namecoin developer), doublec, cosurgi, nodemaster. Fact that it wasn't published on this forum does not mean there was some 'conspiracy'. I was talking about it on namecoin IRC even before official merged mining started.

That's everything what I want to say.

Edit: I was talking about this ^ on the forum and IRC already, I didn't say anything new. I'm just sumarizing that because some people who don't follow this 'affair' may trust some troll post just because they don't know other facts.

I can report, that slush already told me that he is going to pay his members the merge mined NMC even before he had implemented merged mining. That was at times of BCXs upcoming 51% attack which never happened (http://dot-bit.org/forum/viewtopic.php?f=2&t=308). But of course you are right its only my word and i can not proof it. However, sorry to disapoint you, but there was someone else faster unveiling the fact that slush and me are working towards total world domination with all Bitcoin users being our evil minions (http://dot-bit.org/forum/viewtopic.php?p=2106#p2106). This is going to become a great conspiracy theory! Let me get my popcorn ready!

Nice troll.

I'm not sure if that is meant to be a joke, or a paranoid fantasy you should have kept to yourself.

Hi,


I think I have finally stumbled across enough concrete evidence using nothing but the deductive reasoning skills learned on this forum in the aftermath of the finger pointing at another Pool for it's so-called responsibility in the recent wave of DDoS attacks against competing pools.

Fortunately the timeline's speak for themselves and it will be difficult to argue the facts once provided.

Slush was recently caught mining NMC without the concent of his pool. Untill questioned, he had given no evidence that the NMC would be returned to his userbase, although once caught, he did one of the best back peddling routines I have ever witnessed on this forum, attributing 'Testing' to the reasoning behind his abuse of authority as a mining pool operator.

Here's where the situation becomes more of a chicken vs. egg scenario, due to attacks being ongoing.

There is strong evidence to support a claim that the secretly mined NMC that Slush aquired was to be used as a payoff to a Botnet OP to keep bitcoin.cz safe from attacks and once paid, the attacks would then be focused on other competing pools, funded by Slush himself.

Unfortunately, once this masterplan began falling apart at the seems, thanks to the tireless efforts of others in the NMC community (wondering where such a large amount of NMC could have been mined from) and their efforts to find the culprit, Slush was forced to rethink his strategy and come clean before official accusations were made - meaning the NMC that were to be used as an insurance policy, would now need to be redistributed back to the users who's resources were actually responsible for their generation/mining in the first place.

With no NMC bounty left to be paid to the Botnet OP, Slush was left to suffer a DDoS attack in conjunction with the other pools that he had initially wanted other attacks directed at in the process, but this was not all for nothing as it were, because during this downtime slush had re-thought his plan and decided to impliment official merged mining, to take advantage of the dire situation and make it work the best that he could...in the grand scheme of things.

Now, throw in the odd sad post, an attempt to further damage another pool by routing DNS traffic thier way....and one might just have enough time to re-work a pool so that he could be one of the first (PUBLIC) merged mining pools, while others were forced to deal with the attacks themselves.

Best,
bitlane.