Topic: [I0C] I0coin - The Best Choice In Digital Currency - page 48. (Read 82318 times)
izerocoin.org will be down while I do some updates.
BTW, currently already 23% of the hash rate have updated.
mmpool has updated to this version. Thanks for updating to a newer codebase!Thanks for your support. Let us know if there are any mining issues. At least one miner upgraded about a month ago, with no problems reported so far. Many more miners have jumped on board in the last week.
BTW, currently already 23% of the hash rate have updated.
mmpool has updated to this version. Thanks for updating to a newer codebase! 
I've now merged some more upstream Bitcoin changes to the "master" branch of my I0coin repository, in order to keep up with development for a future 0.12 release. You can also use that if you build from source, but if you want the exact same version released earlier, use the "i0coin-0.11.9" tag:
https://github.com/domob1812/i0coin/releases/tag/i0coin-0.11.9
It is signed by my GPG key. The "temporary" branch is unaffected and still the same as the binaries.
BTW, currently already 23% of the hash rate have updated.
https://github.com/domob1812/i0coin/releases/tag/i0coin-0.11.9
It is signed by my GPG key. The "temporary" branch is unaffected and still the same as the binaries.
BTW, currently already 23% of the hash rate have updated.
I've also successfully transferred I0C while in prune mode (with only the last 600 MB of the block chain).
The transfer worked brilliantly!
This will allow users and many service sites to run a thin i0coin client without using up gigabytes of storage. Of course we still need some nodes with the full block chain.
how do I turn on prune mode?
With the Qt client add the following to the i0coin.conf file.
prune=xxx
where xxx is the number of MB you want for the block chain (i.e. "prune=600" means the block chain will take up about 600 MB). xxx must be at least 550 MB.
For the i0coind client it would similarly be called like this.
i0coind -prune=xxx
I've also successfully transferred I0C while in prune mode (with only the last 600 MB of the block chain).
The transfer worked brilliantly!
This will allow users and many service sites to run a thin i0coin client without using up gigabytes of storage. Of course we still need some nodes with the full block chain.
how do I turn on prune mode?
I0coin 0.11.9 Windows Executables
Below is a bit more info about the two versions of executables which domob has posted. They are both almost identical with the differences stated below.
"i0coin-0.11.9"
-allows only 0.11.x clients to connect (the older 0.8.x client is blocked because it will be incompatible with the new BIPs)
-most users should migrate to this version so we can phase out the older clients
-miners should upgrade to this version
"i0coin-temp" (0.11.9.9)
-allows all client versions to connect to it
-a few users are running this to allow cross communication between all clients so we don't have any forking issues
-once we've reached our BIP activation point this temp version can be phased out
Good news, thanks for snailbrain (the brain behind Huntercoin), I can now provide Windows binaries:
http://extra.domob.eu/i0coin-0.11.9.zip
http://extra.domob.eu/i0coin-0.11.9.zip.sig (GPG signature with my key, see signature)
If you want to help stabilise the network, you can also run the "temporary" version:
http://extra.domob.eu/i0coin-temp.zip
http://extra.domob.eu/i0coin-temp.zip.sig
With the temporary binary, you should -connect=51.254.131.226 for the initial sync. When you are up-to-date, you can restart without this option.
Note: The update will activate BIP34, BIP66 and BIP65 as soon as 75%/95% of the hash rate has upgraded (currently 13%). This means that miners have to update as soon as this happens; users should upgrade to stay on the best security level, but are not required to do so necessarily.
http://extra.domob.eu/i0coin-0.11.9.zip
http://extra.domob.eu/i0coin-0.11.9.zip.sig (GPG signature with my key, see signature)
If you want to help stabilise the network, you can also run the "temporary" version:
http://extra.domob.eu/i0coin-temp.zip
http://extra.domob.eu/i0coin-temp.zip.sig
With the temporary binary, you should -connect=51.254.131.226 for the initial sync. When you are up-to-date, you can restart without this option.
Note: The update will activate BIP34, BIP66 and BIP65 as soon as 75%/95% of the hash rate has upgraded (currently 13%). This means that miners have to update as soon as this happens; users should upgrade to stay on the best security level, but are not required to do so necessarily.
Below is a bit more info about the two versions of executables which domob has posted. They are both almost identical with the differences stated below.
"i0coin-0.11.9"
-allows only 0.11.x clients to connect (the older 0.8.x client is blocked because it will be incompatible with the new BIPs)
-most users should migrate to this version so we can phase out the older clients
-miners should upgrade to this version
"i0coin-temp" (0.11.9.9)
-allows all client versions to connect to it
-a few users are running this to allow cross communication between all clients so we don't have any forking issues
-once we've reached our BIP activation point this temp version can be phased out
I've also successfully transferred I0C while in prune mode (with only the last 600 MB of the block chain).
The transfer worked brilliantly!
This will allow users and many service sites to run a thin i0coin client without using up gigabytes of storage. Of course we still need some nodes with the full block chain.
The new 0.11.9 client reduces the block chain size by about 50%, from 12.5 GB to 5.8 GB. That's a big improvement, and that's without any pruning. With pruning turned on it can be set to any size you want. Thanks for the hard work domob!
Thanks, but you should actually thank the Bitcoin devs for their hard work -- they did most of the improvements you see.
I know, but you brought it to i0coin!!!
The new 0.11.9 client reduces the block chain size by about 50%, from 12.5 GB to 5.8 GB. That's a big improvement, and that's without any pruning. With pruning turned on it can be set to any size you want. Thanks for the hard work domob!
Thanks, but you should actually thank the Bitcoin devs for their hard work -- they did most of the improvements you see.
Great job guys. I'll give the new wallet a try.
The new 0.11.9 client reduces the block chain size by about 50%, from 12.5 GB to 5.8 GB. That's a big improvement, and that's without any pruning. With pruning turned on it can be set to any size you want. Thanks for the hard work domob!
Good news, thanks for snailbrain (the brain behind Huntercoin), I can now provide Windows binaries:
http://extra.domob.eu/i0coin-0.11.9.zip
http://extra.domob.eu/i0coin-0.11.9.zip.sig (GPG signature with my key, see signature)
If you want to help stabilise the network, you can also run the "temporary" version:
http://extra.domob.eu/i0coin-temp.zip
http://extra.domob.eu/i0coin-temp.zip.sig
With the temporary binary, you should -connect=51.254.131.226 for the initial sync. When you are up-to-date, you can restart without this option.
Note: The update will activate BIP34, BIP66 and BIP65 as soon as 75%/95% of the hash rate has upgraded (currently 13%). This means that miners have to update as soon as this happens; users should upgrade to stay on the best security level, but are not required to do so necessarily.
http://extra.domob.eu/i0coin-0.11.9.zip
http://extra.domob.eu/i0coin-0.11.9.zip.sig (GPG signature with my key, see signature)
If you want to help stabilise the network, you can also run the "temporary" version:
http://extra.domob.eu/i0coin-temp.zip
http://extra.domob.eu/i0coin-temp.zip.sig
With the temporary binary, you should -connect=51.254.131.226 for the initial sync. When you are up-to-date, you can restart without this option.
Note: The update will activate BIP34, BIP66 and BIP65 as soon as 75%/95% of the hash rate has upgraded (currently 13%). This means that miners have to update as soon as this happens; users should upgrade to stay on the best security level, but are not required to do so necessarily.
For anyone else running into this error, see https://github.com/domob1812/i0coin/issues/1. Basically, you have to make sure your keypool is filled while mining. Some old versions did reuse addresses instead of draining the keypool, but this is no longer the case because address reuse is bad practise. Make sure to create sufficient backups when refilling!
I've updated my code for the new 0.11.9 client to the latest Bitcoin sources, including the upcoming BIP65. If you can compile from source, please give it a try: https://github.com/domob1812/i0coin
I'm getting this error with the new client on p2pool:
Code:
2015-11-09 13:48:20.429566 > Error while calling merged getauxblock on http://127.0.0.1:7338/:
2015-11-09 13:48:20.429667 > Traceback (most recent call last):
2015-11-09 13:48:20.429696 > File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 577, in _runCallbacks
2015-11-09 13:48:20.429735 > current.result = callback(current.result, *args, **kw)
2015-11-09 13:48:20.429762 > File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1155, in gotResult
2015-11-09 13:48:20.429787 > _inlineCallbacks(r, g, deferred)
2015-11-09 13:48:20.429823 > File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1097, in _inlineCallbacks
2015-11-09 13:48:20.429857 > result = result.throwExceptionIntoGenerator(g)
2015-11-09 13:48:20.429886 > File "/usr/lib/python2.7/dist-packages/twisted/python/failure.py", line 389, in throwExceptionIntoGenerator
2015-11-09 13:48:20.429931 > return g.throw(self.type, self.value, self.tb)
2015-11-09 13:48:20.429966 > ------
2015-11-09 13:48:20.430017 > File "/home/rig/p2pool/p2pool/util/deferral.py", line 41, in f
2015-11-09 13:48:20.430057 > result = yield func(*args, **kwargs)
2015-11-09 13:48:20.430088 > File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1097, in _inlineCallbacks
2015-11-09 13:48:20.430119 > result = result.throwExceptionIntoGenerator(g)
2015-11-09 13:48:20.430149 > File "/usr/lib/python2.7/dist-packages/twisted/python/failure.py", line 389, in throwExceptionIntoGenerator
2015-11-09 13:48:20.430180 > return g.throw(self.type, self.value, self.tb)
2015-11-09 13:48:20.430226 > File "/home/rig/p2pool/p2pool/util/jsonrpc.py", line 133, in _http_do
2015-11-09 13:48:20.430258 > raise Error_for_code(resp['error']['code'])(resp['error']['message'], resp['error'].get('data', None))
2015-11-09 13:48:20.430296 > p2pool.util.jsonrpc.NarrowError: -12 Error: Keypool ran out, please call keypoolrefill first
I done a search about "Error: Keypool ran out, please call keypoolrefill first" but couldn't find an answer - any ideas anyone?
I'm still only seeing the one node (domob) on the new wallet version - it would be nice if a few more users updated
Working well btw.
Working well btw.
I've updated my code for the new 0.11.9 client to the latest Bitcoin sources, including the upcoming BIP65. If you can compile from source, please give it a try: https://github.com/domob1812/i0coin
I also updated the "temporary" branch: https://github.com/domob1812/i0coin/tree/temporary If you run this one, you help stabilise the network during the transition period. You may need to -connect to a node knowingly running the new version (e. g., 51.254.131.226) if you experience problems during syncing.
I'll try to get binaries built in the next days - but if you can compile yourself, any testing helps!
I also updated the "temporary" branch: https://github.com/domob1812/i0coin/tree/temporary If you run this one, you help stabilise the network during the transition period. You may need to -connect to a node knowingly running the new version (e. g., 51.254.131.226) if you experience problems during syncing.
I'll try to get binaries built in the next days - but if you can compile yourself, any testing helps!
Nice work domob. If anyone has a list of nodes running the "new" client, I will run a "temp" node to help through the transition
The example node domob gave, 51.254.131.226, is a new version 0.11.9. As new nodes come online you can always check the node list for each client version at the following site. Click on the Network tab.
https://chainz.cryptoid.info/i0c/#!network
I've updated my code for the new 0.11.9 client to the latest Bitcoin sources, including the upcoming BIP65. If you can compile from source, please give it a try: https://github.com/domob1812/i0coin
I also updated the "temporary" branch: https://github.com/domob1812/i0coin/tree/temporary If you run this one, you help stabilise the network during the transition period. You may need to -connect to a node knowingly running the new version (e. g., 51.254.131.226) if you experience problems during syncing.
I'll try to get binaries built in the next days - but if you can compile yourself, any testing helps!
I also updated the "temporary" branch: https://github.com/domob1812/i0coin/tree/temporary If you run this one, you help stabilise the network during the transition period. You may need to -connect to a node knowingly running the new version (e. g., 51.254.131.226) if you experience problems during syncing.
I'll try to get binaries built in the next days - but if you can compile yourself, any testing helps!
Nice work domob. If anyone has a list of nodes running the "new" client, I will run a "temp" node to help through the transition
I've updated my code for the new 0.11.9 client to the latest Bitcoin sources, including the upcoming BIP65. If you can compile from source, please give it a try: https://github.com/domob1812/i0coin
I also updated the "temporary" branch: https://github.com/domob1812/i0coin/tree/temporary If you run this one, you help stabilise the network during the transition period. You may need to -connect to a node knowingly running the new version (e. g., 51.254.131.226) if you experience problems during syncing.
I'll try to get binaries built in the next days - but if you can compile yourself, any testing helps!
I also updated the "temporary" branch: https://github.com/domob1812/i0coin/tree/temporary If you run this one, you help stabilise the network during the transition period. You may need to -connect to a node knowingly running the new version (e. g., 51.254.131.226) if you experience problems during syncing.
I'll try to get binaries built in the next days - but if you can compile yourself, any testing helps!
I0coin's market cap has increased from $24,064 to $376,914 since September. That's an increase of 1466% ( http://coinmarketcap.com/currencies/i0coin/#charts ).
The new exchange has helped make this possible.
https://www.cryptopia.co.nz/Exchange?market=I0C_BTC
Jump to: