Topic: [I0C] I0coin - The Best Choice In Digital Currency - page 49. (Read 82618 times)
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
Ok, so now we have 3 different guys stating they never got their i0 back? At least most of it?
Anybody else? Please speak up so I don't start raining on innocent people again.
It is very strange to hear that you have gotten your BTC Back but not your i0c
One plausible explanation for smaller quantities - and 10k i0 is pretty small considering, is the fact that disks have to be defragmented and when that happens people will get their bigger shares back but the smaller amounts take some time or may be lost. The other guy I talked to who is very reputable had no problem withdrawing hundreds of thousands of i0 but then he wasn't able to take out his final 18k coins which sounds the similar to the issues others are having.
I'm curious if anyone had problems removing say 100,000 i0 or more. Something significant like that. And can you provide proof so we don't wrongly accuse Vircurex?
Finally, has anyone here had similar problems withdrawing other alts from Vircurex or is this problem isolated to just i0? That would be important information to have so please share that info if you have it.
Cheers!
Fragmented wallets make large amounts unable to move, not small amounts.
When mining I regularly found I had to send only one or two or five thousands at once to move coins from the wallets I mined to, depending how many coins one block mined gives you.
When mining tiny amounts of coins per block it takes more outputs to put together a large sum, and there is a limit to how large one transaction can be.
So if the problem at Vircurex was fragmentation of coin amounts in the wallet large sums should have been affected first, smaller sums only when remaining outputs in the wallet were so small it would take too many of them to build up even a small sum.
-MarkM-
Edit: What happened to all the posts/rants?
I got confirmation from a few reputable posters that they were able to get their i0Coins off Vicurex without issues. Hundreds of thousands of i0Coins with only a few being stuck there.
Without any other individuals coming forward I concluded that the guy who said his coins were stolen or stuck on there was most likely either a small amount or an isolated event.
That said, I felt it was best to delete my posts since they were overly aggressive and provocative.
Cheers!
I tried to withdraw 18,000+ I0Coins and the withdraw stuck, no transaction number was shown by it.
Regularly one used to see notices claiming for other coins that such stuck withdraws were being fixed, but they were fixed by putting the coins back in your account.
So I wrote to Vircurex customer support to ask about that and whether they were going to therefore allow people extra time to re-try the withdraw or what, and also took that opportunity to remind them again for the umpteenth time that they still have not put into my account the two bitcoins I sent to my bitcoin desposit address back in February or so, but they did not reply and the 18,000+ I0Coins never showed back up in my account, in fact the listing for I0Coin vanished from my account. And the history of withdraws still showed no transaction number for that withdraw, so as far as I can tell they have stolen two bitcoins and over 18,000 I0Coins from me even if one believes them that it was not them who stole all the coins they claim are "frozen"...
-MarkM-
I fired up a Xubuntu VM & the "temporary" branch wallet compiled fine (daemon only). It's currently downloading the blockchain with 2 connections.
So far so good
So far so good
Thanks, let me know how it goes! Once you have all headers (getblockchaininfo shows them), you should be able to remove the -connect option and let it use all of the network.
I fired up a Xubuntu VM & the "temporary" branch wallet compiled fine (daemon only). It's currently downloading the blockchain with 2 connections.
So far so good
So far so good
I think my coins went through from Vircurex!
I am very happy about this as its har d to get IOC in bulk, and Inmho, its the one to watch, as launch seemed to be scam free.
Also of course XPM/PPC/NXT are great (yes I hold a few of them)
XPM has been one of the few coins delisted from eg BTCe ( a largeish exchange) and has recovered in volume etc.
I am very happy about this as its har d to get IOC in bulk, and Inmho, its the one to watch, as launch seemed to be scam free.
Also of course XPM/PPC/NXT are great (yes I hold a few of them)
XPM has been one of the few coins delisted from eg BTCe ( a largeish exchange) and has recovered in volume etc.
If you are not afraid of compiling the code from the repository, you can even give it a try right now. If you want to do that, please use the "temporary" branch, i. e., https://github.com/domob1812/i0coin/tree/temporary. You may also need to -connect=51.254.131.226 (my own already updated node) for the initial sync. After you have all headers, you don't need this anymore and can connect to any other node as you like.
It may be possible to update without redownloading the chain (i. e., just leave your existing data directory), but I have not tested that.
How will one know if there is a problem when a redownload is NOT done? Will the client not sync with (download blocks from) your 51.254.131.226 node?
If there is a problem, you will notice it - either the client refuses to start at all, claiming that the directory is damaged; or it will, at least, not sync properly. One can still try to -reindex instead of purging everything first, but the safest way to avoid any problems is to redownload. However, maybe it would be good if someone not afraid of testing and tinkering a bit with an old data directory tries it out and reports the results.
If you are not afraid of compiling the code from the repository, you can even give it a try right now. If you want to do that, please use the "temporary" branch, i. e., https://github.com/domob1812/i0coin/tree/temporary. You may also need to -connect=51.254.131.226 (my own already updated node) for the initial sync. After you have all headers, you don't need this anymore and can connect to any other node as you like.
It may be possible to update without redownloading the chain (i. e., just leave your existing data directory), but I have not tested that.
How will one know if there is a problem when a redownload is NOT done? Will the client not sync with (download blocks from) your 51.254.131.226 node?
While mining, you just have to make sure that the BIPs don't activate.
Right, how does one make sure this doesn't happen? I'll test it out if it will help
Just make sure you don't mine a few hundred blocks in a row.
But to check, you can use "getblockchaininfo" -- it will show you the current state of the fork deployments. While mining, you just have to make sure that the BIPs don't activate.
Right, how does one make sure this doesn't happen? I'll test it out if it will help
Excellent work (again) domob
I'd test the temp branch, but as I'm mining I'll wait until the patched release is available as you advise. The v0.8.6-2 is working perfectly btw.
I'd test the temp branch, but as I'm mining I'll wait until the patched release is available as you advise. The v0.8.6-2 is working perfectly btw.
While mining, you just have to make sure that the BIPs don't activate. As long as you (and everyone else on the new code combined) have far less than 75% of the hashrate, it is fine. (It would, in fact, even be good to get testing results from miners!) The only thing that can happen is that you effectively "51% attack" the network and fork off everyone with the old client, but only if you have more than 75% (or, most probably, actually 95%) of the hashrate.
Excellent work (again) domob
I'd test the temp branch, but as I'm mining I'll wait until the patched release is available as you advise. The v0.8.6-2 is working perfectly btw.
I'd test the temp branch, but as I'm mining I'll wait until the patched release is available as you advise. The v0.8.6-2 is working perfectly btw.
Quick update from the wallet upgrade: I've now a mostly finished version of I0coin implemented on top of the bleeding-edge Bitcoin code, see https://github.com/domob1812/i0coin. The only thing still missing before we can make a release is a patch I submitted to upstream Bitcoin that is necessary to fix a defect with headers-first syncing. (The issue is present in Bitcoin as well but much more severe for short block times, long chains and merge-mining -- all combined by I0coin, unfortunately.) And, of course, some more testing.
If you are not afraid of compiling the code from the repository, you can even give it a try right now. If you want to do that, please use the "temporary" branch, i. e., https://github.com/domob1812/i0coin/tree/temporary. You may also need to -connect=51.254.131.226 (my own already updated node) for the initial sync. After you have all headers, you don't need this anymore and can connect to any other node as you like. Running (ideally publically reachable) nodes with this code helps strengthen the network for when everyone upgrades.
It may be possible to update without redownloading the chain (i. e., just leave your existing data directory), but I have not tested that. Be sure to make a backup of everything before you try, in every case! Also, please do not yet mine with the new client on a larger scale -- you can test mining a few blocks, but not too many consecutive blocks (you definitely shouldn't activate BIP32 or BIP66 on your node).
If you are not afraid of compiling the code from the repository, you can even give it a try right now. If you want to do that, please use the "temporary" branch, i. e., https://github.com/domob1812/i0coin/tree/temporary. You may also need to -connect=51.254.131.226 (my own already updated node) for the initial sync. After you have all headers, you don't need this anymore and can connect to any other node as you like. Running (ideally publically reachable) nodes with this code helps strengthen the network for when everyone upgrades.
It may be possible to update without redownloading the chain (i. e., just leave your existing data directory), but I have not tested that. Be sure to make a backup of everything before you try, in every case! Also, please do not yet mine with the new client on a larger scale -- you can test mining a few blocks, but not too many consecutive blocks (you definitely shouldn't activate BIP32 or BIP66 on your node).
I bought a bit of this coin
Thank you for your support.
Jump to: