eduffieldI guess you missed this question:
-> Is the original private key alone still enough to spend the coins after someone uses the corresponding public key for masternode qualification but shuts that masternode down?
If the answer is yes, then I can't see what you meant here:
In this case, one could also encrypt the wallet.dat with a random key and immediately destroy it forever (so even you don't know it) with a single key pair inside and print out the private key as a paper wallet which can be kept somewhere safe (e.g. not in your house and/or next to the server hardware).
When you decide to shut the node down and spend your coins, you simply delete your wallet.dat and import the private key from the paper wallet to a freshly generated wallet.dat
That's not really going to work. Upon starting the masternode up, it's going to need to sign the input with the 1000DRK to show you own it. After that all messages will use a separate key, so the wallet can be encrypted until the next restart.
If the original private key alone is enough to spend the coins later then I can't see the problem with that private key existing on a paper wallet only.
In that post, I meant you destroy the wallet.dat passphrase, not the wallet.dat itself, nor the public or even the encrypted (but technically never decryptable) private key inside it.
I wish to destroy the wallet.dat passphrase, so nobody will ever use that wallet.dat to spend the coins (only a person with physical access to the off-site/hidden paper wallet will be able to).
---
This is a serious question because I already risked to loose my 1000 DRK if the original private key is not enough to spend the coins.
(I didn't immediately backed up the wallet.dat after becoming a masternode because I thought the original wallet.dat is enough.)
-> And what if I loose my IP address?
(It's only semi-static. It haven't changed since months but it's theoretically still dynamic.)
I think we should put together a FAQ of questions like these ASAP because I get the feeling that I took too much risk by participating in this BETA.
