Topic: [ANN] i0coin - Back from the dead - page 5. (Read 14918 times)

I'm fairly sure coinhunter runs the mcxnow exchange

I have a 1.25GB size blk0001.dat

i0coin.rar (898.0 MB)

Have not seen Lolcust for a long time after that Geld Geist coin.

They'll still be there.

Wait, what's going to happen to all the old i0coins?

PLEASE don't give it a new name Hazard 

Okay well if you do apply the merged mining patch to a version of bitcoin, please make a repo of just that.

That way all the coins can go ahead and update that far if they want to instead of having to wait for the patches to successfully get applied to the latest bitcoin, which is not as simple as applying them to the versions of bitcoin that still used Berkely DB.

-MarkM-

P.S. Sourceforge only got 1.1 gigs of the doti0coin.tgz but shows it on the list anyway even though that is broken. I am trying the sftp again.

SInce I fired up i0coin temporarily on my other server too you could try temporarily adding 198.154.60.183 to your addnodes, maybe with more nodes to get blocks from it will have more success getting blocks.

Correct.

Currently the plan is to just get the block chain to load under 0.7.2 by disabling block checking, and seeing if the memory leak issue is fixed (which it should be). Then I can move onto applying the merged mining patch and release it.

Welp, turns out I don't have the block chain :-/ Will this resurrected i0coin still run SHA256?

By latest I hope you mean 0.7.2

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-

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 I'm sure you see how that could be problematic.

Huh? 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-

So you are trying to 51% attack the i0coin network?

Or steal the name for some new coin?

Or what?

All the merged-mined blocks will not validate as valid if you don't have the merged mining patches.

If you update to very recent bitcoin though, I don't' think it bothers to validate anything prior to the last checkpoint, maybe?

So very-recent bitcoin code maybe might let you get away with having the real blockchain even though you cannot actually validate any of it prior to some checkpoint. Not actually sure about that though.

Someone actually wants a branch of I0Coin they cannot muster hashing power to actually secure due to it not being able to be merged mined?

-MarkM-

I'm aware. I'm setting up a hardfork. Hence why I require the blockchain.

You have to have the merged mining, the difference between being able to be merged mined as a secondary chain and not being able to be merged mined as a secondary chain is a breaking change, when first adding merged mining to a coin you need to schedule in advance a block number at which merged mining will be enabled, the blocks are different from there onward.

If you wanted to fork off a variant that no longer can be merged mined as a secondary chain you'd need to do the same, schedule a block number at which the block format that enables secondary chain ability is replaced with the old format the blocks used to have back before the merged mining was started.

So basically to base off of bitcoin you need a copy of bitcoin to which the merged-mining.patch has been applied. To base off some other coin you'd need to base it off of a coin that already has the ability to be merged mined as a secondary chain.

This is not a change a few constants "sed -i -e 's/bitcoin/scamcoin/g' -e 's/Bitcoin/Scamcoin/g' *" type of job, unless some existing coin that already can be secondary chain in a merge has already been updated to the version of bitcoin you are trying to update to...

-MarkM-

EDIT: I am uploading doti0coin.tgz to https://sourceforge.net/projects/galacticmilieu/files/ it will take a while as it IS large, but it includes everything so should just need download time, no CPU overhead nor the database overhead of building indexes and so on. It won't show on the page until the upload completes. It contains a dir called doti0coin, not .i0coin, so untarring it won't walk over any existing .i0coin dir

I always liked I0coin, it's what prompted the creation of the original Solidcoin 1 by Coinhunter.


~BCX~
[/quote]
as a newbie I'm slightly out of clue - wish you explain in Simple English - many thanks
(I mean  exactly this one :Solidcoin 1 by Coinhunter)

nice that you recovered dead one...
Always appreciated.

i am tired and bored of this new shitcoin popping all day long, where can i find info about this coin client and other?

I'd imagine.

More focused on getting a working client out there than merged mining, for now. That'll come later. Really just need the blockchain before I can do any serious work on this.