renaming MN wallet.dat file

semajjames you have hot cold setup for your masternode right?

If so, the server - your vps machine, keeps your masternode online.
Your local PC which has the wallet.dat with the 1000 coins can be shut down in any time, you can rename the wallet.dat to what-ever-name you want but when you`ll start the client again you need to rename it to wallet.dat so the client will read the data from the wallet.dat which has the coins, otherwise the new, empty, wallet.dat will be created....
Clear enough? :)
 
You can rename your wallet and put it to your shortcut -wallet=walletname.dat, no need rerename.

Edit. Corrected-wallet=
 
Last edited by a moderator:
@up, NEVER change the name of wallet.dat when the client is running.
 
When I was running 20 MN's for various individuals - I made a wallet.dat file for each one
MN0.dat
MN1.dat
etc
etc

You just have to change the MN0.dat to wallet.dat to view the wallet file in the Qt.

I also made a separate masternode.conf file for each MN ......etc etc


hope that helps
 
Ok, thanks for the ideas. Hadn't thought of that. But still, this is something an HD wallet could help immensely with -- no more ".dat" files to manage.
 
sorry again
so (wallet shut down)
can I rename my .dat into tungi.dat or not ?
do I have to rename it to wallet.dat before I start wallet ?

I have multiple wallets + MN's and I keep them all in separate / different named folders .... but sometimes I get tangled up (late night , doing too much ) and then a clear naming system of .dat files would definitely help
 
sorry again
so (wallet shut down) = 1
can I rename my .dat into tungi.dat or not ? = 2
do I have to rename it to wallet.dat before I start wallet ? = 3

I have multiple wallets + MN's and I keep them all in separate / different named folders .... but sometimes I get tangled up (late night , doing too much ) and then a clear naming system of .dat files would definitely help


Y'ES!! = 1
and
Y'ES!! = 2
and
Y'ES!! = 3


you got this.......
 
HD wallet?

explain....

HD stands for Hierarchical Deterministic... it's what Electrum's used from the beginning. One seed to remember, nothing else to back up, ever. With BIP32, you can have multiple levels, paths you can descend into. You can give out a public key and have someone else generate unique addresses to your wallet without them ever having access to the private keys. Seriously, read up on BIP32, it might blow your mind.

Bitcoin's had this (via Electrum & other wallets) since before Darkcoin was ever released. I'm really surprised more people in here aren't pushing for things like this.
 
semajjames you have hot cold setup for your masternode right?

If so, the server - your vps machine, keeps your masternode online.
Your local PC which has the wallet.dat with the 1000 coins can be shut down in any time, you can rename the wallet.dat to what-ever-name you want but when you`ll start the client again you need to rename it to wallet.dat so the client will read the data from the wallet.dat which has the coins, otherwise the new, empty, wallet.dat will be created....
Clear enough? :)

Yes the wallet.dat containing the 1000 coins is on my local pc and shut down,
So it's as i thought if the client is shutdown then the .dat file can be renamed and a shortcut made to then start the client with the correct .dat file
I get that
the bit i'm not sure about is:-
If the online MN restarts either automaticaly or manualy for whatever reason how does it know to use the new shortcut/renamed wallet.dat file when restarting ?
 
Masternode only see your 1000 Dash tx, not wallet.
Wallet filename is irrelevant.
 
Back
Top