Welcome to the Dash Forum!

Please sign up to discuss the most innovative cryptocurrency!

How to repair a wallet that is encrypted?

Discussion in 'Daemon and QT Wallet Guides' started by aka teslaalset, Feb 28, 2017.

  1. aka teslaalset

    aka teslaalset New Member

    Joined:
    Feb 28, 2017
    Messages:
    9
    Likes Received:
    3
    Trophy Points:
    3
    I am a recent user of QT wallet and have some issues that may be resolved using the 'wallet repair' options.
    My wallet is encrypted by default during (re)start.
    Initiating most of the wallet repair options, after unlocking the wallet first, initiate application to restart.
    E.g. trying the first option ("salvage wallet") in the wallet repair page result in a pop up with the warning text:
    "Wallet is locked. can't replenish keypool! Automatic backups and mixing are disabled, please unlock your wallet to replenish keypool".

    This seems a bug that frustrates the intended action(s). Any views on this?

    I am currently using QT Wallet using Dash Core 0.12.1.1.
     
  2. stan.distortion

    stan.distortion Active Member

    Joined:
    Oct 30, 2014
    Messages:
    839
    Likes Received:
    492
    Trophy Points:
    133
    What are the issues you're having that need repairing? Not sure why you're getting that message but the command line has much more powerful options, the wallet repair functions in the qt client are just a small set put in for convenience and many of the issues they're intended to address are long past at this stage.
     
  3. aka teslaalset

    aka teslaalset New Member

    Joined:
    Feb 28, 2017
    Messages:
    9
    Likes Received:
    3
    Trophy Points:
    3
    Stan, I've posted my issue(s) in another thread of this discussion section.
    (I can't post the link since I am a new user and require three postings first, while this is my second one).

    But for this thread it is irrelevant. The issue I raise here is that a QT Wallet feature ("wallet repair") does not seem to work due to the fact that initiating one of the 'wallet repair' options triggers the wallet app to restart, closing the wallet encryption and not requesting to open up the encrypted wallet before pursuing the repair action.
     
  4. stan.distortion

    stan.distortion Active Member

    Joined:
    Oct 30, 2014
    Messages:
    839
    Likes Received:
    492
    Trophy Points:
    133
    Ahh, ok. Could be worth submitting the issue:
    https://github.com/dashpay/dash/issues
    Might be better pinging @UdjinM6 on it first in case anything's being done with the qt repair options at the mo though.
     
  5. UdjinM6

    UdjinM6 Official Dash Dev
    Dash Core Team Moderator

    Joined:
    May 20, 2014
    Messages:
    3,637
    Likes Received:
    3,536
    Trophy Points:
    1,183
    Interesting... I''l check that, thanks for reporting!
     
    • Like Like x 1
  6. robbie47

    robbie47 New Member

    Joined:
    Feb 25, 2017
    Messages:
    2
    Likes Received:
    1
    Trophy Points:
    3
    FYI, I used the Windows 64bit version wallet application. Thanks for checking...
     
    • Like Like x 1
  7. UdjinM6

    UdjinM6 Official Dash Dev
    Dash Core Team Moderator

    Joined:
    May 20, 2014
    Messages:
    3,637
    Likes Received:
    3,536
    Trophy Points:
    1,183
    Well, I checked the code and this option should work. The warning doesn't seem to break anything according to logs. Wallet restart is also a part of the procedure, so nothing wrong here. It will trigger again and again (and will disable mixing) every time you start your wallet until you actually let it fill keypool with fresh keys by unlocking your wallet (and restart again).

    One thing to note though: salvagewallet option is _very_ aggressive and should be only used when a) you have backup of wallet.dat and b) you have no other choice, nothing else helped. It can even break your wallet actually, so please do not click it "just for fun".
     
    • Like Like x 1
  8. aka teslaalset

    aka teslaalset New Member

    Joined:
    Feb 28, 2017
    Messages:
    9
    Likes Received:
    3
    Trophy Points:
    3
    Ok, thanks for checking.
    The error message is very misleading though.
    Would be useful to fix that in one the next releases.