Quote from: dreamwatcher on June 04, 2013, 04:40:02 PM

I would be willing to put up a block explorer, when an i0coin daemon (testing or release) is given to me that uses a reasonable amount of memory.

The state of the client/daemon now would require too much VPS memory for me to put on CCE.

Yeah, that's the thing... by that time, I wouldn't need one anymore. I'm trying to find out where a fork occurs in my blk0001.dat file. We're past one of the fork points which Hazard was able to find, since it happened at a specific block, but there is another fork (or a couple) before the merge-mining fork at 160000.

I can currently follow the bad fork (since I didn't update at the time until after I found myself forked off, so still have the orphaned blocks in my chain) but can't backtrack to find where it happened.

I had thought about taking the trimmed blk0001.dat file from the testing build, and re-importing it into the old daemon, to see how far it gets before it rejects my supposed-to-be-orphaned blocks, but it doesn't import well, and have had no success.

(Hazard is handling the code, I'm just doing testing)

-- Smoov