A quick search produced no information on these coins with regards to where to get source, clients, how merge mining capable they are (chain id's etc). Do you have any further details? Where are they used?

Thanks, I'll do some work on longpolling efficiency. Part of the problem is longpolls are so often with the number of chains being mined.

Is there any interest in additional user stats? If so, what sort of stats? Or a leaderboard of users?

Are you still getting them or was it just for a short period of time? What does cgminer say the longpoll URL is? Try the http://mmrpc.bitparking.com:80/ URL for the miner - that uses a port 80 longpoller too and may help identify if it is a firewall issue.

They proved they were the owner of an address that was used to mine a large number of LTC coins, associated with a large miner in this thread.

Without source it'd be difficult to "shutdown" RealCoin since you have to use their close source binary to mine. You can't modify it to do a "Luke-Jr attack" where you use your >51% power to reject all blocks but your own, or to double spend. You can mine most of the coins of course and cause difficulty that way though.

Pool is back up now. There appears to have been a kernel panic that shut it down as a result of something namecoind related. I'm looking into it what caused that.

Pool is back up now. There appears to have been a kernel panic that shut it down as a result of something namecoind related. I'm looking into it.

Down for me too. Waiting to hear back from the company hosting the machine.

btc is only able to be used as a 'parent' chain. It can't be an auxiliary chain. It requires a block chain fork for a chain to be changed to support use as an auxiliary chain.

I tried this briefly with mmpool to see how it would work. Unfortunately 10 second longpolls means every user of the mmpool would be constantly longpolling. Many would probably not get the longpoll message before another one went out. Without sending the longpoll to users (ie. trying to hide the fact that p2pool was being used) would result in a large number of stales.

Block 162209 is shown as P2Pool but it was the bitparking mmpool. You can confirm this with the IP you have being that of the mmpool server. There's a few others with that IP shown as P2Pool as well.

P2Pool as a 10 second share time doesn't it? If this means a traditional pool would have to expose 10 second longpolls to its clients I don't think it'd work very well.

You have to register a new name, and enter our addresses along with a devcoin address. If you use the same addresses for the other coins as the old account I'll, at some point, combine the values so you won't lose 'dust' in the old account. Hopefully I'll have that implemented some time this weekend.

I find this pretty scary. It may be "worse case" but when worse case happens by someone mining a single block and the result is a drop in the network hash rate by almost 50% and people lose money, that seems non-optimal. Depending on the make up of the pools that support it it could push one of them over 50%.

Note that I'm not opposing the new feature being introduced, I'm concerned about the bad things that seem possible when it happens. Would it be possible to push out a client first that activates some far time in the future at a particular block number when it's expected a larger number of clients would have updated.

You're right, it's unlikely anyone will accidentally do it. But I can guarantee there are malicious people around just itching to cause a bit of havoc in bitcoin. It would be best to plan for the case of "it will happen that someone will mine a block" rather than "I don't think anyone would waste time to".

There was no attack that I'm aware of from BTCGuild or anyone on i0c other than the double spend attack on the exchange much later in the chains history. Whoever did that is a mystery, other than knowing the i0coin addresses that hold the funds. i0coin's issue was broken difficulty adjustment code that used 'real world' time. ArtForZ actually provided the fix for this so the chain could continue.

mmpool has 70 Ghash mining i0coin. Transactions are going through and blocks are being processed so the chain is not dead. This is different from CLC whereby Luke was not allowing any other blocks at all.

Unfortunately removing MM results in the chain getting owned by someone else when the hash rate drops. Another fun idea is to make mining blocks cost coins, rather than gain them. Eventually the merge miners will run out of money and can't mine blocks anymore. Solving the problem of no one wanting to mine at that point is an exercise for the reader

Yes, it's a good idea. Currently I adjust balances immediately on receiving a share so can't identify earnings in a 24 hour period easily. I can show number of shares in a 24 hour period without too much difficulty since I already keep that information. I'll look at adding the earnings feature though.

Do nodes automagically update to these? Or is some manual work required?

Mining is available on port 80 (standard HTTP port) by using the server mmrpc.bitparking.com. So instead of using http://mmpool.bitparking.com:15098, just use http://mmrpc.bitparking.com. This is slightly less efficient than the 15098 port in that internally it redirects to that but it shouldn't be noticeable.