Bitcoin Forum

Alternate cryptocurrencies => Announcements (Altcoins) => Topic started by: rsnel on August 05, 2013, 04:02:16 AM



Title: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: rsnel on August 05, 2013, 04:02:16 AM
Please upgrade to (at least) i0coin-0.8.3-2 (or current git HEAD, branch i0coin-0.8.x) as soon as possible. All old clients are on an unsafe, unsupported and mostly stale fork of the I0coin blockchain. The fork occured on September 10th.


I0C (logo by Lightlord), our favourite non-premined, fully decentralised, merged minable altcoin is back. I0coin used to require a lot of memory, about 8.2GB. The updated version only uses about 250MB (fully synced). The problem was fixed by moving data from memory storage to disk storage (this data was almost never used, it just took up space). Technical details are in the git log.

Merged minable means you can mine this coin for free while mining BTC. The new release is compatible with the old one, users using the old crashy and memory-hungry client will see the same blockchain as users of the new client. The old client is incompatible with the old client after block 895079, you should use the new client.

Short instructions on how to join the network, and start merged mining with P2Pool:

If you want to download binaries for windows or GNU/Linux, you can find release 0.8.6-1 on my i0coin website (http://i0coin.snel.it/).

The sourcecode is in a git repository on github. The recommended branch (currently i0coin-0.8.x) is automatically selected. If you want to compile the program yourself, do:
Code:
$ git clone http://github.com/rsnel/i0coin/
$ cd i0coin/src
$ make -f makefile.unix i0coind

create ~/.i0coin/i0coin.conf which contains
Code:
server=1
daemon=1
rpcport=7332
rpcuser=i0coinrpc
rpcpassword=SOME_PASSWORD_HERE
port=7333
addnode=85.17.248.211:7333
addnone=198.154.60.61:7333
addnode=188.165.216.59:7333

Note, the seednodes are currenty hardcoded in the program, so the addnode= lines don't really do anything.

Run the daemon and let it sync. At the start of this resurrection, there were about 848000 blocks in the blockchain. Please open incoming port 7333 in your firewall, the network needs externally reachable nodes to grow.

Let's earn some coin with P2Pool. Miners that already are merged mining GG,NVC,IXC,DVC already know what to do.

For the rest of us:

Code:
$ git checkout https://github.com/forrestv/p2pool/
$ cd p2pool
$ less README.md
$ # install required packages, you did read the README didn't you?
$ ./run_p2pool.py --give-author 1.0 \
        --merged http://i0coinrpc:SOME_PASSWORD_HERE@localhost:7333/ \
        BITCOINRPC_USERNAME BITCOINRPC_PASSWORD

If you point your miner to localhost:9332 you will earn BTC, it will be sent directly to your wallet. In addition, without extra cost, you will get free I0coins. If you want to earn yet more coins (like IXC,DVC,NMC), please see this excellent topic https://bitcointalk.org/index.php?topic=62842.0. After that you should be able to figure GG out yourself.

Too much hassle? Check out http://mmpool.bitparking.com/pool/ (BTC 01.5% DGM, NMC/DVC/IXC/I0C??!?!!? PPS) to see if, they have re-enabled I0C!

I hope that, once there is enough mining power, exchanges will relist this likable coin.

Updates:
  • bitparking has enabled support for I0C
  • added seednode from pankkake, thanks!
  • official binary release 0.8.3-1 http://i0coin.snel.it/
  • this coin is officially not dead (https://bitcointalk.org/index.php?topic=134179.msg2899812#msg2899812) anymore (undead?  :o)
  • added DNSSeedNode i0seed.snel.it to current git (how it works (https://github.com/rsnel/i0coin/tree/i0coin-0.8.x/contrib/phpdnsseed))
  • official binary release 0.8.3-2 http://i0coin.snel.it/ (please upgrade asap)
  • official binary release 0.8.4-2 http://i0coin.snel.it/ (contains stability and DoS protection fixes from bitcoin)
  • the hard fork has occured, I0coin is ready for primetime!
  • official binary release 0.8.5-1 http://i0coin.snel.it/ (contains stability fixes from bitcoin)
  • Vircurex (https://vircurex.com/) has re-enabled I0coin, you can make an account there using my referral URL (https://vircurex.com/welcome/index?referral_id=489-3370)
  • official binary release 0.8.6-1 http://i0coin.snel.it/ (contains misc fixes from bitcoin)


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: George5 on August 05, 2013, 08:39:03 AM
Where do I download the client?


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: rsnel on August 05, 2013, 12:59:26 PM
Where do I download the client?
I've compiled a windows binary. It can be found in the 'updates' section of the announcement. Please test it. (note, it has no gui, it's just a system service, to communicate with it you run (in another terminal) "i0coind.exe getinfo", for example, or "i0coind.exe help" to see all commands) In "Application Data" there will be a directory called I0coin, in this directory you will find the file debug.log. See inside to know what i0coind.exe is doing.

Greetings,

Rik.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: Lucko on August 06, 2013, 09:02:06 AM
It would be really nice to have a GUI...


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: rsnel on August 06, 2013, 08:32:38 PM
It would be really nice to have a GUI...
I will look into it.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: Lucko on August 06, 2013, 08:52:03 PM
Thanks!!!


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: ssateneth on August 07, 2013, 01:44:38 AM
It would be really nice to have a GUI...


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: purelithium on August 07, 2013, 02:15:42 AM
It would be really nice to have a GUI...


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: K1773R on August 07, 2013, 09:00:32 AM

I0C (logo by Lightlord), our favourite non-premined, fully decentralised, merged minable altcoin is back. I0coin used to require a lot of memory, about 8.2GB. The updated version only uses about 250MB (fully synced). The problem was fixed by moving data from memory storage to disk storage (this data was almost never used, it just took up space). Technical details are in the git log.

Merged minable means you can mine this coin for free while mining BTC. The new release is compatible with the old one, users using the old crashy and memory-hungry client will see the same blockchain as users of the new client.

Short instructions on how to join the network, and start merged mining with P2Pool:

The sourcecode is in a git repository on github. The recommended branch (currently i0coin-0.8.x) is automatically selected.
Code:
$ git clone http://github.com/rsnel/i0coin/
$ cd i0coin/src
$ make -f makefile.unix i0coind

create ~/.i0coin/i0coin.conf which contains
Code:
server=1
daemon=1
rpcport=7332
rpcuser=i0coinrpc
rpcpassword=SOME_PASSWORD_HERE
port=7333
addnode=85.17.248.211:7333
addnone=198.154.60.61:7333

Run the daemon and let it sync. Currently there are about 848000 blocks in the blockchain. Please open incoming port 7333 in your firewall, the network needs externally reachable nodes to grow.

Let's earn some coin with P2Pool. Miners that already are merged mining GG,NVC,IXC,DVC already know what to do.

For the rest of us:

Code:
$ git checkout https://github.com/forrestv/p2pool/
$ cd p2pool
$ less README.md
$ # install required packages, you did read the README didn't you?
$ ./run_p2pool.py --give-author 1.0 \
        --merged http://i0coinrpc:SOME_PASSWORD_HERE@localhost:7333/ \
        BITCOINRPC_USERNAME BITCOINRPC_PASSWORD

If you point your miner to localhost:9332 you will earn BTC, it will be sent directly to your wallet. In addition, without extra cost, you will get free I0coins. If you want to earn yet more coins (like IXC,DVC,NMC), please see this excellent topic https://bitcointalk.org/index.php?topic=62842.0  After that you should be able to figure GG out yourself.

Too much hassle? Check out http://mmpool.bitparking.com/pool/ (BTC 0% DGM, NMC/DVC/IXC/I0C?!?! PPS) to see if they have re-enabled I0C!

I hope that, once there is enough mining power, exchanges will relist this likable coin.

Updates:
  • Windows binary available at: http://i0coin.snel.it/

thanks, going to add it to my p2pool again :) couldnt stand the memory hog :S
now you should do it with CLC + GRC too, in case you want to and have enough time ;)


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: xorxor on August 07, 2013, 09:38:11 AM
just a notice:

i0coin was originally launched 2011!
That means 25% 66% of all coins alre already mined.
As for dead mergemined chain, it means mined for free @ zero diff.

It's a i25coin i66Coin now, not i0coin, if chain is not restarted.



Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: K1773R on August 07, 2013, 09:57:20 AM
just a notice:

i0coin was originally launched 2011!
That means 25% of all coins alre already mined.
As for dead mergemined chain, it means mined for free @ zero diff.

It's a i25coin now, not i0coin, if chain is not restarted.


thats so wrong, this is just a fix for the stupidity of the original i0coin, this is not a different coin, just a fixed sourcebase!


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: rsnel on August 07, 2013, 10:02:26 AM
Hi All,

Thanks for all the positive reactions.

I am working on the GUI. Compilation in GNU/Linux is fixed (update availabe in git repository) and I replaced some bitcoin logo's by i0coin logos.

Next step is to setup a VM with windows to provide GUI binaries. Don't hold your breath...

Greetings,

Rik.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: Cockeyed on August 07, 2013, 10:05:31 AM
This seems really cool.

I am used to DOS, so using the command prompt is no problem for me. But I really would like to have kind of a manual with the meaning of all the commands. OK, they are kind of "self explanatory", got it. But all the trial and error costs many hours / maybe days. Thanks a lot anyways! :)


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: K1773R on August 07, 2013, 11:00:56 AM
This seems really cool.

I am used to DOS, so using the command prompt is no problem for me. But I really would like to have kind of a manual with the meaning of all the commands. OK, they are kind of "self explanatory", got it. But all the trial and error costs many hours / maybe days. Thanks a lot anyways! :)
i0coind help <yourcommand>


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: r3wt on August 07, 2013, 11:03:37 AM
+1, i loved this con.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: Cockeyed on August 07, 2013, 12:10:09 PM
"i0coind help <yourcommand>"

thanks! Stupid me... :P


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: creativex on August 07, 2013, 12:48:00 PM
Hi All,

Thanks for all the positive reactions.

I am working on the GUI. Compilation in GNU/Linux is fixed (update availabe in git repository) and I replaced some bitcoin logo's by i0coin logos.

Next step is to setup a VM with windows to provide GUI binaries. Don't hold your breath...

Greetings,

Rik.

Nice work Rik. Out of curiosity I started the dusty old I0coin windows gui yesterday for the first time this year. This was on a windows 8 x64 vm and I was surprised to see it find a single connection and begin downloading the chain. It eventually crashed of course, but it took 20mins or so and updated thousands of transactions during that time. Possible you can work backwards from the old windows gui to expedite the update process?

Cheers.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: skrubalov on August 07, 2013, 01:32:49 PM
Where do I download the client?
I've compiled a windows binary. It can be found in the 'updates' section of the announcement. Please test it. (note, it has no gui, it's just a system service, to communicate with it you run (in another terminal) "i0coind.exe getinfo", for example, or "i0coind.exe help" to see all commands) In "Application Data" there will be a directory called I0coin, in this directory you will find the file debug.log. See inside to know what i0coind.exe is doing.

Greetings,

Rik.

I've tried those commands but i get an error "'i0coind.exe' is not recognized as an internal or external command,
operable program or batch file."
How do I fix that?
How to find out my wallet address?
thanks


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: rsnel on August 07, 2013, 01:39:20 PM
Nice work Rik. Out of curiosity I started the dusty old I0coin windows gui yesterday for the first time this year. This was on a windows 8 x64 vm and I was surprised to see it find a single connection and begin downloading the chain. It eventually crashed of course, but it took 20mins or so and updated thousands of transactions during that time. Possible you can work backwards from the old windows gui to expedite the update process?

Cheers.

Thanks!

Well, the linux GUI seems to work. I have replaced most instances of Bitcoin with I0coin. Windows compilation can probably be done by everyone who can compile Bitcoin v0.8.3. Windows GUI binaries will probably be here before the weekend.

Side node: your old node found other nodes through IRC (there are some old nodes active on the network; I keep it running to be able to spot possible incompatibility issues (none expected and none seen so far)).


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: xorxor on August 07, 2013, 01:46:25 PM
just a notice:

i0coin was originally launched 2011!
That means 25%  of all coins alre already mined.
As for dead mergemined chain, it means mined for free @ zero diff.

It's a i25coin  now, not i0coin, if chain is not restarted.


thats so wrong, this is just a fix for the stupidity of the original i0coin, this is not a different coin, just a fixed sourcebase!


2 possibilities:

1. (actual) "this is not a different coin, just a fixed sourcebase!"

- the SAME genesis block, 2 years of freemining 25% 66% of the coins, no cost, zero diff.

2 (theoretical) new genesis block

- fair start


That is not wrong. That is why long dead coins CANNOT be resurrected.
..unless someone tries to cheat some people into believing it is, just to dump the freemined worthless coins.




Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: markm on August 07, 2013, 02:14:24 PM
That is silly, it was never dead, it is just that a lot of miners have been too lazy to run their own merged mining setups so have been missing out on most of the merged mined coins.

If you chose not to throw RAM at it that is your choice, don't go all dog in the manger / sour grapes now just because others were willing to spend resources to keep on mining.

Sounds like you probably also are not mining GRouPcoin, CoiLedCoin, and GeistGeld, too?

GeistGeld in particular is in the same boat that I0Coin was: they both exposed a resource cost of merged mining that all merged mined coins will eventually face. It has now been fixed in I0Coin and hopefully the fix will soon be applied to GeistGeld too, then hopefully also eventually to all the merged mined coins before they start to suffer as much as I0Coin and GeistGeld did.

Those who have thrown resources at keeping those coins alive have done all merged mined coins a service by continuing to keep at least some small amount of awareness on the memory problems all such coins are going to have to eventually deal with.

-MarkM-


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: xorxor on August 07, 2013, 02:55:34 PM
That is silly, it was never dead, it is just that a lot of miners have been too lazy to run their own merged mining setups so have been missing out on most of the merged mined coins.

If you chose not to throw RAM at it that is your choice, don't go all dog in the manger / sour grapes now just because others were willing to spend resources to keep on mining.

Sounds like you probably also are not mining GRouPcoin, CoiLedCoin, and GeistGeld, too?

GeistGeld in particular is in the same boat that I0Coin was: they both exposed a resource cost of merged mining that all merged mined coins will eventually face. It has now been fixed in I0Coin and hopefully the fix will soon be applied to GeistGeld too, then hopefully also eventually to all the merged mined coins before they start to suffer as much as I0Coin and GeistGeld did.

Those who have thrown resources at keeping those coins alive have done all merged mined coins a service by continuing to keep at least some small amount of awareness on the memory problems all such coins are going to have to eventually deal with.

-MarkM-


There is completely no difference why coin was abandoned by 99.9% of cryptos users.

-intentional scam
-resource hog, not repaired in time
-price crash
-bad difficulty adjustment algorithm [high diff halt, resonance, zero diff drop, <50% timetravel attack]
-51% attack
-security hole

Effect is allways the same after 2 years.
Freemining , effectively identical to monsterous premine.

keeping the chain alive on few private PC's is not keeping the coin alive.
Coin is the comunity, not only blockchain:
-developers and their continuous support
-services
-investment buying support
-dedicated miners and pools
-exchanges and trading volume.

When all this died to ZERO, keeping the blockchain itself alive at zero diff is not keeping the coin alive, it's worse than death.
The fact  that someone can keep the blockchain alive and freemine all the time, is the reason dead coin once is dead for good.

BBQ was considered dead and forgotten for much much shorter period of time, and few guys got to around 1000000BQC just by mining with CPU or few minutes a day on GPU.

I don't mean the blockchaint is dead, the coin is. if blockchain is alive, you can try to resurrect coin.
If you find enough suckers to buy in all the dumping freemine, it might be a success.

I just believe everybody should know about Premine, instamine or in this case : freemine of a 66%  of all coins ever to be mined.
 
Earlier I stated 25%, but I was fooled by a bad maths done in the code :

Code:
// Subsidy is cut in half every 218750 blocks, which will occur approximately every 4 years
    nSubsidy >>= (nHeight / 218750);

    return nSubsidy + nFees;
}

static const int64 nTargetSpacing = 90;    //1.5 minute blocks

How the heck 218750 of 1.5 minute blocks is 4 years?
that is halving every ~228 days
 
and that means,  I0Coin aka I66Coin with 66% freemine is 2 place most "preallocated" coin in the history , ex-aequo with orbitcoin's 66% instamine.
The most preallocated coin was MMM with 10Trillon premined and 0.01 reward ....


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: xorxor on August 07, 2013, 03:13:24 PM
Oh, one big difference:

all of the things like:

-hidden off-forum launch
-premine
-launch without binaries or nodes given
-instamine
-zero starting diff

all are simply a SCAM!!!! intentional try to steal from investors.

while You and few others that kept all dead mergemined coins did nothing wrong:

-all the time You allways stated that you are mining them
-all the time You tried to find new miners and users and gave help to do so.

so You are fair.

there is no difference to anyone trying to join now though :C


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: pyra-proxy on August 07, 2013, 03:14:43 PM
Quote from: xorxor
Oh, one big difference:

all of the things like:

-hidden off-forum launch
-premine
-launch without binaries or nodes given
-instamine
-zero starting diff

all are simply a SCAM!!!! intentional try to steal from investors.

while You and few others that kept all dead mergemined coind did nothing wrong:

-all the time You allways stated that you are mining them
-all the time You tried to find new miners and users and gave help to do so.

so You are fair.

there is no difference to anyone trying to join now though :C

It wasn't "freemined" though, just because you were not mining it, others were and it cost them to do so.  I mined this chain on bitparking all the way up to the point where it was dropped and if vircurex can recover it's old wallets I have quite a few saved there otherwise my old coin are obliterated.  So ya it'd be advatageous for me to start from block 0, but that is not fair to those who spent time/resources on this chain when I chose not too.

Why do you want it to be more "fair" for you over those who stuck with the coin prior to it being fixed?


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: purelithium on August 07, 2013, 04:30:21 PM
People seem to be getting butthurt over the fact that they can't "get in on the ground level" on this coin like most of the other new offerings on the forum.

This is just an old coin coming back, it's not intended to "scam" anyone, certain people were willing to deal with the issues of the old client, now those issues are being fixed, and released to the wider public to decide if they want to support this piece of cryptocoin history, or not.

I tweeted Cryptsy last night to see if they would support the coin again. The reply was that they would research it. Maybe an exchange onboard with the resurrection?!


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: xorxor on August 07, 2013, 04:33:30 PM

It wasn't "freemined" though, just because you were not mining it, others were and it cost them to do so.  I mined this chain on bitparking all the way up to the point where it was dropped and if vircurex can recover it's old wallets I have quite a few saved there otherwise my old coin are obliterated.  So ya it'd be advatageous for me to start from block 0, but that is not fair to those who spent time/resources on this chain when I chose not too.

Why do you want it to be more "fair" for you over those who stuck with the coin prior to it being fixed?



Let's start with :  not for me. I care for others that might want to partipate. I will not participate in 66% preallocated coind so I dont care "for me"
Even if blockchain would have been restarted, I would not participate - I don't have a single asic so all sha256 coins are not for me to mine.

next:  I dont get your ethics, "fair for them, or fair for me, or fair for you."

All three are UNFAIR in my understanding and fair for everyone is the only fair I know.

-there is nothing bad in mining dead coin just in case , it's smart thing do.

- there are no resources used to do it, its dead so there is zero diff, you get everything for free. and here we talk about mergemined coins so this would be free anyway.

  



Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: xorxor on August 07, 2013, 04:36:47 PM
People seem to be getting butthurt over the fact that they can't "get in on the ground level" on this coin like most of the other new offerings on the forum.

This is just an old coin coming back, it's not intended to "scam" anyone, certain people were willing to deal with the issues of the old client, now those issues are being fixed, and released to the wider public to decide if they want to support this piece of cryptocoin history, or not.

I tweeted Cryptsy last night to see if they would support the coin again. The reply was that they would research it. Maybe an exchange onboard with the resurrection?!


Yea. You call it butthurt, I call it :

"ONE OF THE MOST PREMINED COINS IN HISTORY "

If you just simply ignored my warning , it would just stay there . trying to say I'm wrong is a bad thing for You.

 just leave it.

P.S.

I Dont have any agenda against I0Coin, if it will pick up on exchanges and some BTC pools start to mergemine it and not a single one of the freemine guys dumps his coins, it wil be alive again in no time.   No problem for me. Just warned some before buying.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: SirMintALot on August 07, 2013, 05:38:43 PM
IMHO premined is a wrong term in this case, as the coin was never dead and the "preminined" coins are in many hands, and not just the "developers". It's just a nice little extra that you get and that costs you nothing when you are on a merged mined pool that supports I0coin.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: xorxor on August 07, 2013, 06:54:49 PM
IMHO premined is a wrong term in this case, as the coin was never dead and the "preminined" coins are in many hands, and not just the "developers". It's just a nice little extra that you get and that costs you nothing when you are on a merged mined pool that supports I0coin.

of course it is not a standart premine, read the whole thread.

I used terms: "preallocation" and "freemining" .

actually in this case : " [ANN][I0C] Resurrection" 66% of coins where mined BEFORE annoucement for free, so you can call it premine.



Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: mr_random on August 07, 2013, 07:35:18 PM
Anyone who kept the faith and continued mining it for months after it died deserve to have their faith rewarded imo.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: xorxor on August 07, 2013, 07:58:00 PM
Anyone who kept the faith and continued mining it for months after it died deserve to have their faith rewarded imo.

yup, there is nothing wrong or immoral in doing that, especially that markm talked about it everywhere he could. That was a smart thing to do.

For anyone to buy into this market, they should know they are buying into coin that 66% is already owned by few guys. It still might be a huge success, but they should know.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: markm on August 07, 2013, 08:12:09 PM
Actually vast amounts of this coin were mined on bit parking pool long ago at difficulties too high for me to get many of tm.

Once bitparking dropped it the difficulty did eventually get low but still even mining it through all the time since bitparking dropped it I doubt i have anywhere near as many of them as any large miner who got them while they were on bitparking.

IXCoin stayed on bitparking all along, all that this relatively brief time of I0Coin not being on bitparking has done is let me catch up a little so I actually have more I0Coins than IXCoins now, I still do not have many of either through compared to any actually large miner who mines at bitparking.

Already bitparking is getting most of the blocks too, so it won't be long before the large miners there more than make up for the few coins they missed out on the months it has been off the pool due to the memory problems.

-MarkM-


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: xorxor on August 07, 2013, 08:18:46 PM
Actually vast amounts of this coin were mined on bit parking pool long ago at difficulties too high for me to get many of tm.

Once bitparking dropped it the difficulty did eventually get low but still even mining it through all the time since bitparking dropped it I doubt i have anywhere near as many of them as any large miner who got them while they were on bitparking.

IXCoin stayed on bitparking all along, all that this relatively brief time of I0Coin not being on bitparking has done is let me catch up a little so I actually have more I0Coins than IXCoins now, I still do not have many of either through compared to any actually large miner who mines at bitparking.

Already bitparking is getting most of the blocks too, so it won't be long before the large miners there more than make up for the few coins they missed out on the months it has been off the pool due to the memory problems.

-MarkM-



I can only congratulate You great idea of keeping them in your mergemine collection. If it is allready picking up, You will make a nice return.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: purelithium on August 07, 2013, 09:11:14 PM


of course it is not a standart premine, read the whole thread.

I used terms: "preallocation" and "freemining" .

actually in this case : " [ANN][I0C] Resurrection" 66% of coins where mined BEFORE annoucement for free, so you can call it premine.



What are you talking about? This coin has been in the wild for 2 years now, many coins were mined by solo miners, merge miners, and pools. Exchanges supported this coin, the only reason it fell out of favour is because of issues in the client that was abandoned by the developers. A few individuals have decided to update and fix a stagnant project in order to make it useful again. It didn't die; people just gave up because it wasn't working for them anymore. Rather, that it was too much of a hassle for them to keep it running.

I'm not sure what "Announcement" you're talking about, this thread is definitely not the first time this coin has been talked about:

The original thread: https://bitcointalk.org/index.php?topic=36425.0

More:

https://bitcointalk.org/index.php?topic=194887.0

https://bitcointalk.org/index.php?topic=143512.0  (From this year!)

https://bitcointalk.org/index.php?topic=55482.0

You're crazy if you think this coin was hidden. No one cared about it because it was frustrating to use the client due to the abandonware. It's now being actively developed again and people are starting to care again.

You say you don't have an agenda against i0coin, but your constant chirping about how it was freemined belies that statement.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: xorxor on August 08, 2013, 02:33:51 AM

What are you talking about? This coin has been in the wild for 2 years now, many coins were mined by solo miners, merge miners, and pools. Exchanges supported this coin, the only reason it fell out of favour is because of issues in the client that was abandoned by the developers. A few individuals have decided to update and fix a stagnant project in order to make it useful again. It didn't die; people just gave up because it wasn't working for them anymore. Rather, that it was too much of a hassle for them to keep it running.

I'm not sure what "Announcement" you're talking about, this thread is definitely not the first time this coin has been talked about:

The original thread: https://bitcointalk.org/index.php?topic=36425.0

More:

https://bitcointalk.org/index.php?topic=194887.0

https://bitcointalk.org/index.php?topic=143512.0  (From this year!)

https://bitcointalk.org/index.php?topic=55482.0

You're crazy if you think this coin was hidden. No one cared about it because it was frustrating to use the client due to the abandonware. It's now being actively developed again and people are starting to care again.

You say you don't have an agenda against i0coin, but your constant chirping about how it was freemined belies that statement.


You must be shure another post by me will be good for your I0coins... ok, so another one:

Quote
"It didn't die; people just gave up because it wasn't working for them anymore"

well, yup. self explanatory. didnt die, just stopped working for most users, EVERY POOL AND EXCHANGE..... yup. not dead at all.

Quote
The original thread: https://bitcointalk.org/index.php?topic=36425.0

 90% of this thread is from 2011, than in 2012 a lot of pages about:
 multiple forking of the chain and failed tries to synchronize
 bugs with difficulty droping to zero and mined thousands of blocks in no time,
 bugs with exeptions and memleaks.
 pools disabling i0coin from mergemining.
 
Quote
https://bitcointalk.org/index.php?topic=194887.0

This is well known I0C fan ADMITTING the coin is dead and asking if it can be revived.
Also, geting answer that it would be 3rd time, since coin died 3 times after 2 revivals.

Quote
https://bitcointalk.org/index.php?topic=143512.0 (From this year!)

this is one page about one guy asking if it can be mined, one page.

Quote
https://bitcointalk.org/index.php?topic=55482.0

this is  bragging about exchange in 2011, one page.

Quote
You're crazy if you think this coin was hidden. No one cared about it because it was frustrating to use the client due to the abandonware.

"I am crazy to think coin was hidden" when "NO ONE CARED ABOUT IT" due to client crashing nonstop and no pools or exchanges or nodes

Quote
It's now being actively developed again and people are starting to care again.

Thats great! just let them know coin is ~66% mined by now , over a year of it for free at no diff.

Quote
You say you don't have an agenda against i0coin, but your constant chirping about how it was freemined belies that statement.

Read carefully the thread - I posted only one simple post.  All others are  just answers to attacks on me in person.
I just dont like being acused of being "silly" , "crazy" etc. and im explaining my point.
Attack me again if you wish for another post like this, but I believe that is not a good promotion for your precius i66coin.


p.s.

also, this coin can be fcuk'ed inside-out by any basic coder and <1% attacked  LOL!!!

Code:
     //due to retargets being done more often it also needs to be lowered significantly from the 4x increase

slowed diff increase, but  :

Code:
else if (nActualTimespan > nTargetTimespan*4)   nActualTimespan = nTargetTimespan*4;

left the 4x decrase limit.

you can simply take diff to ZERO at any given moment and orphan any amount of blocks you want, just set the timestamps prearranged way..
- reverse transactions and doublespending
- steal all mining

 


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: purelithium on August 08, 2013, 12:29:30 PM
You seem to think i'm lightlord, you're clearly not paying attention.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: xorxor on August 08, 2013, 12:59:08 PM
You seem to think i'm lightlord, you're clearly not paying attention.

oh, corrected.  sorry.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: BountyCoin on August 08, 2013, 01:00:06 PM
glad to see this coin come back to life!


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: rsnel on August 08, 2013, 09:04:51 PM
Where do I download the client?
I've compiled a windows binary. It can be found in the 'updates' section of the announcement. Please test it. (note, it has no gui, it's just a system service, to communicate with it you run (in another terminal) "i0coind.exe getinfo", for example, or "i0coind.exe help" to see all commands) In "Application Data" there will be a directory called I0coin, in this directory you will find the file debug.log. See inside to know what i0coind.exe is doing.

Greetings,

Rik.

I've tried those commands but i get an error "'i0coind.exe' is not recognized as an internal or external command,
operable program or batch file."
How do I fix that?
How to find out my wallet address?
thanks
Hi skrubalov,

Please try the official windows installer for release 0.8.3-1. You can find it at my i0coin website http://i0coin.snel.it/ (http://i0coin.snel.it/). It should work out of the box.

Greetings,

Rik.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: purelithium on August 08, 2013, 09:47:54 PM
Awesome job on the GUI, looks great and grabbed my wallet file and blockindex perfectly


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: K1773R on August 09, 2013, 03:40:32 PM
@rsnel:

you have a little typo in makefile.unix in <git>/src/

Code:
all: i0coin
it should be
Code:
all: i0coind
as there is no build target i0coin, only i0coind ;)

you had issues disabled @ github so i report it here


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: xorxor on August 09, 2013, 05:31:58 PM
https://bitcointalk.org/index.php?topic=134179.msg2899812#msg2899812



I moved I0Coin from the "dead" section


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: rsnel on August 09, 2013, 06:40:21 PM
@rsnel:

you have a little typo in makefile.unix in <git>/src/

Code:
all: i0coin
it should be
Code:
all: i0coind
as there is no build target i0coin, only i0coind ;)

you had issues disabled @ github so i report it here

Thanks. It is fixed.

Greetings,

Rik.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: rsnel on August 09, 2013, 10:13:39 PM
Hi xorxor,

https://bitcointalk.org/index.php?topic=134179.msg2899812#msg2899812

I moved I0Coin from the "dead" section

I0coin is officially undead! Whooohooo!

Regarding the percentage of coins already in circulation; it is much worse that you said before.

I0coin started with a block subsidy of 48 coins per block. It halves every 218750 blocks. At most, there will be 96*218750 = 21000000 coins.

Now, say at block 850000, we have (48 + 24 + 12)*218750 + 6 * (850000 - 3*218750) = 19537500 coins in circulation. This means 93% of the coins are already mined. Fortunately this coin can be mined for free, so miners do not have to live off of transaction fees.

You also warned about a possible attack on I0coin.

Quote from: xorxor
also, this coin can be fcuk'ed inside-out by any basic coder and <1% attacked  LOL!!!

The code you quote has in some cases a lower limit for difficulty changes smaller than 4, but not in the default case. I believe this is to prevent coin hopping (a lot of hashrate on a coin -> very high difficulty -> miners go to another coin -> blockchain moves very slow).

Note that I0coin has the anti-timewarp patch from solidcoin.

Is the vulnerability you talk about documented somewhere, can you point me to a thread or an example?

Greetings,

Rik.






Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: K1773R on August 10, 2013, 08:35:24 AM
I0coin is officially undead! Whooohooo!
Iz0mbieCoin!


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: K1773R on August 10, 2013, 09:14:50 AM
@rsnel:
there has been a bounty of several thousand i0coins if someone fixes the i0coin problems, i just messaged lightlord to pay you the bounty ;)


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: rsnel on August 10, 2013, 09:32:05 AM
@rsnel:
there has been a bounty of several thousand i0coins if someone fixes the i0coin problems, i just messaged lightlord to pay you the bounty ;)
Thanks, I knew there was a bounty.

But a condition is that the coin is listed on some major exchange. I expect it to happen, but it hasn't happened yet.



Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: pyra-proxy on August 10, 2013, 03:02:14 PM
@rsnel:
there has been a bounty of several thousand i0coins if someone fixes the i0coin problems, i just messaged lightlord to pay you the bounty ;)
Thanks, I knew there was a bounty.

But a condition is that the coin is listed on some major exchange. I expect it to happen, but it hasn't happened yet.



That was only for a portion of the bounty, for some of the bount(ies) you've already earned them I think....


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: markm on August 10, 2013, 03:53:13 PM
I am not sure if a bounty ever did get offered for the "mergecoin" thing, just the basic applying of the merged mining as secondary chain patches to bitcoin.

If so I think this update of I0Coin serves fine to accomplish the same end as the mergecoin thing would have so you should get it if indeed such a bounty did end up getting offered. I just don't recall if it did or not.

(It would have been a DeVCoin bounty, in the DeVCoin thread.)

-MarkM-


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: xorxor on August 10, 2013, 04:25:47 PM
Hi xorxor,

https://bitcointalk.org/index.php?topic=134179.msg2899812#msg2899812

I moved I0Coin from the "dead" section

I0coin is officially undead! Whooohooo!

Regarding the percentage of coins already in circulation; it is much worse that you said before.

I0coin started with a block subsidy of 48 coins per block. It halves every 218750 blocks. At most, there will be 96*218750 = 21000000 coins.

Now, say at block 850000, we have (48 + 24 + 12)*218750 + 6 * (850000 - 3*218750) = 19537500 coins in circulation. This means 93% of the coins are already mined. Fortunately this coin can be mined for free, so miners do not have to live off of transaction fees.

You also warned about a possible attack on I0coin.

Quote from: xorxor
also, this coin can be fcuk'ed inside-out by any basic coder and <1% attacked  LOL!!!

The code you quote has in some cases a lower limit for difficulty changes smaller than 4, but not in the default case. I believe this is to prevent coin hopping (a lot of hashrate on a coin -> very high difficulty -> miners go to another coin -> blockchain moves very slow).

Note that I0coin has the anti-timewarp patch from solidcoin.

Is the vulnerability you talk about documented somewhere, can you point me to a thread or an example?

Greetings,

Rik.


You can time-attack not only by compressing time and therefore speeding up your miner relatively. this attack can be patched against. it can be detected because the longer chain has bad time.

