New Ixcoin fork -> I0coin

[Acejam]

Is anyone else's Win64 client crashing for them in -server mode? I'm running i0coin.exe in -server mode and have my i0coin.conf setup correctly with the following:

rpcuser=user
rpcpassword=pass
rpcallowip=192.168.1.*
rpcport=7332
server=1

Every hour (or less) I notice that my miners return "Problem communicating with Bitcoin RPC". I'm 100% certain that I'm hitting the correct i0coin instance, since I've already managed to generate 4 confirmed blocks, and they are now in my wallet.

Killing i0coin.exe and then restarting it seems to fix the issue. Anyone reason as to why this might occur? Right now I have 14 connections, but I had ~52 connections earlier.

[bitcool]

Just curious, is there one place shows all variants of bitcoin forks?

There's a thread, ALL IN CAPS in the Bitcoin discussion forum

great find, thanks a lot.
so many forks, so little improvements... why are those people so unimaginative?
oh wait, maybe because they are ... copycats?  

[tacotime]

difficulty: 8m

You mean block 8k and difficulty 256?

no, make i1coin start at 8m so everyone at least has a chance.

[Digigami]

Is anyone else's Win64 client crashing for them in -server mode? I'm running i0coin.exe in -server mode and have my i0coin.conf setup correctly with the following:

rpcuser=user
rpcpassword=pass
rpcallowip=192.168.1.*
rpcport=7332
server=1

Every hour (or less) I notice that my miners return "Problem communicating with Bitcoin RPC". I'm 100% certain that I'm hitting the correct i0coin instance, since I've already managed to generate 4 confirmed blocks, and they are now in my wallet.

Killing i0coin.exe and then restarting it seems to fix the issue. Anyone reason as to why this might occur? Right now I have 14 connections, but I had ~52 connections earlier.

Not sure if it's related to your miners connection issues or not, but as far as the fewer outside connections, likely a large number of nodes are getting banned from IRC servers.. see here

https://bitcointalk.org/index.php?topic=37564.msg461616#msg461616

[gamer4156]

trading has started on the Io exchange

[mike85123]

Is anyone else's Win64 client crashing for them in -server mode? I'm running i0coin.exe in -server mode and have my i0coin.conf setup correctly with the following:

rpcuser=user
rpcpassword=pass
rpcallowip=192.168.1.*
rpcport=7332
server=1

Every hour (or less) I notice that my miners return "Problem communicating with Bitcoin RPC". I'm 100% certain that I'm hitting the correct i0coin instance, since I've already managed to generate 4 confirmed blocks, and they are now in my wallet.

Killing i0coin.exe and then restarting it seems to fix the issue. Anyone reason as to why this might occur? Right now I have 14 connections, but I had ~52 connections earlier.

Having the exact same issue, although about every 20 mins.  Doesn't look like anything is wrong, but the i0coin client stops downloading blocks. Terminate the process and restart and it downloads 50 blocks real quick and starts accepting shares from my miners again.

Any help on this issue?

[coinotron]

Hi all

I've added I0coins to Coinotron.

Now you can mine for BTC, NMC, IXC or I0C

Please visit our pool.

[joulesbeef]

Just curious, is there one place shows all variants of bitcoin forks?

There's a thread, ALL IN CAPS in the Bitcoin discussion forum

great find, thanks a lot.
so many forks, so little improvements... why are those people so unimaginative?
oh wait, maybe because they are ... copycats?  

yeah an ecrypted wallet.. who the hell wants that... totally lame.
and faster block times, so transactions go faster.. what kind of improvement is that? I like waiting for 1/2 for my money to get confirmed.
and address checks.. where is the fun in that.. it is much more fun to drunkenly send namecoins to someone bitcoin wallet.
why cant someone actually improve something important, like the color of the client or something like that.

[joulesbeef]

Is anyone else's Win64 client crashing for them in -server mode? I'm running i0coin.exe in -server mode and have my i0coin.conf setup correctly with the following:

rpcuser=user
rpcpassword=pass
rpcallowip=192.168.1.*
rpcport=7332
server=1

Every hour (or less) I notice that my miners return "Problem communicating with Bitcoin RPC". I'm 100% certain that I'm hitting the correct i0coin instance, since I've already managed to generate 4 confirmed blocks, and they are now in my wallet.

Killing i0coin.exe and then restarting it seems to fix the issue. Anyone reason as to why this might occur? Right now I have 14 connections, but I had ~52 connections earlier.

Having the exact same issue, although about every 20 mins.  Doesn't look like anything is wrong, but the i0coin client stops downloading blocks. Terminate the process and restart and it downloads 50 blocks real quick and starts accepting shares from my miners again.

Any help on this issue?

I still cant connect... mined solo before.
got my i0coin.conf
same as above.. but a better user name and pass  
i0coin.exe -server client has all the blocks... and nothing.. sits there 'connecting' constantly.

netstat shows the port open and listening.

arggg

[deepceleron]

Confirmed Rewards   29669.89232442
*walks away whistling*

So the post-mortem:
-Miners were instantly klined from IRC, and can't bootstrap to get other clients to connect to,
-Difficulty 20000 worth of miners try to use a difficulty 1 network with about 1000 block finds every second
-miner -> pool latency is major fail and still can't keep up with new blocks every few seconds.

Conclusion
The p2p network becomes completely useless. The miner with the most hashrate on their local i0coind makes the longest blockchain independently. When there are finally enough connections and a high enough difficulty that everybody can start to get blocks from each other's blockchain forks, the longest blockchain wins - the person who could independently get 600 blocks ahead of everybody else by block 3500, and wipe out everybody else's balance when it was announced.

The few miners with the fastest local hashrate can keep on adding generate wins to their own blockchain. Because of continued network fail they can get two transactions or more ahead of everybody without hitting the network, and the slow network with dozens of blocks a second just keeps toasting everybody else's block finds that are a block too late in their block find announce.

1ghash with 0 i0coins after 6 hours, kinda like i0=I got 0.

Early adopter hate now replaced with mega miner hate.

Kinda like this:

However, an attack vector if you are a huge pool that is ready to go - jump on after modding the release client to also ignore any chains except ones with a block 1 you just made, you could cause everyone else's work and coins to be discarded by overwhelming the solo miners with consecutive block solves and growing a longer chain than theirs.

[kr105]

Just curious, is there one place shows all variants of bitcoin forks?

There's a thread, ALL IN CAPS in the Bitcoin discussion forum

great find, thanks a lot.
so many forks, so little improvements... why are those people so unimaginative?
oh wait, maybe because they are ... copycats? 

yeah an ecrypted wallet.. who the hell wants that... totally lame.
and faster block times, so transactions go faster.. what kind of improvement is that? I like waiting for 1/2 for my money to get confirmed.
and address checks.. where is the fun in that.. it is much more fun to drunkenly send namecoins to someone bitcoin wallet.
why cant someone actually improve something important, like the color of the client or something like that.

Just to make the things clear, i didn't write the code to encrypt the wallet. Let say that i just "enabled" it from the main repository, but yes, we are the first client to integrate that feature

[nafai]

1ghash with 0 i0coins after 6 hours, kinda like i0=I got 0.

Early adopter hate now replaced with mega miner hate.

Mining on i0.btcguild.com the whole time with 670 mhash/s, I've earned about 140 i0c in 6.5 hours.

[joulesbeef]

i've mined over 100 at 320mh.. i'm a mini miner, and i have no hate.



and I fixed that solo thing.. who knew.. i forgot to try turning it off and on again.

[darnoth]

Hi all

I've added I0coins to Coinotron.

Now you can mine for BTC, NMC, IXC or I0C

Please visit our pool.

Your pool is asking pretty weird.. It is sending several LP's per second, even when blocks are not being found.

[CoinHunter]

There's 1500BTC on the main I0coin exchange according to the owner and 250,000 I0coins, a BTC share of 0.006 per I0coin, quite amazing for such an early time in it's life.

[Tomatocage]

There's 1500BTC on the main I0coin exchange according to the owner and 250,000 I0coins, a BTC share of 0.006 per I0coin, quite amazing for such an early time in it's life.

Are we looking at the same exchange?

[Acejam]

Is anyone else's Win64 client crashing for them in -server mode? I'm running i0coin.exe in -server mode and have my i0coin.conf setup correctly with the following:

rpcuser=user
rpcpassword=pass
rpcallowip=192.168.1.*
rpcport=7332
server=1

Every hour (or less) I notice that my miners return "Problem communicating with Bitcoin RPC". I'm 100% certain that I'm hitting the correct i0coin instance, since I've already managed to generate 4 confirmed blocks, and they are now in my wallet.

Killing i0coin.exe and then restarting it seems to fix the issue. Anyone reason as to why this might occur? Right now I have 14 connections, but I had ~52 connections earlier.

Having the exact same issue, although about every 20 mins.  Doesn't look like anything is wrong, but the i0coin client stops downloading blocks. Terminate the process and restart and it downloads 50 blocks real quick and starts accepting shares from my miners again.

Any help on this issue?

Update, I found a solution!

Previously, I had server=1 in my i0coin.conf file - AND I was starting i0coin.exe from the command line using i0coin.exe -server. Essentially, this was starting up (2) i0coin.exe processes in task manager. I either needed to remove server=1 from my config file and start using -server OR leave it in the config file and just start i0coin.exe by double clicking on it. (or just launching i0coin.exe with no arguments)

I chose to leave server=1 in my config file and I'm launching the i0coin.exe client by just double clicking on it now. It reads the config file on startup and automatically runs in server mode. I've generated 2 new blocks in the last 1.5 hours, so it seems to be stable so far. My guess is that previously I had 2 server processes running at the same time, causing a fight over the local block/wallet files. Another possibility is that they were fighting for that port/socket in Windows.

[shotgun]

Some one want to tell me how I'm supposed to generate a wallet and payment address with I0coin when the Linux package doesn't include the freaking client? It has i0coind but no i0coin to connect and run commands.

[tysat]

Some one want to tell me how I'm supposed to generate a wallet and payment address with I0coin when the Linux package doesn't include the freaking client? It has i0coind but no i0coin to connect and run commands.

....i0coind is all you need.

[CoinHunter]

Are we looking at the same exchange?

I'm talking about the exchange here : https://i0exchange.bitparking.com/main

The owner is in IRC and told everyone what the deposited BTC and I0 was.