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

Backups........ I would like some advise please.

MrZilch

Member
Hey guys.

Im wondering how you guys deal with your backups? Im about to spin up another MN and just want to check im on the right track for my backups. So far I have been saving my wallet.dat file and also the config file. If I have more than one MN in a wallet do I need to do anything different??

I would quite like to be able to save the priv keys for the MN's on encripted paper wallets. Im not sure if this is a good idea so bear with me. Im can dump the priv keys of each mn but then im wondering how I would encript the priv key to bip38 format. (or what ever it is) Also I would plan on leaving the priv keys in the wallet file (encrypted of course) Is this a good idea. I thought if I was ever need to access the coins quick and with out my qt client I would be able to sweep the paper wallets. Do you guys do this? edit: I have just thought I could generate the encripted MN paper wallets offline and then import the priv get into my qt??

I also have a tresor. Im not sure if this can help me in some way?

basicially : I plain on having a few mn's in a wallet file and I want to make sure my backups are fine. I have read some posts other people have on here about Backing up to USB on a weekly basis. (is this nedcessary)

If someone could ELI5 the best way to backup their masternodes I would be very happy. Thanks again.
 
For me I backup my wallet(encrypted) to a VeraCrypt volume. And of course use different password. Then backup the VeraCrypt volume in different location (more than one backup). Just in case 1 volume fail. I don't think weekly base backup is necessary if you are not creating any new address for the wallet.dat

I am not sure whether a trezor hardware wallet can be used to host Masternode. Maybe others have Trezor can tell.
 
Saving wallet.dat to an "undisclosed location" is a good idea, the config file only important so you don't have to remember your setup.

I think it is a good idea as well to "dumpprivkey" for each of those 1000 coin addresses - then save those keys somewhere safe...
from what I have seen, the private keys are a more fail-safe remedy than a copy of wallet.dat if you run into problems (like a corrupt wallet.dat file).

Note: the wallet itself creates backups for you - in the backups folder of your Appdata\Dash directory unless you specify createwalletbackups=0 in dash.config (which some people do for security reasons).
 
For me I backup my wallet(encrypted) to a VeraCrypt volume. And of course use different password. Then backup the VeraCrypt volume in different location (more than one backup). Just in case 1 volume fail. I don't think weekly base backup is necessary if you are not creating any new address for the wallet.dat

I am not sure whether a trezor hardware wallet can be used to host Masternode. Maybe others have Trezor can tell.


Thanks for your input :)
 
Saving wallet.dat to an "undisclosed location" is a good idea, the config file only important so you don't have to remember your setup.

I think it is a good idea as well to "dumpprivkey" for each of those 1000 coin addresses - then save those keys somewhere safe...
from what I have seen, the private keys are a more fail-safe remedy than a copy of wallet.dat if you run into problems (like a corrupt wallet.dat file).

Note: the wallet itself creates backups for you - in the backups folder of your Appdata\Dash directory unless you specify createwalletbackups=0 in dash.config (which some people do for security reasons).


Ok . so your saying all I really need is the wallet.dat file and the config file is not so important. Also yeah I would be more happy with the priv keys as well as the wallet rather than just the wallet. What do you think about my idea :

Generating Offline Encrypted Paper Wallet.
Importing the priv key of that Paper wallet to my QT client.
Sending the 1000 Dash to these Addresses. (paper wallet & also the priv is on your qt as well.)

The idea is if the shit hits the fan and my hdd fails, or memory stick failure or any digitial failure, I also have a Physical encripted Paper wallet I can quickly sweep the keys from if need be.? Thoughts ? will this work?
 
im wondering how I would encript the priv key to bip38 format.

get your wifs
in the wallet, debug window, unlock your wallet 'walletpassphrase <yourpassword> 600'
export your masternode wif's using 'dumpprivkey Xaddressofyourmasternode1000dash'
copy the wifs to a file on a thumbdrive, these are your unprotected private keys
you'll want to wipe this thumbdrive when done.

goto https://walletgenerator.net/ ignore the ssl warning, download the html to a thumbdrive (same, another, doesn't matter)

unplug your internet, or use a laptop with no networking, attach a printer.

open the html file, seed the random generator with movement, choose dash in the upper-right dropdown
click paper wallet
check bip38
enter your bip38 passphrase (don't forget this or you'll lose your coin!!!)
paste in a wif
hit apply, print your bip38 encrypted paper wallet.
paste in another wif
hit apply, print
repeat as needed


I also have a tresor. Im not sure if this can help me in some way?

I don't know anything about trezor support yet, but I do know that it's supposed to be supported.
http://satoshilabs.com/news/2015-04-07-trezor-firmware-1-3-3-connect-api/

If someone could ELI5 the best way to backup their masternodes I would be very happy. Thanks again.

