Oh right. What's happening is those are blocks mined by someone else, but you are the recipient of the 45,000 share for that block. If you look at the block in the explorer it'll be your own devcoin address from the receivers.csv there. They appear as generates and are still immature. I guess that has the potential to confuse your pool somewhat, assuming that's devcoind output from your pool's daemon.

Yeah, something's wrong. those block amounts don't seem right.

Are you sure you're not on a fork? Check your hash against: http://64.244.102.88:2750/block/0000000000008dad8f4ae8910a759b81de4e9f84bcb74d75ad6052ef4d77dac7

Why are you asking me if I have plans to merge mine currencies I'm already merge mining?

Try mmrpc.bitparking.com, port 80. I've just set this up now so it may take a bit for the dns to propogate. Let me know how it goes. That port is for miners only and forwards internally to port 15098 so may be slightly less efficient due to that additional latency.

Email me at the address on the mmpool site.

Below I'm explaining what an attacker could do with an attack similar to what happen with coiledcoin. I'm not suggesting this will actually happen.

Assume it's a pool with 350 or more Ghash. You can personally summon that much mining power to complete? You'd actually need to exceed what they have.

They don't need to invest money - it's free by merge mining bitcoins at the same time. There is no additional cost for a large miner to attack it. Changing difficulty doesn't matter. If they have >51% they then stop accepting other peoples blocks and continue to publish their chain containing only their blocks. Now they control what transactions can be included. If they stop allowing any transactions the chain is dead. No blocks and no transactions. And it's not costing the attacker anything - they're still earning bitcoins/namecoins/whatever while doing it. The only defence is to exceed their hash rate. Or to somehow identify and stop their blocks.

The coiled coin attack has shown how hard it will be for alt chains to survive without the good will of existing pools.

it can "break" the currency if the miner has greater than 51% and refuses to accept other miners blocks and refuses to include any transactions. Because they have >51% they always have the longest chain. No one else gets blocks, no transactions are allowed, so the chain is effectively dead. It's a pretty nifty example of the power of >51% hash rate.

Because he warned me he would. By attack I mean mine the chain with a huge hashrate, dump the coins and drive the price down as is happening with i0/ixcoin. Whether he still plans to or not I don't know. Since it's actually happening on other chains it's important to be prepared for it. My warning about 51% attacks is due to what happen to coiled coin. I don't know if he plans to do the same with devcoin but since it's happened to an existing chain it's important to have a plan for dealing with it. You don't want to find 2 hours into merge mining enabled that your chain is dead. Even if the plan is to ask him if he'll please not do it.

No worries, it's all a learning experience. I guess that will be the last alt chain for a while.

No, they are normal transactions. It looks like a lot due to the amounts being smallish but coming from addresses with large amounts and the change being the remaining large amount. As far as I'm aware Luke hasn't attacked devcoin.

All users that mined coiled coins on the mmpool have been compensated BTC at the rate of 0.0002 btc per coiled coin. This has been credited to your bitcoin balance. Sorry for the inconvenience of resetting your addresses for such a short lived chain.

Which information exactly? You can read the curledcoin thread for details on what happened there.

That's a pretty uncalled for comment. [thanks for removing the barb]. The only thing I know Luke-Jr to be doing with i0coin/ixcoin is mining them and selling them with the intent to crash the price . I know this because Luke told me in #namecoin IRC. [logs removed due to objection from luke]. I don't know anything about the bitparking pool clams. Luke has definitely not done anything to bitparking.

Please don't try to make it look like that situation was the same as the one here. I ran a stock standard pool that did nothing to change block propagation in any way. The situation here is a majority pool actively refusing other blocks and this is not the same.

I'm not sure what you're getting at. All I'm doing is giving advance warning that when merge mining activates you'll have a hostile pool with large hash rate destroying your chain. I'm not arguing about whether such a thing is moral or legal or anything. I'm just saying, you might want to be prepared. Like find 300 Ghash somewhere.

The pool is still mining, it'll just never get any blocks unless luke's pool gets below 50%.

Sure, but finding 300 Ghash of power to compete with his pool might be difficult. Do his users support him? I doubt they care.

Given that luke-jr seems to be on a crusade to destroy merge minable alternate chains (he recently attacked the coiledcoin chain), what plans does devcoin have to prevent this when it switches on?