... all the way to block 4699548 or wherever its currently at
https://chainz.cryptoid.info/ioc/ Block height is approx 5573412 Apologies this is a different coin called io as in eye ooooohhhhhh coin as it is easy to get them mixed up with one another. Pity it wasn't called zerocoin or just 0coin and it wouldn't be so easy to get confused with other coins.

Some interesting links below for anyone who likes a bit of history about
izerocoin.
https://bitcointalk.org/index.php?action=profile;u=140234https://bitcointalk.org/index.php?topic=276483.0 https://bitcointalk.org/index.php?topic=268228.0I0coin Resurrection Official Website
https://i0coin.snel.it/ https://github.com/rsnel/i0coin/http://blog.zorinaq.com/bitcoin-inspires-copycats-first-tangible-good-sold-for-i0coins/For an inexplicable reason, i0coin, although still very much an underground cryptocurrency with a high risk of failure, appears to have picked up a small number of supporters. Initially, it was forked by kr105, and later modified and enhanced by fusebox and ArtForz who had to reset the network difficulty by consensus after it increased very quickly, scaring its miners away. This is a failure mode that can theoretically affect Bitcoin too, but its probability decreases as its user base diversity and size increases.
What is killing I0coin? And why doesn't it kill NMC,IXC,DVC? (an answer)
https://bitcointalk.org/index.php?topic=224744.msg2830598#msg2830598I0coin is killed by:
I0coin by keeping all auxpow's in memory
slow adoption by regular pools
P2Pool
high blockrate
Why?
I0Coin stores all auxpows in memory, because auxpows are included in CBlockHeader and ALL CBlockHeaders are stored in memory, Bitcoin up to at least v0.8.3 does this also.
Due to normal pools having little support for I0Coin (as opposed to eg. NMC), most of the mining is done in P2Pool
P2Pool has very large (8kB as opposed to 200B) coinbase transactions (each auxpow has a copy of the full coinbase transaction in the bitcoin block with which it is associated)
Due to the high blockrate, i0coin's memory usage grew faster than namecoin, ixcoin, devcoin GOTO bullet 2 and repeat ad infinitum
Endresult: i0coin's memory usage grows by at least 8kB per block, which is 8kB*60/1.5*24*365 = 2.7GB per year... Sad
Solution:
Port I0coin to v0.8.3. I did that
https://github.com/rsnel/i0coin/tree/i0coin-0.8.x (I started with doublec's v32509 and merged sucessively higher versions of bitcoin into it). It seems to work fine. (it can do transactions, it can mine blocks that get accepted eg 01f017f6e86c5de539b0137677e6d096bbd2b05d9859c4c25c14c73579644dc8, which is a nVersion=2 block because it includes its nHeight in the coinbase script) On its own, this port uses about 500MB more memory than v32509. (I hoped to solve the problem by doing this port, but that didn't work...)
Then I proceded by, and I agree that this is a bit dirty, just not storing auxpows. This breaks two things:
response to getheaders request doest not return auxpow part of header (not that bad, because the Satoshi client never issues getheaders requests)
CBlockIndex:CheckIndex, it just returns true because it doesn't have access to auxpow (see comment in source)
I implemented this in branch dirty-trick. Please try it out, and run this version besides your own i0coind (it uses about 321MB) and keep an eye on it.
Better solution:
Retrieve auxpow's from disk in the two problem cases.
Further work:
compile on other os's, only tested "make -f makefile.unix i0coind"
fix logo's in qt client
stabilize/test 0.8.3 port
when to enable BIP30?
much much more
irc seeding is removed in bitcoin, include good seednodes and setup DNSSeed for i0coin
Greetings,
Rik.
https://bitcointalk.org/index.php?topic=224744.0For those of you who don't know, i0coin was one of the older alternate cryptos that had a decent backing before being abandoned by it's developer. Among other issues, a crippling memory leak eventually made the client unusable and the coin died.
I'm currently in the process of fixing all these issues and bringing this coin back to life. To that end, I need people who still have the i0coin blockchain to help me beta test the new client. Inquire if interested!
Disclaimer: I own zero i0coins so this project is at the low end of my priorities list.
https://bitcointalk.org/index.php?topic=224744.msg2363663#msg2363663Huh? Forking the chain is a worse bug than simply using a lot of RAM. Geistgeld uses a lot of RAM too. It might even really just be due to all the dust transactions, since all available to be spent all live in RAM don't they? So most likely the massive amount of dust causes a massive amount of RAM to be used. I think dust transctions may have already been dis-allowed so maybe just paying people to consolidate all their "dust" could help decrease the size of the in-RAM txout set.
-MarkM-
Quote from: Hazard on June 04, 2013, 01:08:31 AM
Merged mining will come, it's just not my primary concern right now. I'm currently trying to fix a coin that I don't even have the blockchain for Cheesy I'm sure you see how that could be problematic.

YOu cannot do profiling looking for memory leaks etc if you cannot run the client, so you just need the current client and blockchain and a debugger / profiler, no hard fork no new bitcoin code just find the damn bug and fix it.
But better might be to help get the merged-mining.patch applied cleanly to the latest bitcoin code.
Then all the merged mined coins, not only I0Coin, can upgrade to that.
Fixing some ancient version is pretty much a waste of time since whatever you end up with will be obsolete almost as soon as the applying of the patches to latest bitcoin is complete, because once that happens I0Coin, IXCoin, CoiLedCoin, GeistGeld, GRouPcoin, DeVCoin, heck maybe even NaMeCoin will all be upgraded using that so will all be up to date properly.
Whatever bug there may be evidently is in no other coin except possibly GeistGeld, and certainly not in the latest bitcoin code, so is going to go away anyway as soon as this "Mergecoin" repo is ready.
-MarkM-
Maybe you can take over ixcoin too

wiked1 looking for Vlad2Vlad to declare crypto jihad on his ass
