I am now working under the assumption that the corruption of the block chain and wallet files, during a hard shutdown, is due to the old block chain file(s) (specifically the database log files) lingering after upgrading from 1.2.* to 1.3. As such I have added some information to the V 1.3 updgrade information page https://cryptocointalk.com/topic/3003-hbn-version-13/Old Block Chain RemovalIf you didn't do this. You are probably ok, but to be safe please be sure to backup your wallet files. Don't over-ride any old backups you have just keep an additional one. Edit: I might also suggest a few things. You can/should test your secondary wallets by bringing them to another computer to make sure they load ok. Also you can use dumpwallet and create a nice text readable format of all your keys. Print it off or copy it to thumb drive, as another method of backup. Remember this is experimental software, you have to keep yourself safe. Ok here what I`ve done to restore access for my wallets: removed 1.3 version downloaded https://github.com/Tranz5/HoboNickels/releases/tag/1.2.2.3backed up whole folder AppData\Roaming\HoboNickels and cleared it ran 1.2.2.3 version and let it download blockchain. put my wallets from a backup and "txleveldb" folder into AppData\Roaming\HoboNickels I was able to start with old wallets, see my balance and actually even got ~200 coins POS. Now My questions: - how to keep these wallets and safely migrate to 1.3  ?? - Where to send your money back Tranz? - as I got my wallets back to working condition Thank you! I just did this same thing with another wallet that another person had an issue with, and i was able to move those coins off that wallet. You beat me to the punch! So what I think is the safest thing to do is simply generate a new wallet with version 1.3. Then Back it up! With both a copy and a dumpwallet. Then move the coins from 1.2 wallet to the new version 1.3. For now I am still experimenting as well. But I think this is good. I don't know of any wallet made from version 1.3 that also had this issue with 1.3. You can send me back to here Eo6DvKHvUiHqCBXj6T6uWdbpEH8DtT3Guk Thank you too! |
|
|
|
Hey Tranz, got some weird behavior with the Mac client.
I left the Mac client opened to let it stake. It did but all blocks are orphaned?!? All without exception.. So I fire up my windows client... It stakes perfectly (and it looks like all those block that got orphaned on the Mac client)
It's the same physical machine, windows 7 in VirtualBox. Both v1.3 and the same wallet is used on both instance (actually a copy of the same wallet).
Also, I noted that I normally have less peer connections on the Mac client than on the Windows client
Do you know about this, what could be the problem? Any advice ?
Anybody else having issues staking on Mac?
Thanks
I have very little mac experiecne so I am not sure about the mac. Perhaps other Mac users can comment. Which mac client did you use for 1.3? There are two on github. Compiled by different people. So I'd like get a base as to which is causing you issues. I haven't even realized they were two different compile... I think I used thise one(99% sure) : https://github.com/Tranz5/HoboNickels/releases/download/1.3.0.0/HoboNickels-Qt-1.3.0.0-Mac.dmg.zipMeanwhile i am using the windows client for staking, let me know if you find any anomalies. Thanks my client says checkpoint too old.
i am using 1.3.0.0
should i be worried?
all my stakes get orphaned...
i am using mac client
It appears at least one of the mac clients is not working correctly. I didn't compile them nor have I used one. So please give the following information. getinfo getpeerinfo getdifficutly and which mac file you used the dmg or the other just .zip and maybe the last few lines of the log file, especially if you just attempted stake. If you are both using the dmg version. I am going to remove that version. If one of you would be so kind as to attempt the other version. Which was compiled by Max, and which version 1.2 worked ok, that would be great to know if it is working. You may need to remove the blockchain files. Also, be sure to save your wallets offline, and I would suggest doing a dumpwallet or usewallet walletname dumpwallet before you mess around too much. So you have a txt of your private keys ready, should anything go awry. I will be getting a mac computer in the future, but for now I am relying on the community to help with that. |
|
|
|
Yes I have a hard shutdown before. Remove db file and those 2 folders. I get 2 wallet files: default and mining. Only the wallet-mining.dat file get error message when launching wallet client. I tried copy mining DAT file to somewhere else and "load" that DAT manually. Still get following message: "Critical error loading wallet xxx.dat:CDB() / error 22" Is it means this wallet file is currupted?  Yes I think it does. Damn..... My guess is it is the mining wallet. You can tell by using the -usewallet="" switch. And see if it starts up. There maybe something not quite right with secondary wallets. Edit: I see you already pinpointed it to a secondary wallet. Please let me know if you have a backup or not. I'll start digging through the code and see why the currpotion is only happening on the non default wallets. I tried -usewallet="wallet-mining.dat" and -usewallet="wallet.dat". Both return "invalid wallet name in -usewallet=XXXXXXX" (Have to wait for block index loading which is very slow) I found the quickest way to check 2nd wallet is move main wallet away and rename 2nd wallet to wallet.dat. The qt-client seems check wallet validity before loading blocks. My error message is "Invalid wallet and salvage failed". Luckily there're just around 5XX HBN inside my mining wallet. So I will keep the copy hope there's some way to recover this file in the future  The -usewallet switch is -usewallet="mining" which would load wallet-mining.dat and default. You don't need to specify wallet.dat, as that is the default wallet and is always loaded. |
|
|
|
I am now working under the assumption that the corruption of the block chain and wallet files, during a hard shutdown, is due to the old block chain file(s) (specifically the database log files) lingering after upgrading from 1.2.* to 1.3. As such I have added some information to the V 1.3 updgrade information page https://cryptocointalk.com/topic/3003-hbn-version-13/Old Block Chain RemovalPlease move/remove these 3 pieces of data before you start up the new version 1.3 client for the first time, and after you shut down the old client
In %appdata%/HoboNickels Remove blkindex.dat, blk001.dat(unless you are going to bootstrap) and the database directory. If you don't remove these it is possible to get corruption of the block chain (not so bad) or your wallet file(potentially bad), if you have a have a hard shutdown. If you didn't do this. You are probably ok, but to be safe please be sure to backup your wallet files. Don't over-ride any old backups you have just keep an additional one. Edit: I might also suggest a few things. You can/should test your secondary wallets by bringing them to another computer to make sure they load ok. Also you can use dumpwallet and create a nice text readable format of all your keys. Print it off or copy it to thumb drive, as another method of backup. Remember this is experimental software, you have to keep yourself safe. |
|
|
|
also ubuntu`s db.log:
file wallet-stake.dat has LSN 231/2730566, past end of log at 1/183838
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
Ok thanks, this makes since. If you didn't remove the and blkindex.dat and database directory before the upgrade to version 1.3 I can see how this could happen. I am sorry I didn't realize this was an issue. Please PM me and I will see if I can help you out. |
|
|
|
|
HBN would be a great trading pair for PoS Coins. Been very steady at a nickel and been with very smooth difficulty changes.
|
|
|
|
cool a new coin WTS 10000 Teacoins  Are you a bot? |
|
|
|
Yes I have a hard shutdown before. Remove db file and those 2 folders. I get 2 wallet files: default and mining. Only the wallet-mining.dat file get error message when launching wallet client. I tried copy mining DAT file to somewhere else and "load" that DAT manually. Still get following message: "Critical error loading wallet xxx.dat:CDB() / error 22" Is it means this wallet file is currupted? Yes I think it does. Damn..... My guess is it is the mining wallet. You can tell by using the -usewallet="" switch. And see if it starts up. There maybe something not quite right with secondary wallets. Edit: I see you already pinpointed it to a secondary wallet. Please let me know if you have a backup or not. I'll start digging through the code and see why the currpotion is only happening on the non default wallets. |
|
|
|
I get this error message suddenly when I relanuch wallet  It's the beta 1.4 client. Still get same message when I download the 1.3 client. Can you tell me if there was a hard shutdown of your computer? Or recent windows update? Another friend got this error as well, not sure what is causing it. It can solved by removing the blk0001.dat and database and txleveldb directories in %appdata%/HoboNickels. It maybe best to take a quick copy of all files in %appdata%/HoboNickels first though. |
|
|
|
Here is a version what will work with HBN, by default. https://github.com/Tranz5/pywalletTried to help another who had a bad wallet but no luck. Backup all your wallets at least every other months and put a copy offline on a thumb drive, and maybe in the backup directory of your %appdata% folder. It is worth the 2 minutes it takes!!!!Version 1.4 will have an auto wallet backup that will take a snapshot every 24 hours or so. But for now, you are responsible for ensuring you are protected. mixax1 if you continue to have issue, please PM me. I'll see if I can help. |
|
|
|
|
Those who have a corrupted wallet, I am working on a version of pywallet that will work with HBN. It should just be --otherversion=34 but you will have to specify the path as well.
For those that are fine. Please take the opportunity to save a wallet off line. And even keep a printed copy. I have added dumpwallet to the rpc commands so it is very easy to print it out and keep it on paper.
|
|
|
|
I had 1k coins stake, but it's not in my transaction list. I guess I'm confused. I have a few PoS mined totaling ~40ish. I would have never known the 1k stake happened if I didn't see it pending on the overview.
Sort your transaction list by date, rather then status. |
|
|
|
Hi Tranz.
Didnt check this thread for a time, and now I see new version 1.3 released.
Does it works with multiwallet form previous version?
Deleted all files except 2 wallet.dat files from previous version (1.2.2) and run the 1.3 version, after chain downloading the client is crushing(
Version 1.3 will work with multi-wallets. You mean to say the client is crashing? Do you have an error in the debug log? It could be a corrupt wallet. But hard to say with no other infomation. One thing to try is to isolate the wallets. So rename your wallets to something like nowallet.dat or nowallet-stake. And then start-up the client. If it doesn't crash, then you have some corruption with one of your wallets. Let me know if you need further help. Hi Tranz. Making nowallet didnt work. Win7 shows miscrosoft visual c++ runtime library error. Debug log shows multiple errors of such a kind: ERROR: CheckProofOfStake() : INFO: read txPrev failed WARNING: ProcessBlock(): check proof-of-stake failed for block ... (different blocks) connection timeout May be I should delete an old .conf file with different addnodes, which may be already dont work...I dont know I have Win7 64, and using windows client 1.3 (P.S. does older 1.2.2 version works now or not?) You can go back to the old client yes. You will need to remove block chain files and re-sync. Although I am not sure you should have too. You can move all your files into a new bkup directory and try to go fresh and see what happens. If you get up to speed you can reload the old wallets from the bkup directory and see if they cause a crash. Ive made a clean install, by deleting all files except the wallet.dat and run the HoboNickels-qt.exe from 1.3.0.0 version, and the client still crush approx after downloading the blockchain. Going back to 1.2.2 Update: after removing back to 1.2.2, during blockchain downloading (after clean install), got this error: "Critical error loading wallet "POS" from wallet-POS.dat:CDB() : can't open database file wallet-POS.dat, error 22" Wallet file was taken from backup, during 1.3 installation I was experimented with "nowallet" thing, could this be the reason? What should I do? I've had 2 wallets on my multiwallet 1.2.2 system when it was working (wallet.dat and wallet-POS.dat). If i'll take 2nd .dat file (wallet-POS.dat) to another machine and will try to sync 1.2.2 system there, would it work without 1st .dat (wallet.dat)? I'll try and report. You may try to use the -salvagewallet option. Between 1.2.2 and 1.3 there is no change to the wallet file only the block chain. So if you are having issues with the wallet. Going back a rev most likely won't help. With a PoS client the wallet is in read/write mode alot more then with only PoW clients, so the operutnity for curroption is much higher. I'll work on some methods to lower this chance. Please keep a backup of your wallet offline. I have done this for every client I have used, and even tough I have currpoted even litecoin wallets, my bakcups have saved me. |
|
|
|
Hey Tranz, got some weird behavior with the Mac client.
I left the Mac client opened to let it stake. It did but all blocks are orphaned?!? All without exception.. So I fire up my windows client... It stakes perfectly (and it looks like all those block that got orphaned on the Mac client)
It's the same physical machine, windows 7 in VirtualBox. Both v1.3 and the same wallet is used on both instance (actually a copy of the same wallet).
Also, I noted that I normally have less peer connections on the Mac client than on the Windows client
Do you know about this, what could be the problem? Any advice ?
Anybody else having issues staking on Mac?
Thanks
I have very little mac experiecne so I am not sure about the mac. Perhaps other Mac users can comment. Which mac client did you use for 1.3? There are two on github. Compiled by different people. So I'd like get a base as to which is causing you issues. |
|
|
|
Maybe the fact that everyone is holding now is keeping the price up, but it seems very uncertain/speculative that the price will remain the same, even as the number of coins in circulation keeps rising exponentially.
The upper limit on stake is 100% a year. The lower limit is 1% a year. As more people let their coins to stake, the difficulty goes up. As the difficulty goes up, the percentage of stake goes down. These can be tightened in the future if necessary too. As it is, the total coins out right now with PoS/PoW is actually lower then if we only had PoW. |
|
|
|
|
Good luck with your investment.
Just so you and others know. I keep a look out for those looking to buy big lots. If I see the price moving up and large bids. I may put a nice large block to feed the whales. If it doesn't get eating in a day or 2 I take it back off.
If anyone is looking to increase their position, I can do the same for you. I believe I put out a nice block at 6500 and a few at 7000 - 10,000.
I never hit the bid I only put my coins at the ask. If anyone wants them they can come get them. I then almost always put 1/2 that back in to the buy side. To help the miners.
|
|
|
|
Ok few things to try
#1 back up both wallets to another directory.
#2 startup client with just the wallet.dat ( you can use switch -usewallet="" )
#3 after you are sync'd up with chain. Try to quickly load the wallet-stake.dat and then send those coins to another wallet.
#4 if that fails and the client crashes. Rename wallet.dat to wallet-olddef.dat Rename wallet-stake.dat wallet.dat then start client with -salvagewallet -usewallet=""
Maybe a stupid question but you do you have a backup of your wallet-stake.dat?
Let me know.
#1 back up both wallets to another directory. #2 startup client with just the wallet.dat ( you can use switch -usewallet="" ) - done waiting for re-sync now... Maybe a stupid question but you do you have a backup of your wallet-stake.dat? - unfortunately - no ( will follow up with later results... thank you! I think it happend after electricity outage ( Yes hard shutdowns can cause corruption. It is a shame that the wallets are so fragile. I do plan to implement a rpc command/improvement that will auto backup all wallets on a set schedule. If you still have issues, there are tools such as prywallet that can help get your private keys out, so you can at least get access to your coins. |
|
|
|
|
Show Posts