The best way is to not have to keep backups by generating your own addresses using bip32 from a very strong passsentence.
Not an eli5, but worth learning if you want to not worry about backups anymore:

http://en.wiki.dashninja.pl/wiki/DIY_Deterministic_Addresses
 
Generating Offline Encrypted Paper Wallet.
Importing the priv key of that Paper wallet to my QT client.
Sending the 1000 Dash to these Addresses. (paper wallet & also the priv is on your qt as well.)

That will work fine, but qt doesn't import bip38 keys. You'll have to use your wif for qt.

So you'll have to generate a paper wallet, copy the wif, bip38 encrypt it, print it.
Then import your copied wif into qt.
 
That will work fine, but qt doesn't import bip38 keys. You'll have to use your wif for qt.

So you'll have to generate a paper wallet, copy the wif, bip38 encrypt it, print it.
Then import your copied wif into qt.

yeah so when your saying wif, your referring to your private key?
 
get your wifs
in the wallet, debug window, unlock your wallet 'walletpassphrase <yourpassword> 600'
export your masternode wif's using 'dumpprivkey Xaddressofyourmasternode1000dash'
copy the wifs to a file on a thumbdrive, these are your unprotected private keys
you'll want to wipe this thumbdrive when done.

goto https://walletgenerator.net/ ignore the ssl warning, download the html to a thumbdrive (same, another, doesn't matter)

unplug your internet, or use a laptop with no networking, attach a printer.

open the html file, seed the random generator with movement, choose dash in the upper-right dropdown
click paper wallet
check bip38
enter your bip38 passphrase (don't forget this or you'll lose your coin!!!)
paste in a wif
hit apply, print your bip38 encrypted paper wallet.
paste in another wif
hit apply, print
repeat as needed




I don't know anything about trezor support yet, but I do know that it's supposed to be supported.
http://satoshilabs.com/news/2015-04-07-trezor-firmware-1-3-3-connect-api/



The best way is to not have to keep backups by generating your own addresses using bip32 from a very strong passsentence.
Not an eli5, but worth learning if you want to not worry about backups anymore:

http://en.wiki.dashninja.pl/wiki/DIY_Deterministic_Addresses


Thanks very much for your response. Im picking up what your putting down however im a little confused about one point :

You said you generate the priv key on your qt client then dump it then transfer to usb. Use that USB in another ofline computer and then using walletgenerator.net or what ever convert the priv key into its bip38 version? Can you do this? In the past when making bip38 paper wallets Im not sure if i can do this with the priv key or if its done when generating the priv key in the first place? I mean can you paste your priv key into wallet address generator then get its bip38 version?? ( sorry if im confusing)
 
Thanks very much for your response. Im picking up what your putting down however im a little confused about one point :

You said you generate the priv key on your qt client then dump it then transfer to usb. Use that USB in another ofline computer and then using walletgenerator.net or what ever convert the priv key into its bip38 version? Can you do this? In the past when making bip38 paper wallets Im not sure if i can do this with the priv key or if its done when generating the priv key in the first place? I mean can you paste your priv key into wallet address generator then get its bip38 version?? ( sorry if im confusing)


wif is 'wallet import format' and is one form of a private key. It starts with X

Try the instructions online (one computer, no usb key) with a throwaway/temp key and see how the process works to get the hang of it.

And, don't forget, once you have a paper wallet:

  • print two copies, keep them in two locations
  • never photocopy it on a shared, public copier (they store copies)
  • laminate it to protect from water damage
  • even if encrypted consider it as weak as your password -- make it a good, long one: https://masternode.me/smart_passwords.html
All that said, I still recommend generating your own addresses (bip32) from a smart passphrase (as above).
And since you're dealing with raw keys and addresses, no software issues to deal with.
(like the fact that you can't import encrypted keys into the qt wallet)

Then all your backups could burn and you'll still have control of your coin.
A bit of effort to learn the technique for a lot of security and peace of mind.
 
...
edit: I have just thought I could generate the encripted MN paper wallets offline and then import the priv get into my qt??
...
You can create bip38 address but you'll have to decode it first (using "Wallet Details" tab on walletgenerator.net) to be able to import it into Dash Core wallet.

...
I also have a tresor. Im not sure if this can help me in some way?
...
...
I don't know anything about trezor support yet, but I do know that it's supposed to be supported.
http://satoshilabs.com/news/2015-04-07-trezor-firmware-1-3-3-connect-api/
...
No Trezor support in Dash Core but there is one in Encompass:
https://dashtalk.org/threads/electrum-dark.3845/page-15#post-53171
https://bitcointalk.org/index.php?topic=1067166.0
https://github.com/mazaclub/encompass/releases/tag/v0.5.0

Encompass however doesn't support any MN/DS/IX functionality.
 
Back
Top