Topic: i0coin UPDATES - page 2. (Read 9954 times)
First part of mine to deliver to you is from 050d408b4b6d5536f410c796dfc946b9faf26e7fd5b9668317225ba2591af0d9
Unfortunately, In the intervening months since the disappearance of I0Coin I've lost a decent portion of my old balance to the aether so I'll get the remaining for you shortly. Thanks for the hard work! Apply this 10k to either the first 2 bounties or the last one, you're good on all of them I just need to reaquire the remaining balance due.
Hello all,
Since I'm behind the current I0coin resurrection, I'd like to claim all applicable bounties.
Here is a list of things I did to get the coin healthy again:
I'd like to thank:
Scanning though this thread, I find the following offerings (my list differs from the list in the first post; please correct me if I have misinterpreted something):
Lightlord: I0C 20000 (paid!)
pyra-proxy: I0C 5000, I0C 5000 (vircurex bonus), I0C 10000 (merged mining) (101% paid!)
steelhouse: I0C 5000 (110% paid!)
paladin_avatar16: I0C 20000 (merged mining), I0C 10000 (vircurex) (166 2/3% paid!)
ayayay: I0C 5000 (can't find a real source, this is just a quote) (paid! (in IXC))
If you think I am eligible to receive a bounty you posted, please transfer the appropriate amount of coin to jR8YJ3XL7PdsodCZCYocu7iDgBEi5gD5vE and post the transaction ID below, so I can mark the amount as paid.
Greetings,
Rik.
Since I'm behind the current I0coin resurrection, I'd like to claim all applicable bounties.
Here is a list of things I did to get the coin healthy again:
- analyze the problem
- implement a clean fix for the issue
- provide windows binaries (on the new I0coin homepage / rebranded the QT client using Lightlord's logos)
- provide DNSseed, since irc seed support is removed from bitcoin
- initiated a hardfork, to fix a current hardfork-requiring issues, making the coin future proof
- informed Vircurex of my progress, in an attempt to get the coin re-enabled, which they have done
I'd like to thank:
- markm for joining the discussion at an early stage and keeping the coin alive (by running the only connectible node, AFAIK)
- doublec, the previous i0coin maintainer, for supporting me as new maintainer and including the coin in his pool.
- all miners that are sending more than 20 TH/s to the coin
- all other people that have contributed in some way to the success of this resurrection
Scanning though this thread, I find the following offerings (my list differs from the list in the first post; please correct me if I have misinterpreted something):
Lightlord: I0C 20000 (paid!)
pyra-proxy: I0C 5000, I0C 5000 (vircurex bonus), I0C 10000 (merged mining) (101% paid!)
steelhouse: I0C 5000 (110% paid!)
paladin_avatar16: I0C 20000 (merged mining), I0C 10000 (vircurex) (166 2/3% paid!)
ayayay: I0C 5000 (can't find a real source, this is just a quote) (paid! (in IXC))
If you think I am eligible to receive a bounty you posted, please transfer the appropriate amount of coin to jR8YJ3XL7PdsodCZCYocu7iDgBEi5gD5vE and post the transaction ID below, so I can mark the amount as paid.
Greetings,
Rik.
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.
The forks I know of were at 14640, 150,000 and 160,000.
I have an old blk0001.dat from 10-3-2012. doublec might have later blk and latest client.
http://i0coin.bitparking.com/
http://i0coin.bitparking.com/
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.The state of the client/daemon now would require too much VPS memory for me to put on CCE.
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
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.
The state of the client/daemon now would require too much VPS memory for me to put on CCE.
I am currently in the process of reviving i0coin. To that end, I need beta testers for the new client. PM if you're interested (and have the i0coin blockchain already).
Also, merged mining support would not be available in the initial release, but the door is open for it to be added later.
Also, merged mining support would not be available in the initial release, but the door is open for it to be added later.
You need to use -testnet then so you don't screw up the real net.
Even better would be to help get the merged mining patch to apply cleanly to current bitcoin, so a proper update all the way to recent code can be done.
-MarkM-
It wouldn't screw up the real net unless there was more hashpower than the non-testing people have, and we're not hashing at this point, just trying to validate the current chain.
Could really use a block explorer right now tho... anyone still have an i0c block explorer up?
-- Smoov
I am currently in the process of reviving i0coin. To that end, I need beta testers for the new client. PM if you're interested (and have the i0coin blockchain already).
Also, merged mining support would not be available in the initial release, but the door is open for it to be added later.
Also, merged mining support would not be available in the initial release, but the door is open for it to be added later.
You need to use -testnet then so you don't screw up the real net.
Even better would be to help get the merged mining patch to apply cleanly to current bitcoin, so a proper update all the way to recent code can be done.
-MarkM-
I am currently in the process of reviving i0coin. To that end, I need beta testers for the new client. PM if you're interested (and have the i0coin blockchain already).
Also, merged mining support would not be available in the initial release, but the door is open for it to be added later.
Also, merged mining support would not be available in the initial release, but the door is open for it to be added later.
I0Coind right now is eating 4.9 gig and GeistGeld typically eats about four gig.
What kills I0Coind though is boost craps out trying to do a DNS lookup.
It is the only coin I have that problem with, I have no idea why it even does DNS lookups once it is up and running, but it dies every day or two or less from this and has to be restarted.
We need a github repo where a recent copy of bitcoin with the merged mining patches, and ONLY the merged mining patches, applied.
Once that is in place, all the merged mined coins can be updated at leisure.
Without that, each time any one of the coins gets updated the whole work of getting the merged mining patches to apply to a new version of bitcoin ends up having to be duplicated for each coin, which is just a total waste of developer-time.
-MarkM-
What kills I0Coind though is boost craps out trying to do a DNS lookup.
It is the only coin I have that problem with, I have no idea why it even does DNS lookups once it is up and running, but it dies every day or two or less from this and has to be restarted.
We need a github repo where a recent copy of bitcoin with the merged mining patches, and ONLY the merged mining patches, applied.
Once that is in place, all the merged mined coins can be updated at leisure.
Without that, each time any one of the coins gets updated the whole work of getting the merged mining patches to apply to a new version of bitcoin ends up having to be duplicated for each coin, which is just a total waste of developer-time.
-MarkM-
I may take a stab at this, but then the conditions on the bounty seem to make it far less interesting. I would have no control on if Vircurex reenables its support of the chain. So the bounties would have to be changes to just being for the technical end that I can control.
If you can resolve the memory issues I'd be willing to add it to the merge mining pool. I agree conditions involving third parties make the bounty less attractive. 
I may take a stab at this, but then the conditions on the bounty seem to make it far less interesting. I would have no control on if Vircurex reenables its support of the chain. So the bounties would have to be changes to just being for the technical end that I can control.
1st that memory issue should be fixed. It is NOT possible that ANY daemon eat so much RAM.
64bit exe will not fix it.
64bit exe will not fix it.
I0coin is still on the list of projects, it has just fallen down a "few" rungs.
If somebody does not fix it before I can get to it, I promise to take another look at it.
If somebody does not fix it before I can get to it, I promise to take another look at it.
I the mean time, if someone could post a 64 bit executable for i0coin v0.3.25.9 it would allow more miners to keep it alive! I had to stop mining once the 32 bit version died.
That would be great
I0coin is still on the list of projects, it has just fallen down a "few" rungs.
If somebody does not fix it before I can get to it, I promise to take another look at it.
If somebody does not fix it before I can get to it, I promise to take another look at it.
I the mean time, if someone could post a 64 bit executable for i0coin v0.3.25.9 it would allow more miners to keep it alive! I had to stop mining once the 32 bit version died.
I0coin is still on the list of projects, it has just fallen down a "few" rungs.
If somebody does not fix it before I can get to it, I promise to take another look at it.
Offering a bounty may encourage somebody to take up the cause, especially with the value of alt-coins sky rocketing now, and get the client patched before I can get to it again.
If somebody does not fix it before I can get to it, I promise to take another look at it.
Offering a bounty may encourage somebody to take up the cause, especially with the value of alt-coins sky rocketing now, and get the client patched before I can get to it again.
Tried the client but it crashes at 2GB...
I'm not a programmer... Too bad...
Could someone give it a try?
I'm not a programmer... Too bad...
Could someone give it a try?
Bumping this month old thread because I got a reply from someone that wants to offer a bounty.
Seems more interest is pouring into i0coin. Perhaps its a non-premined currency.
More worthy over ixcoin, as ixcoin is premined.
It should be i0coins that are worth more then ixcoin.
Lets get this problem fixed. Even though its been hogging around for a year.
It can be brought back up, its possible. As people we can make a community
based currency, made from many different ones. Anyone can contribute.
Seems more interest is pouring into i0coin. Perhaps its a non-premined currency.
More worthy over ixcoin, as ixcoin is premined.
It should be i0coins that are worth more then ixcoin.
Lets get this problem fixed. Even though its been hogging around for a year.
It can be brought back up, its possible. As people we can make a community
based currency, made from many different ones. Anyone can contribute.
Anyway my main question was if i0coin is completely dead in terms of trading?
http://galaxies.mygamesonline.org/digitalisassets.html
https://bitcointalksearch.org/topic/open-transactions-server-assetbondcommoditycryptocoindeedsharestock-exch-53329
In short, no, but, currently it seems one needs Open Transactions in order to access the markets.
At some point it should become possible to make a Ripple gateway for it, so that it can be traded on Ripple in the same gateway-enabled way that bitcoins can be, but apparently the sample gateway source code the Ripple team provided is not intended for production use and so far the gateways that are in production have not seen fit, as far as I am aware, to realease the production-grade software they are using. (If they actually even are; one can hope, but absent their source code who knows...)
-MarkM-
Sounds like the same problem I had with GeistGeld. The 32-bit version on Windows crashed once the memory consumption reached 2gig. I haven't run my i0coin client recently but I will check it tonight.
My Windows is 64bit and I got 6GB of RAM.
Anyway my main question was if i0coin is completely dead in terms of trading?
Jump to: