my wallet address is not showing up on cap.blockx.info/richlist/
and i was wondering why? i am running wallet V2.0.0.0
I don't think iamunick was ready to fully release it. |
|
|
|
Need some help here.
I backed up my multiple wallet files, deleted everything, reinstalled and loaded blockchain and closed down moved my wallet files over and tried opening up and getting error 22....critical error loading wallets. Won't open at all now.
What do I need to do to recover my coins?
Hi ESM, it does sound like you have a bad wallet.dat file. If you are using multiple wallets, the trick is to find out which one is corrupted. I have a FAQ about bad wallets https://cryptocointalk.com/topic/9590-hbn-trouble-shooting-guide-wallet-corruption/If you can identify which wallet is bad, you can restore that one from backup, or you can try to rename it to wallet.dat and run -salvagewallet. If you still have issues after reading over and trying this guide, you can PM. This has happened to 3 or 4 other people over the last year, and I or they were able to get back all the coins. Thank you so much for your quick response! I read your message and the linked help as soon as I saw it but I think I was able to mess things up further before I read it. Furthermore I feel foolish for bothering you'all over 108 or so HBN ...but then it again it was the only HBN I had....+ 37 I have recovered. This is where I am at. Unfortunately I did not understand the interdependency of the database and wallet files as I deleted everything but the wallet file when I reloaded...before i posted here.  That is what most other wallets suggest to do ...or at least in my little bit of experience. I was running multiple wallets including the general wallet, "savings" and then the system created a 3rd "stake". I seemed to be able to open the general wallet that had 37 and sent that to an exchange for the moment. It seems the "savings" wallet was the corrupt one as I cannot get that to open by renaming it to wallet.dat. Through out my trials I think I tried about every combination of wallets and database files ....I happened to find a databse file in my recycle bin that might be from the day I deleted the data and therefore the one that was associated to the wallet originally....but I am not sure at that either. To make a long story longer, I think I likely loaded the current version from the onset as I see I got my 1st HBN on April 25th from the giveaway thread. As the help file seems to be explaining how to recover from a version change problem....not sure if I am now SOL or what. I have managed to get myself this run time error now http://prntscr.com/3u6tvt I see there have been a couple posts after my message and not sure if they suggest there is a utility to help? I apologize for my ignorance as I do not understand the programming end of how this all works. No worries, we are all in this and learning it together. So here is what you should do. #1 Get the most current version 1.4.0.1 from my github release page. https://github.com/Tranz5/HoboNickels/releases/download/1.4.0.0/HoboNickels-qt-1.4.0.1.zipI would suggest using this to replace your blk001.dat and txleveldb directory and then start it up. http://wiki.hobonickels.info/index.php?title=Replace_BlockchainI would also rename current wallets to something like noload_wallet-old1.dat noload_wallet-old2.dat noload_wallet-old3.dat etc. Then start up the client. You will be up and running. But have no coins. After you are fully up to sync. Go back and rename your wallets as follows rename noload_wallet-old1.dat to wallet-old1.dat and then load it. If it loads ok, do the same, for the next. After you are sure you know which one is bad. Shutdown the client. and then rename it to noload_wallet-bad1.dat. If you want to try it yourself you will need to learn to use the switches -datadir and -salvagewallet. Put your bad wallet into a new directory c:\hbnfix or something and make sure it is named wallet.dat and put your database dir in there as well. Then start up client with -datadir=c:\hbnfix -listen=0 -salvagewallet You may need to use version 1.2 to salvage. It is on my release page. https://github.com/Tranz5/HoboNickels/releases/tag/1.2.2.0If you are successful. you should be then able to load the wallet.dat into the new client and be off and running. If you need help I can try for you as well. Just PM me an secure location of the bad wallet and database dir. Good luck! |
|
|
|
Hi guys. I added a small update to github tonight. There was an issue with staking and it wasn't working on 2.0 I have corrected this error: https://github.com/Tranz5/bottlecaps/commit/9409ca831c63763b34cd46b6736a3c2aa636beadFor you self compilers that want to stake, use this release. I will be officially releasing this, plus more sync issues fixes here tonight or tomorrow. Thanks for all your patients on this, hard forks can be a bit frustrating sometimes. But this time next month I think the network will be very secure and staking away! |
|
|
|
HELLO , I NEED HELP TO MY WALLET ITS CXONNECTED TO 8 NETWORKS
BUT IT SAYS "WARNING: INVALID CHECKPOINT FOUND! TRABSACTION MAY NOT BE CORRECT!YOU MAY NEED TO UPGRADE OR NOTIFY.
Sometimes after the initial sync a quick shutdown and restart of the client will remove that message. |
|
|
|
Need some help here.
I backed up my multiple wallet files, deleted everything, reinstalled and loaded blockchain and closed down moved my wallet files over and tried opening up and getting error 22....critical error loading wallets. Won't open at all now.
What do I need to do to recover my coins?
Hi ESM, it does sound like you have a bad wallet.dat file. If you are using multiple wallets, the trick is to find out which one is corrupted. I have a FAQ about bad wallets https://cryptocointalk.com/topic/9590-hbn-trouble-shooting-guide-wallet-corruption/If you can identify which wallet is bad, you can restore that one from backup, or you can try to rename it to wallet.dat and run -salvagewallet. If you still have issues after reading over and trying this guide, you can PM. This has happened to 3 or 4 other people over the last year, and I or they were able to get back all the coins. I have been successful with exporting all the private keys in a wallet file without using the client. Granted your backups are good. I worked a few days on one with flt, and we couldn't get them back because the wallet was corrupted and the user did not have a backup. I will update my code to look at HBN, tranz, what is the prefix for compressed and uncompressed HBN addresses? Send me a pm if you want to try I have pywallet set up for HBN here; https://github.com/Tranz5/pywallet the prefix is 34 |
|
|
|
The fork happened at block 491911 and those clients trapped on the shorter chain cannot re-organise to the longer chain: 17/06/14 12:28:22 REORGANIZE
17/06/14 12:28:22 REORGANIZE: Disconnect 2626 blocks; 000000000dd458745575..00000000185b11596f0a
17/06/14 12:28:22 REORGANIZE: Connect 8226 blocks; 000000000dd458745575..7d8c51bf9b063fcaa768
17/06/14 12:28:29 ERROR: DisconnectInputs() : UpdateTxIndex failed
17/06/14 12:28:29 ERROR: Reorganize() : DisconnectBlock afddc6baaef6389282cf failed
17/06/14 12:28:29 InvalidChainFound: invalid block=7d8c51bf9b063fcaa768 height=500137 trust=2003988848859 date=17/06/14 12:27:28
17/06/14 12:28:29 InvalidChainFound: current best=00000000185b11596f0a height=494537 trust=2004038605111 date=17/06/14 12:11:53
17/06/14 12:28:29 ERROR: SetBestChain() : Reorganize failed
17/06/14 12:28:29 ERROR: ProcessSyncCheckpoint: SetBestChain failed for sync checkpoint 7d8c51bf9b063fcaa768f865551f8e79d0382a927923067203a8be43af1d58ba
Why? Because the DB wasn't supposed to handle such load. Lock table is out of available lock entries
Lock table is out of available object entries The solution? Create DB_CONFIG file in your %APPDATA% / BottleCaps directory and put the following in: set_lg_dir database
set_lk_max_locks 500000
set_lk_max_objects 50000 Restart your client. 17/06/14 13:26:23 REORGANIZE
17/06/14 13:26:23 REORGANIZE: Disconnect 2626 blocks; 000000000dd458745575..00000000185b11596f0a
17/06/14 13:26:23 REORGANIZE: Connect 8289 blocks; 000000000dd458745575..8bc0c8f7881230740c0c
[...]
17/06/14 13:27:49 REORGANIZE: done
17/06/14 13:28:07 SetBestChain: new best=00000000061aa230f715 height=500201 trust=2004039184082 date=17/06/14 13:17:03
17/06/14 13:28:07 SetBestChain: new best=000000001268558811c0 height=500202 trust=2004039184130 date=17/06/14 13:17:37
17/06/14 13:28:08 SetBestChain: new best=000000000a060d20d1fb height=500203 trust=2004039184178 date=17/06/14 13:22:55
17/06/14 13:28:08 AcceptPendingSyncCheckpoint : sync-checkpoint at 000000000a060d20d1fb3f076edc761792a496e84275627f8d4d9e803d4fe25c
17/06/14 13:28:08 ProcessBlock: ACCEPTED
Enjoy. I also suggest Tranz to put a checkpoint at 491915 or so to prevent this from happening. Thanks! I will put in a few more HardCheckpoints and update the clients for download. As far as making this a perm change. Probably not right now, as we are going to have enough fun on July 4th as it is! :-) |
|
|
|
I heard through the grapevine that Cryptsy has massive updates rolling out ASAP. Apparently all lag and everything will be eliminated, I am hoping they will also be able to get CAP back online at the same time.
My 7244 confirmations transfer is the blockchain, but not at Cryptsy yet. It's been 5 days so far and more for others. I think they are on the old fork... They need to update to 2.0 or 2.0.0.1 and get caught up. |
|
|
|
Need some help here.
I backed up my multiple wallet files, deleted everything, reinstalled and loaded blockchain and closed down moved my wallet files over and tried opening up and getting error 22....critical error loading wallets. Won't open at all now.
What do I need to do to recover my coins?
Hi ESM, it does sound like you have a bad wallet.dat file. If you are using multiple wallets, the trick is to find out which one is corrupted. I have a FAQ about bad wallets https://cryptocointalk.com/topic/9590-hbn-trouble-shooting-guide-wallet-corruption/If you can identify which wallet is bad, you can restore that one from backup, or you can try to rename it to wallet.dat and run -salvagewallet. If you still have issues after reading over and trying this guide, you can PM. This has happened to 3 or 4 other people over the last year, and I or they were able to get back all the coins. |
|
|
|
|
Once the few clients that are on the wrong chain are gone this shouldn't be an issue any more.
You can also do this. Start fresh and use the -connect (not -addnode) in the Config file or the startup switch
use these IPs
(Start up Switches)
-connect=37.59.48.89:7685
-connect=62.210.122.161:7685
-connect=107.170.113.225:7685
-connect=66.172.12.153:7685
-connect=192.99.35.133:7685
-connect=72.78.100.7:7685
-connect=178.238.45.216:7685
-connect=72.52.231.153:7685
-connect=74.105.241.83:7685
Once you are on the right chain, you can restart without the -connects.
So far i have 3 of 3 computers on the 500k chain, only 1 I had to full re-sync. The rest picked up on restart no problems.
|
|
|
|
Clearing out peers.dat got me going again, but it nicely synced up to the short chain again. Now it's trying very hard to sync up with the 5500+ longer chain. Last time it got a few of these blocks and then reverted to syncing to the shorter chain. This is the log before it found the longer chain. Oops, it looks like it gave up on the longer chain and is now happily on the shorter chain. I added that log below the first one.
6/16/2014 23:07:57 SetBestChain: new best=000000003da7f48b2ad1 height=493824 trust=2003199650830 date=6/16/2014 23:02:16
6/16/2014 23:07:57 ProcessBlock: ACCEPTED
6/16/2014 23:07:57 received block 7c3c7f020970d202ee55
6/16/2014 23:07:57 SetBestChain: new best=7c3c7f020970d202ee55 height=493825 trust=2003216428302 date=6/16/2014 23:04:20
6/16/2014 23:07:58 SetBestChain: new best=0000000022f9de20187e height=493826 trust=2003216428313 date=6/16/2014 23:05:33
6/16/2014 23:07:58 ProcessBlock: ACCEPTED
6/16/2014 23:07:58 Added 999 addresses from 38.126.94.60: 5 tried, 974 new
6/16/2014 23:07:58 Added 784 addresses from 38.126.94.60: 5 tried, 1608 new
6/16/2014 23:07:58 getblocks 493614 to 00000000000000000000 limit 500
6/16/2014 23:07:58 getblocks 493614 to 00000000000000000000 limit 500
6/16/2014 23:07:59 received block 000000000dbb005521cd
6/16/2014 23:07:59 ProcessBlock: ORPHAN BLOCK, prev=0000000016d7a17ac9e3
6/16/2014 23:07:59 received block 000000000742664d13c8
6/16/2014 23:07:59 ProcessBlock: ORPHAN BLOCK, prev=000000000dbb005521cd
6/16/2014 23:07:59 received getdata (265 invsz)
6/16/2014 23:07:59 Added 521 addresses from 87.106.246.28: 5 tried, 2091 new
6/16/2014 23:07:59 Added 509 addresses from 87.106.246.28: 5 tried, 2496 new
6/16/2014 23:07:59 Added 267 addresses from 87.106.246.28: 5 tried, 2684 new
6/16/2014 23:07:59 ProcessSyncCheckpoint: pending for sync-checkpoint 000000000aab4cb51320db3bff8c3137cdc0b3f0593001a2a0f4c2554bc4d8a7
6/16/2014 23:07:59 socket send error 10054
6/16/2014 23:07:59 disconnecting node 87.106.246.28:7685
6/16/2014 23:07:59 getblocks 493614 to 00000000000000000000 limit 500
6/16/2014 23:08:00 Flushing wallet.dat
6/16/2014 23:08:00 Flushed wallet.dat 30ms
6/16/2014 23:08:01 received block 000000002d939e30106f
6/16/2014 23:08:01 SetBestChain: new best=000000002d939e30106f height=493827 trust=2003216428324 date=6/16/2014 23:05:49
6/16/2014 23:08:01 ProcessBlock: ACCEPTED
6/16/2014 23:15:49 ERROR: ConnectBlock() : UpdateTxIndex failed
6/16/2014 23:15:49 ERROR: Reorganize() : ConnectBlock 0000000020b13db8cca5 failed
6/16/2014 23:15:50 InvalidChainFound: invalid block=0000000000d29ab3a70c height=499349 trust=2003166466916 date=6/16/2014 23:12:50
6/16/2014 23:15:50 InvalidChainFound: current best=0000000055839cec8532 height=493836 trust=2003216428423 date=6/16/2014 23:13:47
6/16/2014 23:15:50 ERROR: SetBestChain() : Reorganize failed
6/16/2014 23:15:50 ERROR: AcceptPendingSyncCheckpoint: SetBestChain failed for sync checkpoint 0000000000d29ab3a70c9668f2359da70e5dc0f0a960c9afc72916a2e67bdc0d
6/16/2014 23:15:50 ProcessBlock: ACCEPTED
6/16/2014 23:15:50 REORGANIZE
6/16/2014 23:15:50 REORGANIZE: Disconnect 1925 blocks; 000000000dd458745575..0000000055839cec8532
6/16/2014 23:15:50 REORGANIZE: Connect 7439 blocks; 000000000dd458745575..000000001770e7b46e2f
6/16/2014 23:15:53 ERROR: ConnectBlock() : UpdateTxIndex failed
6/16/2014 23:15:53 ERROR: Reorganize() : ConnectBlock 0000000020b13db8cca5 failed
6/16/2014 23:15:53 connection timeout
6/16/2014 23:15:54 trying connection 75.111.222.12:7685 lastseen=7.7hrs
6/16/2014 23:15:54 InvalidChainFound: invalid block=000000001770e7b46e2f height=499350 trust=2003166466956 date=6/16/2014 23:14:56
6/16/2014 23:15:54 InvalidChainFound: current best=0000000055839cec8532 height=493836 trust=2003216428423 date=6/16/2014 23:13:47
6/16/2014 23:15:54 ERROR: SetBestChain() : Reorganize failed
6/16/2014 23:15:54 ERROR: ProcessSyncCheckpoint: SetBestChain failed for sync checkpoint 000000001770e7b46e2f901732d4ea8b251a5cf46b6c81621475f5fcb25f5437
6/16/2014 23:15:54 REORGANIZE
6/16/2014 23:15:54 REORGANIZE: Disconnect 1925 blocks; 000000000dd458745575..0000000055839cec8532
6/16/2014 23:15:54 REORGANIZE: Connect 7439 blocks; 000000000dd458745575..000000001770e7b46e2f
6/16/2014 23:15:57 ERROR: ConnectBlock() : UpdateTxIndex failed
6/16/2014 23:15:57 ERROR: Reorganize() : ConnectBlock 0000000020b13db8cca5 failed
6/16/2014 23:15:58 InvalidChainFound: invalid block=000000001770e7b46e2f height=499350 trust=2003166466956 date=6/16/2014 23:14:56
6/16/2014 23:15:58 InvalidChainFound: current best=0000000055839cec8532 height=493836 trust=2003216428423 date=6/16/2014 23:13:47
6/16/2014 23:15:58 ERROR: SetBestChain() : Reorganize failed
6/16/2014 23:15:58 ERROR: ProcessSyncCheckpoint: SetBestChain failed for sync checkpoint 000000001770e7b46e2f901732d4ea8b251a5cf46b6c81621475f5fcb25f5437
6/16/2014 23:15:58 Flushed 5504 addresses to peers.dat 10ms
6/16/2014 23:15:58 RandAddSeed() 82348 bytes
6/16/2014 23:15:58 Added time data, samples 13, offset -5 (+0 minutes)
6/16/2014 23:15:58 nTimeOffset = -5 (+0 minutes)
6/16/2014 23:15:58 Moving 173.192.30.91:7685 to tried
6/16/2014 23:15:58 receive version message: version 70001, blocks=493836, us=108.36.3.37:3214, them=173.192.30.91:7685, peer=173.192.30.91:7685
6/16/2014 23:15:58 received block 000000002dcf88032246
6/16/2014 23:15:59 connection timeout
6/16/2014 23:15:59 trying connection 71.229.213.22:7685 lastseen=128.3hrs
6/16/2014 23:15:59 SetBestChain: new best=000000002dcf88032246 height=493837 trust=2003216428434 date=6/16/2014 23:14:46
6/16/2014 23:15:59 REORGANIZE
6/16/2014 23:15:59 REORGANIZE: Disconnect 1926 blocks; 000000000dd458745575..000000002dcf88032246
6/16/2014 23:15:59 REORGANIZE: Connect 7438 blocks; 000000000dd458745575..0000000000d29ab3a70c
6/16/2014 23:16:03 ERROR: Connect() : WriteBlockIndex for pindex failed
6/16/2014 23:16:03 ERROR: Reorganize() : ConnectBlock 0000000020b13db8cca5 failed
6/16/2014 23:16:04 InvalidChainFound: invalid block=0000000000d29ab3a70c height=499349 trust=2003166466916 date=6/16/2014 23:12:50
6/16/2014 23:16:04 InvalidChainFound: current best=000000002dcf88032246 height=493837 trust=2003216428434 date=6/16/2014 23:14:46
6/16/2014 23:16:04 ERROR: SetBestChain() : Reorganize failed
6/16/2014 23:16:04 ERROR: AcceptPendingSyncCheckpoint: SetBestChain failed for sync checkpoint 0000000000d29ab3a70c9668f2359da70e5dc0f0a960c9afc72916a2e67bdc0d
6/16/2014 23:16:04 ProcessBlock: ACCEPTED
Ok I will have an update tonight or tommorw that should take care of this. |
|
|
|
Hi all! I see we are having some trouble with Cryptsy. I am here to help.. If someone from their team needs assistance please PM me. I personally did have a bit of issues when I got back. First I started up my wallet after a few weeks of being idle, and I finished sycning but I didn't get the thumbs up. Seems I got stuck on a bad fork( .28 diff) . When I finally hit a few other peers I went through a big orphan catchup. So I removed peers.dat and blkindex.dat and then re-download blocks from peers. All went well I got caught up to Friday ( 3 days ago) in about 3 hours. Then I when through a few massive re-orgs. I shut down the client and restarted it. I did get up to the right chain. I am getting checkpoints and I am in sync with http://cap.cryptocoinexplorer.com/So still going through some growing pains. I think a good feature to add(reminder for later) would be to sort peers.dat by last known good connection and begin recursively iterating backward through them. I had the same problem. Came back to the wallet after a week and it was stuck on a certain block. I followed the same steps you did, and now after 12 hours of syncing I'm up to date on a chain about 5k blocks shorter than the one here: http://cap.cryptocoinexplorer.com/Are you still synced up correctly? Can you post the peers which are getting you there? The difficulty is up almost 10x since last night on this chain, so someone's mining this. "difficulty" : 2.31820584, Yes I am still on the correct fork. did you also remove peers.dat? Since older versions will not work with 2.0. I am going to issue an update to remove them.. So far I just have a few peers that appear stuck and are requesting the same blocks again and again. But I have a strong 16 connections and on the right block. |
|
|
|
Hi all! I see we are having some trouble with Cryptsy. I am here to help.. If someone from their team needs assistance please PM me. I personally did have a bit of issues when I got back. First I started up my wallet after a few weeks of being idle, and I finished sycning but I didn't get the thumbs up. Seems I got stuck on a bad fork( .28 diff) . When I finally hit a few other peers I went through a big orphan catchup. So I removed peers.dat and blkindex.dat and then re-download blocks from peers. All went well I got caught up to Friday ( 3 days ago) in about 3 hours. Then I when through a few massive re-orgs. I shut down the client and restarted it. I did get up to the right chain. I am getting checkpoints and I am in sync with http://cap.cryptocoinexplorer.com/So still going through some growing pains. I think a good feature to add(reminder for later) would be to sort peers.dat by last known good connection and begin recursively iterating backward through them. |
|
|
|
Thanks for all the hard work Tranz. You are comfortable calling this 2.0 fully tested? Or should we say it's a public beta?
I have tested it in every way I can think of. The biggest test will be on the fork date. Up till then, this release is a good as any of them. If there are any major issues with the network after that date, we'll get them solved. But I am pretty happy with this. So have at it! :-) |
|
|
|
Well guys here it is version 2.0 is now ready. https://github.com/Tranz5/bottlecaps/releases/tag/2.0I do need a bit of help from the community. #1 We need other wallets compiled. Mac wallet for starters(perhaps someone can hit up maxpowers and/or unick). But if you can create a static build for other systems please let us know. I will update that github release with any other wallets. #2 Flound, please update the OP, and the title with BottleCaps 2.0 and the fork date. I have put in pull requests to both yours and the offical repo. Please pull those in, if you are happy with the code. #3 The old version does not have the alert keys, so I need your help making sure everyone is on the right version. So if you know someone, give them a heads up. If any of you want to try to contact Cryptsy, merchants or pool owners that would be helpful too. Probably just need 1 person to head that up. #4 On and just after the hard fork, please do come back here and make sure all is working well. I am about 99% certain all should be fine. But if there is a need for updates we'll have to move fast. I can issue alerts to 1.999 and 2.0, so your wallet will let you know if there is a problem. I won't be able to respond to PMs or messages for a few weeks. I have some family affairs to take care of, but I will be keeping any eye on the networks as usual. Thanks all. Hopefully there are some good fireworks for us all on the 4th! |
|
|
|
Could someone point me in the direction of some good pools?
I'm not having any luck with the ones on the OP.
Scroll back just a few pages, there are a few from the pool owners themselves. |
|
|
|
There is only one file in it and when I try to run it, it is telling me blkindex file is missing
Remove everything but wallet.dat out of %appdata%/BottleCaps directory and then run it. |
|
|
|
so I just downloaded the 1.5.2 wallet, but not syncing with the network. I wanna move my funds from cryptsy to my wallet. Can someone help me?
Please try version 1.999 https://github.com/Tranz5/bottlecaps/releasesLook for final release 2.0 here soon. Hmm How do I get it work. Do I copy the files to previous wallet folder? Just download that version and start it up. If you do have any issues, you may need to remove blkindex.dat from %appdata%BottleCaps directory |
|
|
|
|
Successful protocol change to version 2.0 on testnet. Doing a few mainnet tests. If all checks out. Should have a release by tomorrow.
|
|
|
|
|
Show Posts
