What is difficult now?
1024... i think.
Topic: New Ixcoin fork -> I0coin - page 54. (Read 217144 times)
yeah an ecrypted wallet.. who the hell wants that... totally lame.
something should have been done and being done on the bitcoin side long while ago, lame indeed.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.
Not entirely convinced faster block generation equate faster confirmation, besides rapid growing block chain size will exacerbate scalability issue.and address checks.. where is the fun in that.. it is much more fun to drunkenly send namecoins to someone bitcoin wallet.
Creating a new fork without these 2 lines of code for checking address type is plain ... stupid.why cant someone actually improve something important, like the color of the client or something like that. 
If that's the boundary of your imagination, I feel sorry for it. How about pruning and consolidating old blocks? how about faster block download and verification? how about using blocks as an Internet time-keeping tool? how about making the hashing power more useful? how about allowing transaction expiration to prevent lost coins? Dare to dream, my friend. Dream.
What is difficult now?
there will be another ixcoin fork soon enough lol.
yeah, but the more forks you make the less they'll have any chance of being worth anything... it's just like printing off more currency, the only thing that will be worth a damn in the end is btc.
Sure. But in the meantime it's pure entertainment
I'd love to see Thomas' face
Although I understand the reasoning, the 500+ confirmation for deposits on the exchange is kind of a bother 
It's down under 300 now. And that's like 7-8 minutes.
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.
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.
Same problem, but running it without -server hasn't helped. Just stops working after a while (and not long). Seems very buggy.
I also have a send transaction that refuses to accrue confirmations. It's not seen on bitparking's end either (and it normally appears immediately there, or at least it recognises how many coins are incoming).
Not a great success. Back to BTC
Yer I found out the hard way, lost 30 i0coin that way, don't suppose there is anyway to get them back is there?
one thing to watch out for... the addys ioexchange create for deposit are one time use only.. so dont set up autopay
And they expire in 48 hours. 
one thing to watch out for... the addys ioexchange create for deposit are one time use only.. so dont set up autopay
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.
If you pool mine you can just send it straight to the exchange (in the above post) and trade it for BTC Perfect, that works. Thanks.
Although I understand the reasoning, the 500+ confirmation for deposits on the exchange is kind of a bother
The owner is in IRC and told everyone what the deposited BTC and I0 was.
I can confirm that I did this. 
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.
If you pool mine you can just send it straight to the exchange (in the above post) and trade it for BTC 
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.
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.
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.
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.
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.
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?
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.
Hi all
I've added I0coins to Coinotron.
Now you can mine for BTC, NMC, IXC or I0C
Please visit our pool.
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.
Jump to: