MultiBit, MultiDoge & Litemode

Let’s talk Bitcoin, Dogecoin, and Dash Wallets. When I started off with my wallets, I went with the Bitcoin Core QT, Doge Core QT, and the Darkcoin QT (since named Dash). Today, I have MultiBit, MultiDoge, and I am in “Litemode” for the Dash.

I still have the 3 original QT’s, respectively. All have their pros and cons. I had picked the Bitcoin and Doge Core QTs as the “lite” QTs said they might not be the best option for faucet transactions etc. Based on that, I went with the “CORE” wallet QTs to avoid any potential “clogging” as disclaimed on the official sites. Again, I still have these wallets, but I set up the MultiBit, MultiDoge, and made a change up with Dash, and went with the litemode for now, eliminating the Darksend feature.

My laptop was plagued with issues with the wallets I had chosen. My laptop, not the latest and greatest, was overheating and shutting down continually with the QTs. I was having issues with corrupted files from overheating resulting in a shut down and those corrupted files created a lot of work, including establishing new wallets, reindexing, a lot of questions, requiring a lot of help from others, and resynching with the network – all a very long project. But I did learn a great deal in the process.

I want to thank a few people along the way. Of course there is Grim over at RLM and MakingMoneyHoney over at and some of the developers from Dash over at the IRC. I couldn’t have done it with out you! So thank you very much, and for what you taught me. Your tech knowledge, your sticktoitedness, and patience with me is greatly appreciated.

My wallets were such a drain on on the resources that it caused my computer to not just overheat and shut down all the time, but it caused lagging galore. It became unbearable actually. So I set out to research and find solutions. And I have a hard time believing that I am the only one, or that I am the only one with  POS laptop computer.

The solution, and I am sure there may have been other options for the solution, was MultiBit , MultiDoge the “litemode” for DASH

I had to backup my original wallets, and import all my addresses and private keys into the new wallets, and I had to learn a little bit about Windows and .txt files, Java, and about the time stamp and T & Z for to take my new wallets to the starting place (or before) of when I set up my old wallets and began my first transactions. I was able to get R done. I used Multibit .txt as the template basically to mirror for the MultiDoge in terms of laying down the private keys and that time stamp to get it just right (remember the T & Z must be included!!!).

You see, Bitcoin Macroeconomics has an official boycott of Microsoft and runs Linux operating system. So with no Windows, I battled the files with MultiBit and MultiDoge and believe it may have been something to do with Java, so I had to do a bit of a work around. I downloaded the Windows version of the wallets (even though I am on Linux) and utilized Wine to be able to run the Windows version. But at least the work around worked, as the Java files jived! I admit I have battled some file management issues in learning Linux, namely with the Editors, and I never had Java on my computer, but again Java wasn’t jiving with the wallets I had downloaded for install. Where I couldn’t get the Linux versions to work, Windows version worked to give that credit. I ran Windows for years, and I have successfully installed wallets going this route, but I wanted to learn Linux and that was the mission along with getting the new wallets up and running. Wa La!

