I didn't comment cos I didn't lose anything - still got mine & still mining it 
good to hear
were you able to withdraw i0c from exchange?
Topic: [I0C] I0coin - The Best Choice In Digital Currency - page 50. (Read 81914 times)
good to hear
were you able to withdraw i0c from exchange?
I didn't comment cos I didn't lose anything - still got mine & still mining it
I'll up that to 4,000 sat. Double the current market price.
if people could get their i0coin out of vircurex there would be more big sells already on cryptopia
give it time
it's definitely a good time to buy
can't go much lower, and it's mostly because vircurex is playing game so people weren't bidding price up or even making any trades
cryptopia looks much better
I'll up that to 4,000 sat. Double the current market price.
Damn Vircurex. I withdraw my I0C almost month ago and Vircurex doesn't send my coins. Already send couple emails without response. 10 000 I0C lost 
I wanna buy 100,000 i0.
I'll pay 3,000 sat if anyone is interested. It's currently at 2,000 sat on Cryptopia.
up the bounty to 250k and i may consider looking at it
I0coin is now trading on Cryptopia. It can be traded against eight different cyrptocurrencies. Here are direct links to two.
https://www.cryptopia.co.nz/Exchange?market=I0C_BTC
https://www.cryptopia.co.nz/Exchange?market=I0C_LTC
They also have a built in block explorer.
https://www.cryptopia.co.nz/BlockExplorer?coin=I0C
Great work getting on a new exchange. I'll add a link to our exchange list at the top of this thread.
OK, sorted. I ended up using:
...first time I've used that - learn something every day.......
Compiled without errors & I'm now up & running with 80602
Code:
git clone -b old-client https://github.com/domob1812/i0coin.git
...first time I've used that - learn something every day.......
Compiled without errors & I'm now up & running with 80602
Great! Thanks for testing!
When I get positive results from you (i. e., that it really works not just for me), I can ask snailbrain from Huntercoin to compile working binaries for all platforms.
Thanks p3yot33at3r for compiling. If anyone else has or can successfully compile the 0.8.6-2 client let us know.
I'm seeing a lot of timeout messages for the daemon trying to connect to peers on port 7333 for some reason, which isn't an i0coin port? I have port 7337 in my conf file, so not sure why it's still trying to use that port.
According to the code, 7333 is the usual listening port and 7332 is the RPC port. But you are free to configure any other port as well in the config file (including 7337).
Apart from that, auxpow seems to be working fine & I'm receiving payments as usual.
Sounds good! The "old-client" branch, however, is only a minor change necessary to upgrade the network to the new client in the future. So no big surprise that auxpow still works ... but it is a good step, we need as many of the new nodes running as possible. Thanks for testing!
I'm seeing a lot of timeout messages for the daemon trying to connect to peers on port 7333 for some reason, which isn't an i0coin port? I have port 7337 in my conf file, so not sure why it's still trying to use that port.
Apart from that, auxpow seems to be working fine & I'm receiving payments as usual.
Code:
2015-09-19 09:54:02 trying connection 91.206.210.116:7333 lastseen=18054.3hrs
2015-09-19 09:54:02 connect() failed after select(): Connection refused
2015-09-19 09:54:02 trying connection 88.147.158.86:7333 lastseen=3.3hrs
2015-09-19 09:54:07 connection timeout
2015-09-19 09:54:08 trying connection 181.124.98.136:7333 lastseen=31.9hrs
2015-09-19 09:54:13 connection timeout
2015-09-19 09:54:13 trying connection 87.182.86.196:7333 lastseen=2210.0hrs
2015-09-19 09:54:18 connection timeout
2015-09-19 09:54:19 trying connection 172.56.37.68:7333 lastseen=2941.9hrs
2015-09-19 09:54:24 connection timeout
2015-09-19 09:54:24 trying connection 37.187.92.30:7333 lastseen=614.7hrs
2015-09-19 09:54:24 connect() failed after select(): Connection refused
2015-09-19 09:54:25 trying connection 80.153.125.196:7333 lastseen=1085.8hrs
2015-09-19 09:54:30 connection timeout
2015-09-19 09:54:30 trying connection 98.230.162.64:7333 lastseen=15411.8hrs
Apart from that, auxpow seems to be working fine & I'm receiving payments as usual.
OK, sorted. I ended up using:
...first time I've used that - learn something every day.......
Compiled without errors & I'm now up & running with 80602
Code:
git clone -b old-client https://github.com/domob1812/i0coin.git
...first time I've used that - learn something every day.......
Compiled without errors & I'm now up & running with 80602
Great! Thanks for testing!
When I get positive results from you (i. e., that it really works not just for me), I can ask snailbrain from Huntercoin to compile working binaries for all platforms.
Yes, that would be great! Thanks, looking forward to the report!
Oh, I'm unable to do a git clone of https://github.com/domob1812/i0coin/tree/old-client.git
You should clone this (the repository):
https://github.com/domob1812/i0coin.git
Then, check out the "old-client" branch.
OK, sorted. I ended up using:
Code:
git clone -b old-client https://github.com/domob1812/i0coin.git
...first time I've used that - learn something every day.......
Compiled without errors & I'm now up & running with 80602
Yes, that would be great! Thanks, looking forward to the report!
Oh, I'm unable to do a git clone of https://github.com/domob1812/i0coin/tree/old-client.git
You should clone this (the repository):
https://github.com/domob1812/i0coin.git
Then, check out the "old-client" branch.
Yes, that would be great! Thanks, looking forward to the report!
Oh, I'm unable to do a git clone of https://github.com/domob1812/i0coin/tree/old-client.git
Is there another way?
No, I ended up reverting back to 0.8.6-1 I'm afraid - never got past block 128...... 
Did 0.8.6-1 resume syncing from that point without any issues? Were there any error messages or anything else suspicious in the log? Did you have proper node connections?
BTW, you don't have to resync the blockchain when upgrading to 0.8.6-2, nor do you have to reindex. The change is purely on the networking-side and does not concern the blockchain format nor block validation rules. (I. e., it is not a fork.)
I had to reindex after trying the latest build, but no problem with connections. I had to dash out & forgot to save the logs, but I remember seeing lots of errors concerning blockheaders(?) I will try compiling 0.8.6-2 from source now & report back
Yes, that would be great! Thanks, looking forward to the report!
No, I ended up reverting back to 0.8.6-1 I'm afraid - never got past block 128......
Did 0.8.6-1 resume syncing from that point without any issues? Were there any error messages or anything else suspicious in the log? Did you have proper node connections?
BTW, you don't have to resync the blockchain when upgrading to 0.8.6-2, nor do you have to reindex. The change is purely on the networking-side and does not concern the blockchain format nor block validation rules. (I. e., it is not a fork.)
I had to reindex after trying the latest build, but no problem with connections. I had to dash out & forgot to save the logs, but I remember seeing lots of errors concerning blockheaders(?) I will try compiling 0.8.6-2 from source now & report back
No, I ended up reverting back to 0.8.6-1 I'm afraid - never got past block 128......
Did 0.8.6-1 resume syncing from that point without any issues? Were there any error messages or anything else suspicious in the log? Did you have proper node connections?
BTW, you don't have to resync the blockchain when upgrading to 0.8.6-2, nor do you have to reindex. The change is purely on the networking-side and does not concern the blockchain format nor block validation rules. (I. e., it is not a fork.)
I was unable to run the 0.8.6-2 daemon binary on 64bit Xubuntu - error referred to db incompatibility, I'm using 4,8
Yes, that's true. I compiled against the standard BDB bundled with the distribution.
Edit: Ah, wait. I just noticed that it's trying to use a bitcoin.conf file - I'll try again using the --conf option.......
Good luck! Did it get unstuck already? Note that I didn't change anything above 0.8.6-1 except for the version number and a parameter related to the "getheaders" P2P message, which is unused by the current network. So there "shouldn't" be any difficulties in comparison to 0.8.6-1.
No, I ended up reverting back to 0.8.6-1 I'm afraid - never got past block 128......
Jump to: