I am in, well done....

+1 vote for this nice coin. 204-205

I want to get some F-IPO ENRG.   

Back to cryptoworld very soon.
The forum seems unfamiliar for me.
I try to find a new start to get me invovled in the cryptoworld again.
But it's hard.
The Communitycoin provided me a chance to experience.  
Also, I think the new things COMM included are encouraged.
I'd like to apply and get invovled.
It's my honor to do the promotion following your all guys.

Congratulations to you. I want to see more about it. And I'm not sure if a old guy like me can get some love.
The idea of free and fair distribution is fantasitic. I will pay my attention on it.

Gained about 1 Mhash (431->432) from the 7th version to todays new version on my 5870 (950/315).

Bumped my hash rate from about 428 to 431 (3 MHash/s or 0.0696%), although previously I was using a customized kernel that has some of the same changes you've made so this increase is not representative.

Edit: XFX 5870 @ 950/315

Seriously just get 7-zip and remove the rest, its free, open source and its default format .7z is probably the most effective lossless compression format commonly used.

This is shown up quite well if you run something like Folding or Seti on your GPU, you will notice a lot more invalid work showing up than you do using the CPU variant and has far as I am aware work for these two does not expire within any reasonable length of time unlike bitcoin so these are actually invalid results and not just "stale".

Its back, jine was fiddling with bitcoind.

My 5870 (950/315) went from 418 -> 428 Mhash an increase of 10 Mhash or about 2.5%.

I think you might have the wrong idea of IRC there, basically there exist 100 channels on freenode(?) named something like #bitcoin-(1-99) or something like that; when you start your bitcoin client it joins one of these channels at random and collects a list of initial peers for it connect to - this process is known as Bootstrapping. Once it has this initial list is doesn't necessarily need to talk to IRC again since it can then fetch new peers via its peers and so and and so forth, the slight downside to collecting the stats like this is that you can disable IRC bootstrapping in the bitcoin.conf and either enable a static DNS bootstrap (aka fetch a list of peers from a predetermined address) or simply manually add nodes/connect directly to someone.

Edit: To more accurately answer the OP if you wanted to only find a list of addresses that contained at least some currency or have had some kind of transactions in the last x days this could be done by analysis of the block chain, blockexplorer would probably be a good place to start.

The most accurate way I can think of off the top of my head would be to monitor the bootstrapping IRC channels for unique IP addresses over a given period - this wouldn't be 100% accurate however.

Very mature move, it also has the side effect of preventing panic trading while this all clears out.

Yeah difficulty went up 2 days ago from about 500k to 876,954.493514

Possible when LP pushed a new block through, LP is pushes when the "network" solves a block, so about every 10 minutes, where as bitcoins.lc will solve a block every couple of hours right now.

If the card is overclocked to the point of being unstable then yes, since it will generate a hash it thinks is correct but if it makes an error it will turn rejected since the proof of work will fail.

Thats normal, your miner is in the middle of a getwork when the LP comes in and sometimes you will find a share at or around the same time as the LP, causing you to submit it and it becomes stale. The lower your latency to the pool the less of these forms of stales you will get (and to a greater extent the better peered the bitcoind is behind the pool).

This sounds like an issue with your Long Polling support, are you running an older miner that doesn't support it, or a version of Phoenix that isn't 1.48+ (they had a serious LP issue)?

Jine has been doing some work on the database which may be the cause of this, but the work is needed to allow the database to scale properly into the future.