• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

V12 Release

One of my Masternode's wallet-QT (on Windows) has issues starting, I have a feeling the wallet.dat file is causing this. They're all running the same version: v12.0.46.


Everytime I want to run the wallet it starts re-scanning, none of the other wallets do this:



Then when the rescanning hits 100%, it throws an error:



After removing the wallet.dat file the wallet starts just fine. How can I fix my wallet without having to re-setup my Masternode?
 
One of my Masternode's wallet-QT (on Windows) has issues starting, I have a feeling the wallet.dat file is causing this. They're all running the same version: v12.0.46.


Everytime I want to run the wallet it starts re-scanning, none of the other wallets do this:



Then when the rescanning hits 100%, it throws an error:



After removing the wallet.dat file the wallet starts just fine. How can I fix my wallet without having to re-setup my Masternode?
I would think - if you have any coins on that wallet - move it to another wallet/DIR for now - when you restart MN a new wallet.dat file will be created - you should be ok

If you have any coins in that wallet - open another instance of DASH and dump private keys... etc etc


edit: you're also not on the correct QT version...
 
One of my Masternode's wallet-QT (on Windows) has issues starting, I have a feeling the wallet.dat file is causing this. They're all running the same version: v12.0.46.


Everytime I want to run the wallet it starts re-scanning, none of the other wallets do this:



Then when the rescanning hits 100%, it throws an error:



After removing the wallet.dat file the wallet starts just fine. How can I fix my wallet without having to re-setup my Masternode?
Is the wallet.dat file from the old v.11 ?
 
One of my Masternode's wallet-QT (on Windows) has issues starting, I have a feeling the wallet.dat file is causing this. They're all running the same version: v12.0.46.


Everytime I want to run the wallet it starts re-scanning, none of the other wallets do this:



Then when the rescanning hits 100%, it throws an error:



After removing the wallet.dat file the wallet starts just fine. How can I fix my wallet without having to re-setup my Masternode?
See here: https://dashtalk.org/threads/v12-testing-thread.5484/page-152#post-63947
But also see here: https://dashtalk.org/threads/v12-testing-thread.5484/page-153#post-63973
 
I've historically been on the losing end of MN payments. An update would always happen when I was due to be paid and I'd always go to the end of the cycle it seemed.

I was paid 2x this morning before I updated to .46 and two after I updated. It's like the network is paying me back. :)

I'm betting Otoh is having a banner MN income day.
 
You don't need it, but it can't hurt to be thorough, no?
https://dashtalk.org/threads/v12-release.5888/page-19#post-63972
Yup. who knows what bitcoin has and we inherited it but i don't think it's a big problem.

i read from this: https://bitcoin.stackexchange.com/questions/35707/what-are-pros-and-cons-of-txindex-option

Transaction Database Index and txindex Option
By default, Bitcoin Core builds a database containing only the transactions related to the user’s wallet. If you want to be able to access any transaction with commands like gettransaction, you need to configure Bitcoin Core to build a complete transaction index, which can be achieved with the txindex option. Set txindex=1 in the Bitcoin Core configuration file (from Mastering Bitcoin by Andreas)
 
Try this: put "txindex=1" in dash.conf, delete everything except masternode.conf, wallet.dat and run again with -reindex.
Tried what you said, wallet started fine but as soon as I tried to send funds it throws the following error:

DXVzA2u.jpg
 
Yup. who knows what bitcoin has and we inherited it but i don't think it's a big problem.

i read from this: https://bitcoin.stackexchange.com/questions/35707/what-are-pros-and-cons-of-txindex-option

Transaction Database Index and txindex Option
By default, Bitcoin Core builds a database containing only the transactions related to the user’s wallet. If you want to be able to access any transaction with commands like gettransaction, you need to configure Bitcoin Core to build a complete transaction index, which can be achieved with the txindex option. Set txindex=1 in the Bitcoin Core configuration file (from Mastering Bitcoin by Andreas)


I thought this was the default - no??

txindex=1
 
I hope you already saved your private key? I think probably the wallet.dat is corrupt but if you don't have your privkey saved somewhere else, dump it and import to another v12 wallet. I found the answer for this problem here:
https://www.reddit.com/r/litecoin/comments/212ov2/help_please_i_think_my_wallet_is_corrupt/
I restored an older wallet.dat file from a week old back-up, that worked. What could possibly have caused the sudden corruption of that specific wallet.dat file? I do remember that once one of the wallet.dat files was in use when the automated back-up tried to back-up everything, hence killing the process.
 
Back
Top