I0coin [not only I0C, a lot of devs doesn't get it ant tries to fasten diff algo that way] uses heavily asymetric towards drop diff adjustment, which can be attacked differently.
First you compress the time, than strech it perfectly to get maximum drop but to more. this way you can drop diff to zero, with proper time. now you mine SHITLOAD of blocks and introduce it to the network. BUM! much higher chain, timestamps are correct => doublespending and freemining.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: markm on August 10, 2013, 05:53:34 PM
Oh darn, it lets difficulty drop more than it lets it rise?

All coins that do that need to be fixed. I guess it was a fashionable thing to do at some point in the distant past.

-MarkM-


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: Tomatocage on August 10, 2013, 06:39:31 PM
It's not officially undead til it has an exchange :)


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: rsnel on August 10, 2013, 07:35:28 PM
About the vulnerability discussed by xorxor and markm.

I read some threads about the "asymmetric adjustment", most notably this post:
https://bitcointalk.org/index.php?topic=46498.msg555148#msg555148

If I understand it correctly, an asymmetric adjustment makes a 51% attack more profitable, because an alternate chain can be produced which has the same amount of work as the original chain and is a lot higher.

This is obviously bad, since it encourages 51% attacks. Judging from the difficulty we only have 111622.573485*2^32/90=5.3TH/s at our disposal (about 1/4 of ixcoin). Due to merged mining, we can be attacked for free...

Also, the limit (factor of 4) to the adjustments is too large, compared to the amount of blocks that are part of the computation.

To play it safe, I think we should use bitcoin as a baseline, and try not to deviate too much. I0coin adjusts over a period of 120 blocks. Bitcoin readjusts every 2016 blocks. So the retarget should be limited by about 4^(120/2016) = 1.086.

Is this too conservative? What other value is reasonable?

Letting this new retarget rule commence at block XXXXXX will cause a hard fork. Announcements will be needed on pools, this topic, homepages (old i0coin page at bitparking and new one by me). It would be nice to reach some community consensus before doing such a thing.

The patch would look like this:
Code:
diff --git a/src/main.cpp b/src/main.cpp
index 132ffb4..186fb91 100644
--- a/src/main.cpp
+++ b/src/main.cpp
@@ -1236,6 +1236,9 @@ unsigned int static GetNextWorkRequired(const CBlockIndex* pindexLast, const CBl
 
     // Limit adjustment step
     int64 nActualTimespan = pindexLast->GetBlockTime() - pindexFirst->GetBlockTime();
+
+    if (height < XXXXXX) {
+
     int64 nTwoPercent = nTargetTimespan/50;
     //printf("  nActualTimespan = %"PRI64d"  before bounds\n", nActualTimespan);
 
@@ -1255,6 +1258,11 @@ unsigned int static GetNextWorkRequired(const CBlockIndex* pindexLast, const CBl
     }
     else if (nActualTimespan > nTargetTimespan*4)   nActualTimespan = nTargetTimespan*4;
 
+    } else {
+        if (nActualTimespan < nTargetTimespan/1.086) nActualTimespan = nTargetTimespan/1.086;
+        else if (nActualTimespan > nTargetTimespan*1.086) nActualTimespan = nTargetTimespan*1.086;
+    }
+
     // Retarget
     CBigNum bnNew;
    bnNew.SetCompact(pindexLast->nBits);

Comments?

Edit:

  • original indent kept for readability
  • anyone against activating BIP16 and BIP30?
  • something must be done about the block versions, I propose to keep accepting v1 blocks (since a non merged miner would generate v2 blocks, and a supermajority of v2 blocks will lead to non-acceptance of v1 blocks)
  • these are the blocks that violate BIP30 at this moment, they contain a copy of an earlier coinbase transaction, therby invalidating unspent coins in the earlier coinbase
Code:
BLOCK 512462 FAILS BIP30
BLOCK 512463 FAILS BIP30
BLOCK 512464 FAILS BIP30
BLOCK 512467 FAILS BIP30
BLOCK 512479 FAILS BIP30
BLOCK 855597 FAILS BIP30
BLOCK 855599 FAILS BIP30
BLOCK 855602 FAILS BIP30
BLOCK 855604 FAILS BIP30
BLOCK 855605 FAILS BIP30
BLOCK 855608 FAILS BIP30
BLOCK 855610 FAILS BIP30
BLOCK 855612 FAILS BIP30
BLOCK 855614 FAILS BIP30
BLOCK 855616 FAILS BIP30
BLOCK 855618 FAILS BIP30
BLOCK 855622 FAILS BIP30
BLOCK 855625 FAILS BIP30
BLOCK 855629 FAILS BIP30
BLOCK 855631 FAILS BIP30
BLOCK 855633 FAILS BIP30
  • we can also drop the bdb limits on blocks


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: rsnel on August 10, 2013, 08:13:05 PM
It's not officially undead til it has an exchange :)

Well, I wouldn't blame the exchanges if they waited until bitparking has < 50% of the hashrate (more pools/p2pminers needed!). Bitparking has 25% of ixcoin, it must be coming from somewhere (private instances of p2pool?). (auxpows can now be examined through getblock in latest git).

Also the proposed hard fork, may sound scary....



Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: doublec on August 10, 2013, 11:41:30 PM
Well, I wouldn't blame the exchanges if they waited until bitparking has < 50% of the hashrate (more pools/p2pminers needed!). Bitparking has 25% of ixcoin, it must be coming from somewhere (private instances of p2pool?). (auxpows can now be examined through getblock in latest git).
Bitparking has currently around 50 immature blocks out of 120. It floats from 30-55 over the last few days. That means it has less than 50% of the hash rate. Bitparkings entire hashrate isn't used on i0coin as I don't react to blocks found meaning I get a lot of stale share submissions. There's at least one other big miner mining the chain. For ixcoin and devcoin there are other big miners mining it too - When I last investigated it was disqus fish and/or 'made in china' IIRC.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: rsnel on August 11, 2013, 06:48:34 AM
@doublec

Well, I wouldn't blame the exchanges if they waited until bitparking has < 50% of the hashrate (more pools/p2pminers needed!). Bitparking has 25% of ixcoin, it must be coming from somewhere (private instances of p2pool?). (auxpows can now be examined through getblock in latest git).
Bitparking has currently around 50 immature blocks out of 120. It floats from 30-55 over the last few days. That means it has less than 50% of the hash rate. Bitparkings entire hashrate isn't used on i0coin as I don't react to blocks found meaning I get a lot of stale share submissions. There's at least one other big miner mining the chain. For ixcoin and devcoin there are other big miners mining it too - When I last investigated it was disqus fish and/or 'made in china' IIRC.

It is good to hear that other large miners have picked I0coin up. Just keep ramping up the hashrate...

What's your opinion on the possible hard fork? Will you support it? I specifically need announcements on the i0coin.bitparking.com website and the poolwebsite itself.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: K1773R on August 11, 2013, 08:21:22 AM
im against hard forking

EDIT: im ok with hardforking if we bundle up alot of fixed and backports from bitcoin ;) ie, make it worth


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: lightlord on August 11, 2013, 09:12:09 AM
https://bitcointalk.org/index.php?topic=124316.0

Yes there is a 20,000 i0coin bounty for the fix of the bug.
It will be a while to download the entire i0coin block chain.

Post your address, so I can send your bounty.
There is other bounties up, so post in that thread
stating the fix and PM them.

Best regards
Lightlord


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: rsnel on August 11, 2013, 09:27:27 AM
@lightlord

I think I met all conditions except introduction at exchanges. I analyzed the problem (https://bitcointalk.org/index.php?topic=224744.msg2830598#msg2830598) (incidentally, almost all points on the 'further work' list are addressed at the moment) and eventually implemented a solution (https://bitcointalk.org/index.php?topic=224744.msg2846493#msg2846493), which I defended and which as been adopted by the community @6.1TH/s and about 40 with my seednode. Both vircurex and cryptsy are following the situation closely. They are probably wary of difficulty adjustment problems (as TRC is having now).

Before that, my hard-fork proposal needs to be debated.

I will probably write a pre-announcement with rationale. If there are no objections I will push a version 0.8.3-2 that will fork the chain at some point in the future and will contain
  • symmetric and slow (as fast as bitcoin) adjustment
  • BIP16
  • BIP30
  • perpetual acceptance of v1 blocks
  • bdb limits lifted

AFAIK these are all the hardfork requiring fixes from recent bitcoin.

My bounty receiving address is jR8YJ3XL7PdsodCZCYocu7iDgBEi5gD5vE


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: lightlord on August 11, 2013, 07:11:58 PM
My bounty receiving address is jR8YJ3XL7PdsodCZCYocu7iDgBEi5gD5vE

20,000 bounty sent.



Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: rsnel on August 11, 2013, 09:03:38 PM
My bounty receiving address is jR8YJ3XL7PdsodCZCYocu7iDgBEi5gD5vE

20,000 bounty sent.



Bounty arrived. Thanks!  :)


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: purelithium on August 12, 2013, 12:40:29 AM
I'm glad that this coin keeps getting noticed! It's great there is support out there again!


Title: Request For Comments: I0coin hardfork proposal
Post by: rsnel on August 12, 2013, 06:36:12 AM
When I took maintainership of I0coin, some issues cropped up which require a hardfork to fix. I propose to apply all hardfork-requiring updates that bitcoin has (as far as I know). Furthermore I'd like to fix a possible issue regarding v2 blocks and to change the difficulty adjustment to be slow (as slow as bitcoin on a per block basis) and symmetric.

The proposed release date of the hardforking version is 2013-08-16, the proposed moment of forking is
  • block 890000XXXXX regarding the difficulty algorithm update
  • 2013-08-23 2013-09-01 0:00 UTC for BIP16/BIP30 and lifting of BDB limits
  • disregard supermajority (95%) v2 blocks: immediately (not an issue, because there won't be one)

I will list all proposed patches verbatim, rationale is listed in commit message and comments:

Code:
commit 84376788462dee4467988ccf6f16eaaf299196b9
Author: Rik Snel <rik@snel.it>
Date:   Sun Aug 11 14:20:35 2013 +0200

    fix retarget at 890000
    
    I0coins old retarget algorithm is asymmetric; difficulty decrease
    is fast and difficulty increase is slow. This can be abused to
    make a 51% attack more profitable than it should be (thereby
    encouraging it).
    
    This patch changes the retarget algorithm to be on par with
    bitcoin's alogirithm (max factor of 4 every 2016 blocks).
    Since i0coin retargets every 120 blocks, the actual retarget
    factor is 4^(120/2016) = 1.086.
    
    Use integer arithmetic, to make sure that all architectures
    return the exact same answer.

diff --git a/src/main.cpp b/src/main.cpp
index 132ffb4..07339f2 100644
--- a/src/main.cpp
+++ b/src/main.cpp
@@ -1236,24 +1236,52 @@ unsigned int static GetNextWorkRequired(const CBlockIndex* pindexLast, const CBl
 
     // Limit adjustment step
     int64 nActualTimespan = pindexLast->GetBlockTime() - pindexFirst->GetBlockTime();
-    int64 nTwoPercent = nTargetTimespan/50;
     //printf("  nActualTimespan = %"PRI64d"  before bounds\n", nActualTimespan);
 
-    if (nActualTimespan < nTargetTimespan)  //is time taken for a block less than 3minutes?
-    {
-         //limit increase to a much lower amount than dictates to get past the pump-n-dump mining phase
-        //due to retargets being done more often it also needs to be lowered significantly from the 4x increase
-        if(nActualTimespan<(nTwoPercent*16)) //less than a minute?
-            nActualTimespan=(nTwoPercent*45); //pretend it was only 10% faster than desired
-        else if(nActualTimespan<(nTwoPercent*32)) //less than 2 minutes?
-            nActualTimespan=(nTwoPercent*47); //pretend it was only 6% faster than desired
-        else
-            nActualTimespan=(nTwoPercent*49); //pretend it was only 2% faster than desired
+    // assymmetric retarget (slow difficulty rise / fast difficulty drop) can be
+    // abused to make a 51% attack more profitable than it should be,
+    // therefore we adopt (starting at block 890000) a symmetric algorithm based
+    // on bitcoin's algorithm.
+    //
+    // we retarget at most by a factor of 4^(120/2016) = 1.086
+
+    if (height < 890000) {  // use the old retarget algorithm
+       int64 nTwoPercent = nTargetTimespan/50;
+       if (nActualTimespan < nTargetTimespan)  //is time taken for a block less than 3minutes?
+       {
+            //limit increase to a much lower amount than dictates to get past the pump-n-dump mining phase
+            //due to retargets being done more often it also needs to be lowered significantly from the 4x increase
+            if(nActualTimespan<(nTwoPercent*16)) //less than a minute?
+               nActualTimespan=(nTwoPercent*45); //pretend it was only 10% faster than desired
+            else if(nActualTimespan<(nTwoPercent*32)) //less than 2 minutes?
+                nActualTimespan=(nTwoPercent*47); //pretend it was only 6% faster than desired
+            else
+                nActualTimespan=(nTwoPercent*49); //pretend it was only 2% faster than desired
+
+            //int64 nTime=nTargetTimespan-nActualTimespan;
+            //nActualTimespan = nTargetTimespan/2;
+        }
+        else if (nActualTimespan > nTargetTimespan*4)   nActualTimespan = nTargetTimespan*4;
+    } else { // new algorithm
+        // use integer aritmmetic to make sure that
+        // all architectures return the exact same answers,
+        // so instead of:
+        //
+        //  foo < bar/1.086     we do   foo < (1000*bar)/1086
+        //  foo = bar/1.086     we do   foo = (1000*bar)/1086
+        //  foo > bar*1.086     we do   foo > (1086*bar)/1000
+        //  foo = bar*1.086     we do   foo = (1086*bar)/1000
+        //
+        // (parentheses to stress desired operator precedence)
+        //
+        // risk of overflow? no way; bar is quite small and
+        // we have it under control, it is defined as 3*60*60
 
-        //int64 nTime=nTargetTimespan-nActualTimespan;
-        //nActualTimespan = nTargetTimespan/2;
+        if (nActualTimespan < (1000*nTargetTimespan)/1086)
+            nActualTimespan = (1000*nTargetTimespan)/1086;
+        else if (nActualTimespan > (1086*nTargetTimespan)/1000)
+            nActualTimespan = (1086*nTargetTimespan)/1000;
     }
-    else if (nActualTimespan > nTargetTimespan*4)   nActualTimespan = nTargetTimespan*4;
 
     // Retarget
     CBigNum bnNew;

Code:
commit d760944021104f81cc732a9a2f9891c10195ed39
Author: Rik Snel <rik@snel.it>
Date:   Sun Aug 11 14:09:18 2013 +0200

    Enable BIP16 for I0coin on 2013-08-23 0:00 UTC
    
    BIP16 is Pay to Script Hash (P2SH). Which may or may not
    be useful in the future.

diff --git a/src/main.cpp b/src/main.cpp
index 132ffb4..d3a9e73 100644
--- a/src/main.cpp
+++ b/src/main.cpp
@@ -1742,8 +1742,9 @@ bool CBlock::ConnectBlock(CValidationState &state, CBlockIndex* pindex, CCoinsVi
         }
     }
 
-    // when will BIP16 be active in I0C? I have no clue. Set it to INT64_MAX for now.
-    int64 nBIP16SwitchTime = 0x7fffffffffffffffLL; //from Bitcoin: 1333238400;
+    // BIP16 will be enabled for I0coin on 2013-08-23 0:00 UTC
+    // date -d "2013-08-23 0:00 UTC" +"%s"
+    int64 nBIP16SwitchTime = 1377216000;
     bool fStrictPayToScriptHash = (pindex->nTime >= nBIP16SwitchTime);
 
     unsigned int flags = SCRIPT_VERIFY_NOCACHE |

Code:
commit cabccac5946f48e92b9e3b34b3b15acc546642f0
Author: Rik Snel <rik@snel.it>
Date:   Sun Aug 11 14:05:03 2013 +0200

    Enable BIP30 for I0coin on 2013-08-23 0:00 UTC
    
    BIP30 disallows duplicate (coinbase) transactions. Creating
    a duplicate coinbase transaction destroys unspent coins from
    the original coinbase transaction.

diff --git a/src/main.cpp b/src/main.cpp
index 132ffb4..5153561 100644
--- a/src/main.cpp
+++ b/src/main.cpp
@@ -1721,8 +1721,9 @@ bool CBlock::ConnectBlock(CValidationState &state, CBlockIndex* pindex, CCoinsVi
     //
     // This rule applies to all Bitcoin blocks whose timestamp is after March 15, 2012, 0:00 UTC.
     //
-    // When should this happen in i0coin? Not yet...
-    int64 nBIP30SwitchTime = 0x7fffffffffffffffLL;
+    // BIP30 for I0coin will go into effect on 2013-08-23 0:00 UTC
+    // date -d "2013-08-23 0:00 UTC" +"%s"
+    int64 nBIP30SwitchTime = 1377216000;
     bool fEnforceBIP30 = (pindex->nTime > nBIP30SwitchTime);
 
     // after BIP30 is enabled for some time, we could make the same change

Code:
commit a6caa06588b691013f0507ed5ee9aa36b6137b7c
Author: Rik Snel <rik@snel.it>
Date:   Sun Aug 11 21:45:35 2013 +0200

    Stop enforcing BDB limits on 2013-08-23 0:00 UTC
    
    Well, I0coin never reached those BDB limits, but since all
    BDB based clients will disappear from the new chain, we
    can safely drop compatibility kludges.

diff --git a/src/main.cpp b/src/main.cpp
index 132ffb4..a639a00 100644
--- a/src/main.cpp
+++ b/src/main.cpp
@@ -2247,9 +2247,9 @@ bool CBlock::CheckBlock(CValidationState &state, int nHeight, bool fCheckPOW, bo
     // Bitcoin had a chain split because of incompatible changes in 0.8.x
     // old releases had some difficulty with large blocks with many transactions
     //
-    // for now, in I0coin, we enforce BDB limits to keep the chain from splitting
-    // Special short-term limits to avoid 10,000 BDB lock limit:
-    if (true)
+    // on 2013-08-23 0:00 UTC we will stop enforcing BDB limits
+    // date -d "2013-08-23 0:00 UTC" +"%s" = 1377216000
+    if (GetBlockTime() < 1377216000)
     {
         // Rule is: #unique txids referenced <= 4,500
         // ... to prevent 10,000 BDB lock exhaustion on old clients
@@ -4376,9 +4376,9 @@ CBlockTemplate* CreateNewBlock(CReserveKey& reservekey)
     // Bitcoin had a chain split because of incompatible changes in 0.8.x
     // old releases had some difficulty with large blocks with many transactions
     //
-    // for now, in I0coin, we enforce BDB limits to keep the chain from splitting
-    // Special short-term limits to avoid 10,000 BDB lock limit:
-    if (true)
+    // on 2013-08-23 0:00 UTC we will stop enforcing BDB limits
+    // date -d "2013-08-23 0:00 UTC" +"%s" = 1377216000
+    if (GetAdjustedTime() < 1377216000)
         nBlockMaxSize = std::min(nBlockMaxSize, (unsigned int)(MAX_BLOCK_SIZE_GEN));
 
     // How much of the block should be dedicated to high-priority transactions,

Code:
commit c546f77099265587a5519db1a5fb1773d0b0eea3
Author: Rik Snel <rik@snel.it>
Date:   Sun Aug 11 14:27:14 2013 +0200

    Don't enforce v2 blocks.
    
    Version 2 blocks have their height encoded in the first 4 bytes of
    the coinbase input script. getauxblock produces v1 blocks.
    
    This can be enabled later if getauxblock is updated and most miners
    produce v2 blocks. (desireable, but it won't cause a hard fork, since
    95% of the miners automatically produce the best chain)

diff --git a/src/main.cpp b/src/main.cpp
index 132ffb4..079c691 100644
--- a/src/main.cpp
+++ b/src/main.cpp
@@ -2349,6 +2349,9 @@ bool CBlock::AcceptBlock(CValidationState &state, CDiskBlockPos *dbp)
         if (!Checkpoints::CheckBlock(nHeight, hash))
             return state.DoS(100, error("AcceptBlock() : rejected by checkpoint lock-in at %d", nHeight));
 
+       // I0coin currently doesn't enforce 2 blocks, since merged mining
+       // produces v1 blocks and normal mining should produce v2 blocks.
+#if 0
         // Reject block.nVersion=1 blocks when 95% (75% on testnet) of the network has upgraded:
         if ((nVersion&0xff) < 2)
         {
@@ -2370,6 +2373,7 @@ bool CBlock::AcceptBlock(CValidationState &state, CDiskBlockPos *dbp)
                     return state.DoS(100, error("AcceptBlock() : block height mismatch in coinbase"));
             }
         }
+#endif
     }
 
     // Write block to history file

Please speak up if you have an opinion on this proposed hardfork. If I proceed, everybody should upgrade before 2013-08-23 0:00 UTC OR block 890000 (whichever is earlier) 2013-09-01 0:00 OR block TO_BE_DETERMINED.

Updates
  • switch difficulty adjustments to integer arithmetic, to make sure all architectures return the exact same answer
  • move deadline to 1 sep (and corresponding block numer) to give everybody more time to upgrade (this change is not reflected in the patches above)


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: K1773R on August 12, 2013, 06:49:36 AM
merging the changes from bitcoin into 1 huge hardfork is a good idea, therefore i agree on the hardfork ;)


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: markm on August 12, 2013, 02:00:39 PM
Why slow difficulty adjustment?

I thought most merged mined coins did some kind of adjustment to be faster than bitcoin in that regard, though maybe that was also how some evidently changed to going down faster than they go up?

GRouPcoin and DeVCoin both use the same system as each other I believe and it seemed to work well. Unless maybe that was the very one that goes down faster than up???

-MarkM-


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: rsnel on August 12, 2013, 02:28:44 PM
Why slow difficulty adjustment?

I thought most merged mined coins did some kind of adjustment to be faster than bitcoin in that regard, though maybe that was also how some evidently changed to going down faster than they go up?

GRouPcoin and DeVCoin both use the same system as each other I believe and it seemed to work well. Unless maybe that was the very one that goes down faster than up???

-MarkM-


A factor of 1.086 allows for a doubling or halving of difficulty over about 1000 blocks (nominal time is a day, so approx 1/2 day for doubling and 2 days for halving). This is already very flexible in my eyes.

I hope a slow adjustment process will lead to less screwing around with the blockchain. If someone with a lot of hashing power wants to increase the difficulty sigificantly, he/she will have to mine a lot of coins and may therefore be motivated to keep supporting the chain.

The designed block rate of I0coin is very high. Even if a large drop of hashing power would occur (say 85%), there would still be a block every 10 minutes. Which is slow, but not unworkable.

So I think 1.086 is fast enough.

If I didn't convince you, please propose a different constant.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: rsnel on August 12, 2013, 04:20:03 PM
One more thing:

It is not be the smartest idea to rely on floating point math (*1.086). It may lead to every floating point implementation having its own blockchain... I will update the patch to use integer math.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: pyra-proxy on August 12, 2013, 05:27:25 PM
One more thing:

It is not be the smartest idea to rely on floating point math (*1.086). It may lead to every floating point implementation having its own blockchain... I will update the patch to use integer math.

This is a good thing.  Nice foresight!


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: CYPER on August 13, 2013, 04:22:04 PM
Wow, this coin is alive  :o

Can you help me with 2 questions:

1 - I read that the i0coin will have to download the entire BTC blockchain. Can I just copy it over as I already have it (I update my BTC client daily). Or even better can I point i0coin to the BTC folder, so they share the blockchain?
2 - In regards to that hardfork - what does that mean in simple terms? Do I have to do something, so I don't lose my coins?

Thank you.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: rsnel on August 13, 2013, 05:00:18 PM
Hi CYPER,

Wow, this coin is alive  :o

Can you help me with 2 questions:

1 - I read that the i0coin will have to download the entire BTC blockchain. Can I just copy it over as I already have it (I update my BTC client daily). Or even better can I point i0coin to the BTC folder, so they share the blockchain?
2 - In regards to that hardfork - what does that mean in simple terms? Do I have to do something, so I don't lose my coins?

Thank you.

1. The I0coin client needs to download the entire I0coin blockchain, it goes automatically. The I0coin blockchain is different from the Bitcoin blockchain because the genesis block differs and the rules (difficulty adjusment, reward etc) are different. The size of the blockchain is about 4GB.

2. You have to upgrade to the version I will release friday (unless there will be showstopping issues or complaints by the community; a successfull hardfork is only possible if there is agreement on the necessety of the fork), then you will be on the good branch of the fork. I will urge everybody to upgrade, because the new version includes important security enhancements, it is impossible to fix these issues without EVERYONE (sorry for shouting) having to upgrade.

Greetings,

Rik.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: CYPER on August 13, 2013, 05:08:12 PM
Thank you for you swift reply.

I started the client about 30 minutes ago and it is downloading it quite fast: 68 weeks left, which is almost about 1/3rd.
In regards to the new fork - we won't lose our coins from before, right?


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: K1773R on August 13, 2013, 05:10:09 PM
Thank you for you swift reply.

I started the client about 30 minutes ago and it is downloading it quite fast: 68 weeks left, which is almost about 1/3rd.
In regards to the new fork - we won't lose our coins from before, right?
nope, no coins would be lost


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: purelithium on August 14, 2013, 11:52:18 PM
So has doublec committed to the hardfork? I think that's pretty important, as he's the highest profile pool mining i0coin.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: doublec on August 14, 2013, 11:56:20 PM
So has doublec committed to the hardfork? I think that's pretty important, as he's the highest profile pool mining i0coin.
I'll go along with whatever the current coin developer and users prefer. It'll be helpful if there is plenty of time from the release of the code to when it activates. I'm only about 30% of the network though so it'll take time for the new version to get a majority on the network.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: rsnel on August 15, 2013, 05:49:32 AM
So has doublec committed to the hardfork? I think that's pretty important, as he's the highest profile pool mining i0coin.
I'll go along with whatever the current coin developer and users prefer. It'll be helpful if there is plenty of time from the release of the code to when it activates. I'm only about 30% of the network though so it'll take time for the new version to get a majority on the network.

If you say 'plenty of time', you probably mean more than a week. What timespan do you recommend? (2 weeks, month, 2 months?)

The date is not etched in stone yet, but I'd like to release the forking version tomorrow.

Greetings,

Rik.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: doublec on August 15, 2013, 09:23:16 AM
If you say 'plenty of time', you probably mean more than a week. What timespan do you recommend? (2 weeks, month, 2 months?)
I'd need a week to schedule testing and upgrade but whatever you think is best beyond that.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: rsnel on August 15, 2013, 10:14:53 AM
Thanks, doublec, for your comment.

I think it is best to prolong the the transition period by a week and a few days. So, the deadline will be September 1st.

Release is scheduled for tomorrow.
 


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: rsnel on August 16, 2013, 05:47:05 AM
i0coin-0.8.3-2 is released, it contains the changes we discussed here, please upgrade as soon as possible


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: purelithium on August 17, 2013, 03:20:49 AM
I feel like there needs to be a larger announcement than this small post buried in this thread, which is only marked as i0coin by the short name. People searching for an "i0coin" topic by title alone won't find.

rsnel, consider creating a new announcement thread with an informative title to inform the wider user base.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: rsnel on August 17, 2013, 06:14:05 AM
I feel like there needs to be a larger announcement than this small post buried in this thread, which is only marked as i0coin by the short name. People searching for an "i0coin" topic by title alone won't find.

rsnel, consider creating a new announcement thread with an informative title to inform the wider user base.

It probably wouldn't hurt, will do. Thanks for the suggestion.

On my seednode:
Code:
$ ~/src/i0coin/src/i0coind getpeerinfo | grep -e subver | sort | uniq -c
      1         "subver" : "",
     12         "subver" : "/Satoshi:0.8.3/",
      9         "subver" : "/Satoshi:0.8.3.1/",
      9         "subver" : "/Satoshi:0.8.3.4/",



Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: tiker on September 03, 2013, 03:04:06 PM
Just an FYI, the windows GUI version shows "Bitcoin" on the title of the debug window instead of I0coin.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: rsnel on September 03, 2013, 07:01:05 PM
Just an FYI, the windows GUI version shows "Bitcoin" on the title of the debug window instead of I0coin.

Thanks for spotting it. Update pushed to git repository. The next release will have I0coin in the title of the debug window.

While we're at it:
Code:
$ ~/src/i0coin/src/i0coind getpeerinfo | grep -e subver | sort | uniq -c
      2         "subver" : "",
      6         "subver" : "/Satoshi:0.8.3/",
      5         "subver" : "/Satoshi:0.8.3.1/",
     28         "subver" : "/Satoshi:0.8.3.4/",

I run an old version to monitor the fork. Currently the chain hasn't forked, because there are no blocks added to the chain about which there is disagreement. Anybody could cause a fork at this moment, by creating a block with a duplicate coinbase tx. It will be accepted by all old versions, but not by the new, recommended version.

A split will occur for sure after block 895000, because the difficulty adjusment calculation will change. Please upgrade as soon as possible.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: rsnel on September 04, 2013, 08:00:26 PM
Just an FYI, the windows GUI version shows "Bitcoin" on the title of the debug window instead of I0coin.

Also FYI: I just released version 0.8.4-2 which contains fixes from bitcoin, more renamings of Bitcoin to I0coin and working logos in the windows installer. See the website http://i0coin.snel.it/ for the downloads.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: Vlad2Vlad on September 12, 2013, 11:22:04 PM
So is this THE official i0Coin thread?

Does anybody wanna sell some i0Coin?   I've got a thing for old school coins and this is one of the originals.  There is some risk here since its not even on an exchange yet but if I can get a favorable price I would like to buy some.  TIA!


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: Vlad2Vlad on September 12, 2013, 11:24:20 PM
I'll announce i0Coin is alive on my threads and on Cryptsy.

I'm pretty loud so some people should take notice.  But I need to know which thread is the main i0Coin thread cause there's a few. 

I'm confused myself so someone let me know which tread to put out.  There's no reason why this coin should have such few hits while my NUGGETS thread gets way more and its not even a real coin.  Lol


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: CYPER on September 13, 2013, 12:09:29 AM
That is the original thread with the proposed idea: https://bitcointalk.org/index.php?topic=36425.0

Btw I found this piece of information: https://bitcointalk.org/index.php?topic=46774.0

Maybe that was the rate I bought mine at. I was mistaken in thinking I have 15K. I have around 11K, so it looks like I spent around 12-13BTC for them.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: rsnel on September 13, 2013, 04:02:31 AM
I'll announce i0Coin is alive on my threads and on Cryptsy.

I'm pretty loud so some people should take notice.  But I need to know which thread is the main i0Coin thread cause there's a few.  

I'm confused myself so someone let me know which tread to put out.  There's no reason why this coin should have such few hits while my NUGGETS thread gets way more and its not even a real coin.  Lol

I'd say that this thread is the official one... and the official homepage is http://i0coin.snel.it/

Edit: Vlad2Vlad: I like the idea of generating some publicity for I0coin..., the best publicity will be a re-introduction in the exchanges. (for example: I got to know XPM because I saw it in vircurex)


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: markm on September 13, 2013, 08:57:57 AM
I did git pull to get latest code, restarted daemon with -reindex as well as -rescan, but before I went to sleep it had reached block 895084 and now quite a few hours later it is at block 895086. It has eight connections.

What block numbers are other people up to? How many people are actually running the latest code?

-MarkM-


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: markm on September 13, 2013, 09:04:54 AM
Well it is running through its hosts file trying and failing to find more connections. Maybe it already marked as misbehaving all the people who are actually running the latest code.

Guess I will try deleting its copy of the blockchain and let it get it fresh from someone.

Presumably its checkpoints sehould prevent it getting the wrong one that way?

-MarkM-


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: rsnel on September 13, 2013, 09:15:50 AM
I did git pull to get latest code, restarted daemon with -reindex as well as -rescan, but before I went to sleep it had reached block 895084 and now quite a few hours later it is at block 895086. It has eight connections.

What block numbers are other people up to? How many people are actually running the latest code?

-MarkM-


You need to switch to branch i0coin-0.8.x (this is the default now, but since you cloned as one of the first people, you are on master, which still needs to be merged with upcoming bitcoin 0.9.x).

Code:
git checkout -B i0coin-0.8.x origin/i0coin-0.8.x

Better yet: do a fresh clone.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: markm on September 13, 2013, 09:44:09 AM
So if I delete my git repo clone entirely, and clone from scratch, I get a different branch?

Isn't the default branch the right one? How did I get onto the wrong one?

Normally I just do git pull and it is up to the releasers, the people controlling the github repo, to ensure the correct code is not off in some branch somewhere but is right up front where it is what people naturally get when they pull...

-MarkM-


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: rsnel on September 13, 2013, 09:52:33 AM
So if I delete my git repo clone entirely, and clone from scratch, I get a different branch?

Isn't the default branch the right one? How did I get onto the wrong one?

Normally I just do git pull and it is up to the releasers, the people controlling the github repo, to ensure the correct code is not off in some branch somewhere but is right up front where it is what people naturally get when they pull...

-MarkM-


Yes, a fresh clone gives you the right branch.

When you originally cloned, the default (github/HEAD) was set to 'master'. Later I switched the default to branch i0coin-0.8.x, so all recent clones have the right branch as 'remote tracking branch', but you still track master. So you either have to create branch i0coin-0.8.x and have it track my git repository or reclone.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: markm on September 13, 2013, 09:55:47 AM
So what happens when you upgrade to a new version?

Everyone is tricked onto a wrong branch again by their default normal pull being stuck in the old version?

Isn't the point of default/master that regardless of whether the correct/right one to get has to be forced back to an old version due to a problem, or is a new version, the master always has the right one people should be grabbing at any particular moment?

-MarkM-


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: rsnel on September 13, 2013, 10:58:40 AM
So what happens when you upgrade to a new version?

Everyone is tricked onto a wrong branch again by their default normal pull being stuck in the old version?

Isn't the point of default/master that regardless of whether the correct/right one to get has to be forced back to an old version due to a problem, or is a new version, the master always has the right one people should be grabbing at any particular moment?

-MarkM-


The problem is that I follow bitcoin development closely. There are two branches of interest: bitcoin/master (from which bitcoin-0.9.0 will be split off) and the stable series. Currently, I want people to track the stable branch, so I set the github/HEAD to branch i0coin-0.8.x.

By the time I want people to track another stable branch, everybody will have your problem. Maybe I should create a new repository if I start a new stable branch.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: markm on September 13, 2013, 11:08:24 AM
I don't see a problem, it's easy to switch branches.

When you do git pull it does not TELL YOU to switch branches.

There are now how many tens of projects / coins on github?

How many hundreds of coins in future, or hundreds of projects on github if you include things other than coins, all of which you need to keep up to date?

So, you go to your source/development directory, and manually or otherwise you basically do "for project in is-a-git-project do git pull".

It is in doing a git pull in each project you have source code for that you discover which, if any, of the things that you compiled from github source need to be recompiled.

Ideally you'd even automate the entire build and install process, looping over all source doing pull if its git, update if its SVN, whatever, based on what version system the source code comes from, and rebuilding whichever find they have downloaded new code.

That is same thing I did for I0Coin: I wondered if I have latest version, so I did a pull to find out, sure enough it pulled new code, so I built it, installed it, and ran around installing it on all machines that run it all over the net, shutting down any currently running daemon to upload the new binary then starting it back up again.

Whatever is alphabetically next after I0Coin might be next if i did this in formal sequence, like okay, so much for I0Coin, next cd to ixcoin-git, do a git pull, if it pulls new code then build and install that and run around installing that everywhere. And so on, by the time I am done the alphabet maybe when i get back to the top, bitcoin-git or whatever, I will find that already has new code and embark on another loop through all the source code directories.

Maybe there needs to be some convention such that when you do a git pull and that would pull the wrong thing, it tells you "this branch is obsolete, please instead pull XXXXX".

But except for one or two weird tricksy sneaky projects that screw your pulls up like this, normally doing a pull gets you the latest code, because if they move to a new version they make that version be what you now get when you do your normal usual pull you've been doing all those/these years.

Users who do not want latest code manually select some non-head (non-master, non-default) branch that is deliberately set up not to go to new versions but only to get bugfixes, then they too can just pull automatically, confident that on their non-main branch doing so will only give them bigfixes for the old version they have deliberately stuck themselves on.

-MarkM-


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: almightyruler on September 13, 2013, 03:22:20 PM
I'm trying to build this under FreeBSD, but I'm running into this issue:

g++ -c -O2 -pthread -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -g -DBOOST_SPIRIT_THREADSAFE -D_FILE_OFFSET_BITS=64 -I/nas01/coins/i0coin/src/i0coin-i0coin-0.8.x/src -I/nas01/coins/i0coin/src/i0coin-i0coin-0.8.x/src/obj -I/usr/local/include -I/usr/local/include/db48 -DUSE_IPV6=0 -I/nas01/coins/i0coin/src/i0coin-i0coin-0.8.x/src/leveldb/include -I/nas01/coins/i0coin/src/i0coin-i0coin-0.8.x/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/init.d -o obj/init.o init.cpp
init.cpp: In function 'bool AppInit2(boost::thread_group&)':
init.cpp:534: error: no matching function for call to 'min(int&, unsigned int)'
/usr/local/include/boost/asio/error.hpp: At global scope:
/usr/local/include/boost/asio/error.hpp:244: warning: 'boost::asio::error::system_category' defined but not used
/usr/local/include/boost/asio/error.hpp:246: warning: 'boost::asio::error::netdb_category' defined but not used
/usr/local/include/boost/asio/error.hpp:248: warning: 'boost::asio::error::addrinfo_category' defined but not used
/usr/local/include/boost/asio/error.hpp:250: warning: 'boost::asio::error::misc_category' defined but not used
/usr/local/include/boost/system/error_code.hpp:214: warning: 'boost::system::posix_category' defined but not used
/usr/local/include/boost/system/error_code.hpp:215: warning: 'boost::system::errno_ecat' defined but not used
/usr/local/include/boost/system/error_code.hpp:216: warning: 'boost::system::native_ecat' defined but not used
gmake: *** [obj/init.o] Error 1


Here's the area in init.cpp around the error:

531:    // Make sure enough file descriptors are available
532:    int nBind = std::max((int)mapArgs.count("-bind"), 1);
533:    nMaxConnections = GetArg("-maxconnections", 125);
534:    nMaxConnections = std::max(std::min(nMaxConnections, FD_SETSIZE - nBind - MIN_CORE_FILEDESCRIPTORS), 0);


(source downloaded from https://github.com/rsnel/i0coin/archive/i0coin-0.8.x.zip along with fixed makefile.unix from http://pastebin.com/ncnG57t8 )

I've compiled 20+ altcoins in the past few days without too many problems, but they're pretty much all clones of Litecoin. I guess the i0coin source is older since it's based on Bitcoin and started development before the mad rush of search-replace-release altcoins?

Any ideas on how to fix this error? I know C, but not C++.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: rsnel on September 13, 2013, 05:13:56 PM
I'm trying to build this under FreeBSD, but I'm running into this issue:

g++ -c -O2 -pthread -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -g -DBOOST_SPIRIT_THREADSAFE -D_FILE_OFFSET_BITS=64 -I/nas01/coins/i0coin/src/i0coin-i0coin-0.8.x/src -I/nas01/coins/i0coin/src/i0coin-i0coin-0.8.x/src/obj -I/usr/local/include -I/usr/local/include/db48 -DUSE_IPV6=0 -I/nas01/coins/i0coin/src/i0coin-i0coin-0.8.x/src/leveldb/include -I/nas01/coins/i0coin/src/i0coin-i0coin-0.8.x/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/init.d -o obj/init.o init.cpp
init.cpp: In function 'bool AppInit2(boost::thread_group&)':
init.cpp:534: error: no matching function for call to 'min(int&, unsigned int)'
/usr/local/include/boost/asio/error.hpp: At global scope:
/usr/local/include/boost/asio/error.hpp:244: warning: 'boost::asio::error::system_category' defined but not used
/usr/local/include/boost/asio/error.hpp:246: warning: 'boost::asio::error::netdb_category' defined but not used
/usr/local/include/boost/asio/error.hpp:248: warning: 'boost::asio::error::addrinfo_category' defined but not used
/usr/local/include/boost/asio/error.hpp:250: warning: 'boost::asio::error::misc_category' defined but not used
/usr/local/include/boost/system/error_code.hpp:214: warning: 'boost::system::posix_category' defined but not used
/usr/local/include/boost/system/error_code.hpp:215: warning: 'boost::system::errno_ecat' defined but not used
/usr/local/include/boost/system/error_code.hpp:216: warning: 'boost::system::native_ecat' defined but not used
gmake: *** [obj/init.o] Error 1


Here's the area in init.cpp around the error:

531:    // Make sure enough file descriptors are available
532:    int nBind = std::max((int)mapArgs.count("-bind"), 1);
533:    nMaxConnections = GetArg("-maxconnections", 125);
534:    nMaxConnections = std::max(std::min(nMaxConnections, FD_SETSIZE - nBind - MIN_CORE_FILEDESCRIPTORS), 0);


(source downloaded from https://github.com/rsnel/i0coin/archive/i0coin-0.8.x.zip along with fixed makefile.unix from http://pastebin.com/ncnG57t8 )

I've compiled 20+ altcoins in the past few days without too many problems, but they're pretty much all clones of Litecoin. I guess the i0coin source is older since it's based on Bitcoin and started development before the mad rush of search-replace-release altcoins?

Any ideas on how to fix this error? I know C, but not C++.

please try the fix presented here: https://github.com/bitcoin/bitcoin/pull/2695



Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: almightyruler on September 14, 2013, 01:43:56 AM
I'm trying to build this under FreeBSD, but I'm running into this issue:
[...]

please try the fix presented here: https://github.com/bitcoin/bitcoin/pull/2695



Yep, add one tiny little cast and it compiles. Thanks for that.

Out of curiosity, how did you find that fix? Is there a way to search github to see when that specific source line has been changed?


============


edit: had further issues with errors, many instances of undefined reference to `boost::chrono::steady_clock::now()'

Fix is to add boost_chrono as a library in makefile.unix


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: rsnel on September 14, 2013, 06:34:10 AM
I'm trying to build this under FreeBSD, but I'm running into this issue:
[...]

please try the fix presented here: https://github.com/bitcoin/bitcoin/pull/2695



Yep, add one tiny little cast and it compiles. Thanks for that.

Out of curiosity, how did you find that fix? Is there a way to search github to see when that specific source line has been changed?


============


edit: had further issues with errors, many instances of undefined reference to `boost::chrono::steady_clock::now()'

Fix is to add boost_chrono as a library in makefile.unix

I googled for: bitcoin freebsd std::min nMaxConnections
as I expected std:min to be the problem and bitcoin having the same problem. (first I checked the litecoin source, and it doesn't have nMaxConnections in init.cpp).



Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: No_2 on September 16, 2013, 08:42:14 AM
IOC seems to have appeared on Vircurex.

Can't find any announcements on this in the threads however?


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: Kumala on September 16, 2013, 09:01:26 AM
I posted it on two threads,

here: https://bitcointalk.org/index.php?topic=294490.0
and here: https://bitcointalk.org/index.php?topic=224744.80


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: markm on September 16, 2013, 09:02:14 AM
Oh good. I wonder why GRouPcoin didn't also appear though since bitparking picked up both of them at about the same time for its merged mining pool so most likely anyone mining I0Coins is also mining GRouPcoins.

-MarkM-


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: No_2 on September 16, 2013, 11:38:28 PM
Can someone answer my questions or point me at useful sources to answer them:

1. How many IOC coins have currently been mined?

2. What is the planned cap or method of growth of supply?

3. What is the approximate block completion time?

4. Can anyone point me at a mining calculator so I can calculate my mining abilities - I can mine SHA-256 at 1200MHs (or scrypt at 1200KHs).



Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: markm on September 17, 2013, 12:14:50 AM
The useful source is main.cpp in the src directory of the git repo.

I am not sure what the URL is of the git repo offhand but a search on github should find it presumably.

-MarkM-


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: steelhouse on September 17, 2013, 01:02:05 AM
I0C - 90 sec per block, retarget every 120 blocks or every 3 hours, 960 a day                  
Date   Block   Coins   Inflation   Reward   Coins per day   
12/11/11   150639   7230672   233%   48   46080   
2/20/12   218799   10500000   80%   24   23040   
9/30/12   437339   15750000   27%   12   11520   
5/12/13   656859   18375000   11%   6   5760   
12/21/13   875399   19687500   5%   3   2880   
8/1/14   1093939   20343750   3%   1.5   1440   
3/12/15   1312479   20671875   1%   0.75   720   

I made the above table over a year ago.  According to Vircurex we are at block 901213.

Thus the block reward should be 3 and we now have a coin with less annual inflation than the U.S. dollar.  Note, the dates are wrong because the coin stopped for awhile. Can someone confirm that the block reward is 3?


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: markm on September 17, 2013, 01:16:17 AM
Yes it has been three for a while now.

Are you sure it ever actually stopped?

-MarkM-


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: smeagol on September 22, 2013, 11:45:36 AM
i0coin now has a devtome article!
http://devtome.com/doku.php?id=i0coin


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: ayayay on September 24, 2013, 11:59:25 PM
may have recovered my lost  iocoin wallet.dat file   now where does it go   i'm do a search for iocoin wallet on my pc and find nothing the client is up and running


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: markm on September 25, 2013, 12:08:49 AM
Most coins are alike in that they have a wallet.dat file in their data directory. Most likely put their data directory in much the same place too, but named after the particular coin whose data directory it is.

For example on Linux, ~/.bitcoin, ~/.i0coin, etc.

-MarkM-


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: ayayay on September 25, 2013, 12:31:54 AM
wallet.dat file currupt salvage fail    any way to fix


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: sal002 on September 25, 2013, 12:44:26 AM
Anyone know the current block reward and target block time?


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: rsnel on September 25, 2013, 06:54:35 AM
wallet.dat file currupt salvage fail    any way to fix

Did you try pywallet.py (https://github.com/jackjack-jj/pywallet) with --recov_device pointed at the old wallet.dat?

If it fails, I'd like to take a look at your wallet, unfortunately this raises severe trust issues, since I could run off with your coins.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: ayayay on September 25, 2013, 12:23:19 PM
Please take a look at wallet-  I trust you will not run off with my coins.-


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: nullbitspectre1848 on September 26, 2013, 03:47:36 PM
Can someone please tell me where I can actually find a windows binary for this?  All the links are dead, and I can't compile anything atm.

Thanks.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: rsnel on September 26, 2013, 07:48:13 PM
Hi,

I'm sorry, but my hosting provider had big problems yesterday. I am currently uploading backups to the replacement server. i0coin.snel.it should appear shortly.

Greetings,

Rik.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: aa on October 10, 2013, 05:04:30 AM
Added I0coin info to this page: http://www.lurkmore.com/wiki/Cryptocurrency_information_and_wallet_client_downloads


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: Anonylz on October 11, 2013, 06:57:05 AM
i0coin now has a devtome article!
http://devtome.com/doku.php?id=i0coin

the blocktarget time of your article is incorrect


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: jubalix on October 13, 2013, 11:23:15 AM
I see I0coin is doubling in value recently


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: smeagol on October 19, 2013, 01:19:05 PM
Can anyone help resurrect devcoin to bitcoin 0.8?


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: No_2 on October 21, 2013, 09:37:24 AM
@rsnel

Gliss has said he will add I0C to his tracker at http://coinmarketcap.com/ (http://coinmarketcap.com/) if somone can point him at a block explorer for it:

...

Do you have any plans to add IOC which had recently been revived and is also back on Vircurex, see here:

https://bitcointalk.org/index.php?topic=268228.0

I will add if there's a block explorer with quantity info...

See main thread:

https://bitcointalk.org/index.php?topic=199685.0 (https://bitcointalk.org/index.php?topic=199685.0)


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: jubalix on October 24, 2013, 08:54:26 AM
how many coin per block?


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: umairsaleem010 on October 31, 2013, 02:16:40 AM
My coins are gone after updating.  >:(


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: No_2 on November 27, 2013, 08:54:41 AM
I0C is now on coinmarketcap.com (http://coinmarketcap.com/).


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: tazman on November 28, 2013, 01:57:11 AM
I0C is now on coinmarketcap.com (http://coinmarketcap.com/).

Now we can watch it grow!!!


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: lightlord on November 29, 2013, 05:02:06 AM
i0coin is now at:

http://vircurex.com/
http://coinmarketcap.com.
http://coinchoose.com/

I PM'ed both https://bter.com/ & https://www.cryptsy.com/

If things turn out well, we will see it on even more exchanges.

Shall i0coin be successful!


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: No_2 on November 29, 2013, 10:24:06 AM
Just noticed its on http://www.cryptocoincharts.info/ (http://www.cryptocoincharts.info/) too.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: m00x! on November 30, 2013, 11:40:17 PM
I0C just broke $1,000,000 in value on coinmarketcap.com.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: kr105 on December 15, 2013, 07:29:20 AM
My little son grew up!


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: rsnel on December 15, 2013, 09:10:05 PM
My little son grew up!

Yes! And now it's at version 0.8.6-1.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: CrayjeksAjek on February 16, 2014, 06:22:35 PM
Any pools besides bitparking?


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: rizzn on April 02, 2014, 11:40:58 AM
I arrived on this thread through http://mmpool.org/, so that's another pool.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: sandbox on April 03, 2014, 11:55:46 PM
I arrived on this thread through http://mmpool.org/, so that's another pool.

mmpool.org is bitparking



Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: m00x! on April 04, 2014, 12:05:15 AM
Any pools besides bitparking?

P2Pool, some brief instructions in first post here:

https://bitcointalk.org/index.php?topic=268228.0


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: ExtremeDice on April 06, 2014, 05:00:24 AM
New dice game launched for I0 https://i0c.xtremedice.com/ (https://i0c.xtremedice.com/)

Also the site has a invest option now has a invest option. Let your I0C coins make you more I0C coins.

You can invest and devest instantly. I charge no fees as this time since the invest option is still in beta.

Cheers


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: COMKORT on April 15, 2014, 07:46:05 AM
https://i.imgur.com/UKkuLO6.png (https://bitcointalk.org/index.php?topic=550598.msg5990419#msg5990419)


Good News

I0coin (I0C) was added COMKORT EXCHANGE


https://comkort.com/market/trade/i0c_btc

https://comkort.com/market/trade/i0c_ltc

https://comkort.com/market/trade/i0c_doge

GOOD LUCK & HAPPY TRADING



Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: cinnamon_carter on June 26, 2014, 10:44:10 PM
I am a little late here but doing some research

Is there currently a working abe block crawler for i0 coin or am I on my own ?


(to the guy above that lost his coins if you need help in how to recover them I did a post about how to fix just about any type of wallet problem I can direct you to it if you never got your coins, it will not crack a password lost but everything else it can correct )


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: mblados on August 16, 2014, 01:57:42 PM

So is this coin Dead?  ??? thread seem to be left.


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: K1773R on August 16, 2014, 06:59:26 PM

So is this coin Dead?  ??? thread seem to be left.
sry, this isnt a "get rich quick scam coin". wrong thread ;)


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: cinnamon_carter on August 16, 2014, 07:14:16 PM
no , not dead at all, just because older established or more professional developers and coins

dont have a thousand fake accounts bump and  spam the thread 7 days a week does not mean anything at all,

look at all the new coin scams , 21 days proof of work , 14 days proof of work, 3 days proof of work ,

some of this garbage actually has a lot of exposure and all sorts of 'experts' who were not even around  year ago trying to lead other people around with a hook in thier nose to buy into their scams.

some of them have hundreds of pages , the fact that it is fake and phony is obvious

I always liked i0 and iX since they have been around and being merged with bitcoin cannot be 51% killed by someone who owns a few neptunes.....

quite alive


Title: Re: [ANN][I0C] Resurrection, memory problems and instabilitiy fixed!
Post by: crackfoo on August 22, 2016, 02:40:43 PM
Hi,

We've added I0C to the miners multipool: www.zpool.ca

Cheers