You will need to download the new build before block 150,000 if you are running older than 0.3.25.4, or block 160,000 if you are running 0.3.25.4 itself (this is reported as 32504 in the 'version' field of the 'getinfo' RPC call in the command line client. Latest version is 32506).

I've released source and windows binaries for i0coin version 32506 at http://i0coin.bitparking.com/. This version  backports a bunch of fixes from recent bitcoin versions. The most important change however is it enables merged mining as a auxiliary chain on block 160,000. This is a required upgrade before block 160,000, otherwise you'll be left on the wrong side of a fork. This completes the set of bug fixes and merge mining enabling I set out to do so will hopefully be the last 'required upgrade', except for emergency bug fixes.

Hopefully with merged mining, and a stronger hash rate, exchanges and merchants can have some confidence in the coin.

I've tested merge mining bitcoin as the primary chain (using namecoin patches for getworkaux implementation), with i0coin and namecoin as auxiliary chains and all three chains merge mined producing blocks (on testnet for the chains).

All nodes broadcast addresses, it's trivial to collect a list of most connectable nodes on the network. Even with IRC disabled. You can then test each of these for an open JSON-RPC port with the default password. It's possible people are actively doing that.

It'd be interesting to analyse the two chains and see if any transactions were changed.

Yes, I saw your request for a drop to the reward. I won't be changing i0coin since this changes the value of existing held coins. It would mean i0coin would effectively be a new coin with a large 'premine' given to people who mined previously. My plan was to fix i0coin bugs, implement merged mining, but leave the generation rate, transaction fees, and values as they are since they are what gives a coin variant its identity. Plus I'd like to avoid the claims of arbitrary changing of values by a 'coin dictator'.

For ixcoin you should contact the coin creator with your idea of dropping the rate. If they agree I'd be willing to provide the patches, a pool, etc. I'd be interested in seeing what a slower generation coin does. Current coins seem to have more coins available than people need to use since their is very little non-trading usage of them. Since ixcoin already has a premine and a 'controller' it may not be so bad to change things.

Now that merge mining exists a possibly better approach for these "lets change a coin's features" requests is to create a new chain starting with no premine with the new features. Merge mine it with existing coins. Provide an exchange to trade between new coin and old coin, and see how they go.

If you have existing i0coins they will remain usable. This is not creating a new chain like SC 2 did to SC 1. It's operating from the existing blockchain.

See my reply to a similar question. I haven't yet pushed the version that enables merged mining so it's unlikely that the chain will get any great amount of hash power until that goes through. I'll do that in a day or two, probably switching on at 160,000. I'm currently backporting a number of bitcoin bug fixes that have been done since the original i0coin was released.

It's possible to do an exchange earlier with some form of auto-checkpointing mechanism but that centralizes things around the exchange somewhat (ie. the exchange has control of what blockchain is the 'real' fork). I would imagine most people would be against that.

The bitparking i0coin exchange was the victim of a >51% attack on the chain whereby the attacker would deposit, trade for bitcoins and then release a fork of the chain with the deposit transaction invalidated. This is why I closed the exchange. The ixcoin exchange was never attacked (to my knowledge) but I closed it as well since it also had a low hash rate and could suffer a similar attack.

From what I remember the  threatened attacks at the time were:

• Namecoin had a low hash rate. The attacker had >51% of the rate. use the 'timewarp/zeitgeist' exploit that ArtForZ discovered on the GeistGeld chain to mine blocks at low difficulty to obtain a large number of coins quickly.
• With >51% of the hash rate, rewrite the namecoin blockchain since there was no recent checkpoint at the time.
• The attacker claimed to know of an exploit involving merged mining that would enable them to 'leapfrog' checkpoints and rewrite the chain with a hash rate less than 50%.

What version of wxWidgets are you using? 2.9,1 exhibits that problem I think. Try 2.9.2.

Sent: f8a57d9b3c54c15ac3900b3ce56b0dbfa498cbc8289ee5436fc29acee83ef085

I pushed a fix to the git repository just now for this. Let me know if it works for you.

Merged mining should work fine on Windows. Use the windows binaries from http://i0pool.bitparking.com and start i0coin.exe with the "-server" command line option, or run the non-gui version i0coind.exe instead. Install Python for windows and use that to run the merged mining proxy, same as the linux command to run it.

Ok, I have a backup of the ixcoin bitparking bitcoin wallet - I'm downloading the blockchain now to see if that address exists and the coins arrived. Is 1Eks95X2LozPJSfY7Zi5DRT66vdE7mUzLt an address owned by you? It's the change address from the transaction and can send the 80 btc back to that. Please confirm if you own that address and I'll follow up if I own the 80 btc address.

The ixcoin exchange closed, the server instance deleted, a month ago. The wallet no longer exists.

A new version, 32504, with source and windows binaries is available at http://i0coin.bitparking.com. This version has the following changes:

* Add a checkpoint at block 131,130
* Merge patch from bitcoin to fix issues with database writes in the presence of lots of transactions
* Add merged mining support, ported from the namecoin implementation

The database writes patch fixes an issue that came up when the solidcoin 1 chain was under pressure from specially crafted transactions. I cherry-picked the bitcoin fix for the problem.

The merged mining code pulls in the changes I made to enable merged mining. I haven't activated support for i0coin as an auxiliary chain yet as this requires forking the block chain. After a bit more testing I'll pick a block number to activate and provide another update. In the meantime you can test this on the testnet, or use it as a primary chain to mine namecoins at the same time on the main net. See this post for how to do that.

I've updated the 'master' branch of github to version 32504 which includes the merged mining code. With this you can use i0coin as a primary merge mining chain. This allows mining namecoins and i0coins at the same time (namecoin as the auxiliary chain). Once it's been tested for a bit longer I'll enable a switch on block for support for i0coin as a auxiliary chain. That will enable mining bitcoins and i0coins at the same time.

To mine i0coins and namecoins, make sure i0coind and namecoind are running (or the GUI versions with the 'server' option enabled). Now run 'merged-mine-proxy' from the 'contrib' subdirectory of the source like so:


Replace  the username and passwords with those from the namecoin and i0coin .conf files. Now point your miner to port 9332 with any username and password. Mining will start with i0coins and namecoins being mined at the same time. Output will look like:

Awesome, thanks, much appreciated!

I will probably do something if another exchange doesn't. Whether it's the old exchange, or something a little different, I'm not sure yet. If it was the old exchange it'd require merge mining to be active, and for a healthy hash rate distribution.