MakingMoneyHoney provided the technical know how to solve the problem with DASH. It was a matter of back and forth communicating, where I was laying down commands in the terminal….but the solution in the end was going to my DASH launch (consider it a path…) and going to “properties” and using the COMMAND (says command near the middle of the properties menu (had options of Basic and Properties and click properties) and copying and pasting that command and giving that command in my terminal. No sudo apt, no CD, none of that, just the copy and paste of the command as seen. That got me going in the right “path” for DASH. But we battled for about a half hour and got the command just right by adding something like -litemode at the very end.

I asked for a drum roll. I got one. And then I hit enter….sure enough my DASH QT opened in “litemode”, minus the Darksend feature. And then I happy.

With me being the heat sensor, DASH QT ran hot, hotter than hell actually, way hotter than Bitcoin or Dogecoin. Must be a powerful wallet! But it did me no good when it corrupted files and kept overheating my computer. Though it was the hottest, the Bitcoin and Dogecoin CORE QTs were every bit of a drain and still got my computer hot, shutting it down, it’s just that DASH burned up immediately. Surely I am not the only one, and thus this solution to share with others. Hey it worked! Whatever works – works!

Again, I had other options, and looked at Armory and Electrum but chose the MultiBit and MultiDoge. I can still try out any other wallet some day, but not today. Armory looked like a decent option, though I had no idea if it would cause a heat issue, shutting down, or lagging affect.

I was used to the “console” from the Bitcoin and Doge Core QTs for command lines like dumpprivkey so I could import my private keys (which I have had to do as a result of all of this), but there is no “console” in MultiBit or MultiDoge, so that too was a lesson in and of itself, but once I saw it done (via TeamView with the help I got) and by taking notes, and making a few errors the first time, I nailed it. If you don’t get it right, the MultiBit or MultiDoge will say that, as you will not be able to import your old wallet information (coins, transactions and time). I just had to stay on it! But I had about had it and failure was not going to be an option. I had to get the .txt files just right along with the time stamp (I even went back a year prior than my first transaction and that worked!) so remember that, and remember you need the T&Z included in that time or it will not work.

The instructions from MultiBit were helpful, though they are assuming the knowledge base of their users. They may have instructions but I did not feel the instructions went far enough for a step by step and realize there are several operating systems, but I’ll just say I felt they were assuming, which is more a reflection of my abilities, but then again, this is high tech! I think for general adoption of cryptocurrency, there needs to be less assumption that everybody is a Whiz Kid on the computer or operating systems or is a developer. But I did cut my teeth this week and I did learn something. And the main thing is I got 3 wallets working properly.

Remember that you have to get all of your RECEIVING ADDRESSES out of the old wallet (I had to use dumpprivkey command in console, and then it gives you the private key), but the point to be made is, you have to get each private key or you may be leaving your coins behind. You don’t want to leave anything on the table or have someone send coins to an old key and you never know about it, which could happen if you do not import all the keys, so remember that.

Never let anybody see or get your private keys because if they do, they can steal or take your coins without you knowing! Now I had to break the golden rule by getting some help from a friend who helped me with TeamView, but this is the trust factor that you should NEVER have with cryptocurrency! This is something to keep in mind. But one must still learn the technology, the best practices, but also work arounds and solutions the problems, in this case the need to switch to a different wallet.

Bitcoin Macroeconomics also had a problem on the first go around with encryption and that was a hard lesson I have written about too. The lesson is, never load your wallet with any real amount of cryptocurrency UNTIL you know your wallet SENDS and RECEIVES before loading it with any real amount of coin, and that means after encryption. Make sure your encryption works along with your passphrase and test the wallet out so as you know 100% it sends and receives. The developers again may assume that their protocol works for the encryption with a standard, but that is assuming and my advice is to test that it works for yourself – one extra step and precaution rather than a developer knowing their protocol works. Besides there are enough faucets to test your wallet out to ensure it works properly, and that includes after encryption.

Backup and Security. They go hand in hand. Remember those .txt files that had the private keys that had to be imported into the new wallets? You have to erase that off your computer or a hacker or a thief can rifle through your computer and steal your coins man! Get a thumbdrive and (keep good records! Keep good notes, write it down for message to yourself or maybe someone else in case anything happens to you) save not only the private keys there (save the notepad or .txt file) along with the corresponding RECEIVE ADDRESSES, but also the entire backup of the wallet to that thumbdrive.

Then go back and ERASE THE PRIVATE KEYS FROM YOUR COMPUTER. Save that thumbdrive to a safe spot, consider fire proof, and water proof. And best practices would also be to have a backup of the backup.

I am learning, do not put all of your eggs in one basket. It’s a good lesson that rings true with cryptocurrency, so if you are new to Bitcoin remember that. If you are doing cryptocurrency now, you probably know what I mean. You can have several wallets and several addresses! This is a good lesson in best practices! And it is for your own protection. You are in control. You are your own bank and you are your own IT Department. Do it right, and do it right the first time. Backup and Security!

That being said, the next thing I am going to try is the Paper Wallet Generation! But not today. But I am going to boot my computer from disc and generate a paper wallet, literally. With the generation of a paper wallet, there is a math equation that is tied to that RECEIVING ADDRESS and you get a corresponding private key….all on paper. With the transactions, they addresses will be recognized on the Blockchain, and that private key will unlock those coins that are rightfully yours.

With a paper wallet, you can have several wallets …all on paper. Pretty cool right? Don’t put all of your eggs in one basket!  But remember, back up and security. Make sure you have fire proof, make sure you have water proof (consider safe spots and no risk of water damage or mold!). If you go this route, you can have multiple paper copies for backup, and you can also have them where the private key is not in the paper wallet cause if they have the private keys, they can steal your coins! But you can also catch a thief this way too….and some have been known to test out their roommates to see if any coins go missing! That is the beauty of paper wallets and multiple copies and not putting all of your eggs in one basket!

For more on the paper wallets…

Paper Wallet Tutorial: Create a Bitcoin, Dogecoin, or Litecoin paper wallet.

Compliments of MMH

So that’s about all I want to write about for today’s lesson. It was a time consuming effort, but I got R done! And I couldn’t do it without the help of some online friends. And thanks again for the help. I write this and want to give back in the same fashion and do what I can to help the next guy thanks to your efforts. I hope this is helpful for others.

On that note, I will leave with a brief glimpse of the lesson I had with directions on MultiBit, which so far seems like a great wallet, and an option for me that solved my problems so thank you MultiBit, MultiDoge, and DashPay (litemode version) for the options and solutions to my pain in the ass problems. But nobody can say that I didn’t learn something this week! But now my computer isn’t overheating left and right and corrupting files, causing long synching, etc, reindexing, and a continual loop of insanity. (Ref:

The MultiBit, MultiDoge, and DashPay (litemode) synchs way faster on the first time (as you import the private keys or start from scratch) and synchs in general WAY faster than the CORE versions that drained my system causing major headaches. I mean this battle continued and reindexing took a very very very long time, enough that I wasn’t going to quit, but I wasn’t going to keep battling it either, and nor should I have to rush out to get a new computer to stay up on this technology. In the end, the solutions were the lite versions as mentioned.

Smooth sailing from here on out! And I am glad I was able to rely on some people to help me learn some things. This was brain surgery this week! But it all helped in learning the stepping stones of Bitcoin and other cryptocurrencies.


Leave a Reply

Your email address will not be published. Required fields are marked *