Please update for my pool:
SSL: yes
wallet address change security features: yes
share validation waiting period: 100 blocks
Decimal places paid out: 8

Thanks.

bitcoincharts - probably most accurate data, they ask old mtgox's api (polling)
sierrachart - uses bitcoincharts data, but bitcoinchart is serving delayed data (20 min?). So using websocket (if it works) is definitely better solution.
mtgoxlive - because websocket is broken?

Yesterday I downloaded blockchain on 10Gbit line, few Xeon CPUs and SSD raid. It took only one hour to complete :-).

I followed iostat, iftop and htop and it definitely looks that the biggest issue is waiting on data from network. Sometimes it processed 500 blocks per second, but then suddently dropped connection to peer and it took long time (minutes?) to recover and continue downloading.

No, it's 0.3 for pretty long time. It adds MtGox multicurrency support and also use better (more stable) websocket library. Follow link bellow...

Yes, simply use -w option to switch off websocket, it will use only bitcoincharts.com polling. Actually that's the reason why I though mtgox socket is working; I overlooked that I'm using -w already .

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...

Works for me (however it felt down few times during last day).

Edit: You're right, it's down.

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.

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.

OK, it's only >estimated< reward; it's calculated from slightly outdated info (becuase of caching). I'll watch how rewards from this block will be finally distributed and if there will be something weird, I'll fix it. Thanks for pointing me to that.

Everything seems to be ok. It's "only" 9.5mil shares, so nothing impossible. For example, deepbit had 10+ mil shares in one round today, too.

Ok, you win . Have a nice day .

Tell me, please - why are you lying?

1) I have no responsibility to announce YOU that pool is mining namecoin for *pool members*. People who were mining on the pool were collecting namecoins since first MM block.

2) I didn't announced it *officially* before, because I wasn't sure it will work. And there were really scalability issues, so announce "pool is mining namecoins" and then turn off merged mining would be much worse for my reputation. However people around namecoins DID know that I'm preparing it many days before MM launch. You looks so interested in namecoin, I'm curious why you wasn't on IRC when we spoke about it. However, it's YOUR fault, not mine.

3) I announce merged mining on forum, but giveaway was something like *week* later. You had hell long time to jump to my pool and earn some bucks while there was low difficulty.

Finally - I don't understand this 'affair' completely. It's my pool, my pool members, I gave them all mined namecoins and it wasn't because of some weird conspiracy theory about DDoS (lol). So what are you talking about?

One guy reported me that he lost some coins, because he didn't confirm new wallet fast enough while his reward already crossed over threshold. To prevent this stupid issue, pool won't process payouts for users who have pending wallet change in progress.

To enable payouts again, you need to cancel request or confirm new wallet.

Now I see the problem guiminer isn't following HTTP redirects. I reported it to Kiv, hope he will release fix soon :-).

Hello, looks like retrieving account balance for my pool does not work. Can you please take a look, Kiv? Yesterday I added two variables 'hashrate' and 'rating', but everything should be backward compatible if you parse it as standard JSON.

Edit: Oh, I see the problem. It's unrelated to changes in json, but website is forcing HTTPS and you don't handle redirection correctly:

Hm, I see an error too. Ok, thanks, I'll report it to Kiv (GUIMiner author).

Did you filled your API token in GUIminer?

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.

Yes, of course. Everything you need is to be the God :-).

I'm kidding. "Reverse pool hopping" does not work, because nobody knows when round will finish (in the oposite everybody knows when round begin, which is the problem with standard proportional method).