Can't you change the wallet used by your pool?

mmpool has mined a few. It gets about 15-20 out of the 120 immature generations. I assume most of the rest is Eligius.

I've adjusted the fees for the pool based on current stale and orphan rates down to 2.5% for all coins. Previously it was 5% for bitcoin/namecoin/devcoin and 7.5% for i0coin and ixcoin. Current PPS rates are:

• bitcoin 0.00003898
• devcoin 0.08386213
• i0coin   0.00844560
• ixcoin 0.00344397
• namecoin 0.00010509

Note these change based on difficulty so check mmpool for the up to date rates.

I've adjusted the fees for the pool based on current stale and orphan rates down to 2.5%. Previously it was 5% for bitcoin/namecoin/devcoin and 7.5% for i0coin and ixcoin.

mmpool doesn't allow changing of addresses at all. You have to re-register with new addresses. Registration is light weight in that you only need a username, no password or email address, so it's not too much of a burden. I did it this way to avoid the "hack account, change address" which seems to occur occasionally in places.

You could consider making the link to vircurex one without a referral id and follow it with something like "and if you use this link, you get reduced trading fees" or something. It'd look less spammy.

Devcoin's difficulty adjusts fast! 41,945 and rising.

Websites can go down or be DOS'd. I used the P2P messaging to avoid this, but if that isn't important then yes, a website URL is an option.

There's a thread someone started for this but I can't edit it for hash rate or features so I've started this one. The Bitparking Merged Mining Pool mines Bitcoin, Namecoin. IXcoin and Devcoin. Features of the pool:

• URL: http://mmpool.bitparking.com
• DGM at 1.5% fee
• Payout on found blocks enabled after only a few confirmations - no waiting for the full 120
• Miners can select difficulty level (see below)
• Merge Mining Bitcoin, Namecoin, ixcoin and devcoin
• Stratum support on stratum+tcp://mmpool.bitparking.com:3333
• Simple registration. Just set your username, coin addresses and mine.
• Getwork mining on port 80 available by pointing your miner to http://mmrpc.bitparking.com instead of http://mmpool.bitparking.com:15098
• Mining stats.
• IRC Channel: #mmpool on freenode IRC network
• Run by the operator of the first public bitcoin mining pool.

I've kept everything deliberately sparse. Coin addresses can't be edited once created (by design) but you can register a new username anytime with new addresses. This is to prevent unauthorized people modifying addresses.

Large hashrate miners can choose to set their own difficulty to mine at. To do this set your password to be "d=8" to mine at difficulty 8. Change '8' to any number less than 60,000.

One of the issues with low hash rate chains is dealing with having to add checkpoints regularly and getting users to upgrade to keep the network secure. Here's a work-in-progress proof of concept of 'dynamic checkpoints': https://github.com/doublec/i0coin/tree/dynamic_checkpoints

This provides the ability for a trusted entity with a key to send a checkpoint out to nodes. These 'checkpoint' messages are passed to all nodes. Nodes that are operating in 'trust' mode will check the signature on the message and if it is from the trusted entity it will install the checkpoint. No need to upgrade the software.

The patch provides:

- All nodes relay the "checkpoint" messages
- Only nodes with the "-trust" command line argument will check the signature and install the checkpoint
- Nodes can add "-trustkey=foo" arguments where "foo" is an address to override the default key and trust some other entity for checkpoints
- a JSON-RPC command to sign and send checkpoint messages
- Only checkpoints higher than existing checkpoints can be added so no chain rollback can be done.

At least the following should be added:

- a JSON-RPC command to return the latest checkpoint. Nodes like exchanges could use this to know for certain a chain won't rollback past a point. This could be used to feel confident to accept large deposits.
- Flood control to deal with "checkpoint" messages being sent around

Thoughts on this model? it centralizes the aspect of checkpoints but provides the ability for nodes to override. And isn't different to a trusted developer releasing versions with checkpoints. Maybe only have it enabled when the chain hash rate is low?

Note the patch is an experiment and shouldn't be used in production right now.

CLC is dead - I'm no longer allowing addresses to be registered. I paid out all existing CLC shares at a BTC rate of 0.0002 per CLC.

What I posted just means it's likely Eligius is mining alternate chains, nothing more. It could just be namecoin for example with weird merkle tree sizing. Someone more motivated would have to dig further into the chains if they wanted to find anything else out.

Ok, thanks. If it becomes an issue I'll do zero fee and have my pool take those transactions.

It can be shown that the Eligius pool is likely multiple block chains by looking at the coinbase of the generated bitcoin transactions. Here's a coinbase from an Eligius  bitcoin block that was used for namecoin only merge mining:


The details of the coinbase are available in the merged mining specification. From this you can see that the number of entries in the aux merkle tree is 1. This means up to 1 other chain is being mined. That's probably namecoin. You can look up the hash of the namecoin block. It's hash 4976cbf9003c0705e29e581038d3ddbe260a5d324c2b17b24779b6ca48c4f832 or  block 36067.

Now look at a slightly later block. Say 160499:


The aux merkle tree size is 4. So up to four other alt chains are being mined. Why the increase if it's only namecoin being mined? Also note that the hash in the coinbase no longer corresponds to a namecoin block. This is another sign multiple chains are being mined. This is during the period that i0coin and ixcoin hash rates increased.

Now a more recent block:

The aux merkle tree size here is 8. Why the increase? Coiled Coin and Devcoin are both active at this time and would have required the aux merkle size to be upped. I got the Eligius found blocks from here.

Pools payout the total generation amount based on shares submitted. So people with lower hash rates get lower amounts. With mmpool it's PPS so they get (at the moment) 0.29 devcoins per share or so.

Any thoughts on how to deal with fees for devcoin withdrawals in pools? Looks like I'll have to set a much larger minimum withdrawal for devcoin since I can't judge how much the fees are. I'm getting people withdrawing 2 devcoin and I'm paying a 6 devcoin fee for it.

What address was this sent to for me? I haven't received this or the recent devcoin bounty you sent in the address I thought I was using.

edit: disregard, I received them now.

Devcoin merge mining is active at bitparking now.

Devcoin merge mining is active on bitparking now.

You can use a bitcoin address created from your own bitcoin wallet. Use that in the devcoin address field. At some later time when you want to claim the devcoin's you can import the private key for the address from bitcoin into devcoin. Their addresses are the same format.