Depends on you definition of hard... if you consider aes256-cbc encryption "hard" (and you should)... then yes, it is hard to decrypt the encrypted seed in your Electrum wallet file.

If you don't have the seed phrase or the wallet password, it is going to be difficult to recover your coins. At this stage, using "btcrecover" script is likely to be your best bet for recovery.

This looks bad:

Basically, it can't find your Bitcoin Core blocks... although, that error is from the 7th July...

Did you pick and choose a couple of errors that you thought might be relevant? You really should post the WHOLE file... if you're selectively picking entries from the .log file it makes it difficult for folks to see what is really going on.

Seems like the earlier errors you posted would indicate that your Bitcoin Core blocks might be corrupt... but yeah... post FULL logs

MB Classic and MB HD are two very different wallets... you need to use the "find_unspent_multibitHD_txes.py" script... it should hunt through your wallet and find the unspent UTXOs...

Although it may struggle if it thinks you have unconfirmed transactions...

Also, if "Breadwallet" or "Simple Bitcoin Wallet" came up with a zero balance then that isn't normal. Have you checked your addresses from MBHD on a blockchain explorer like blockchain.info to see if there ARE actually unspent coins on your addresses?

Where exactly "online" are you attempting to use your signed message? Are you attempting to claim coins/tokens from an ICO or giveaway like Stellar Lumens or something?

Are you using a standard wallet or a multisig/2FA wallet?

You can't... you're using MultiBit HD... it isn't at all compatible with MB Classic... and it doesn't support exporting your private keys directly. Unfortunately, as you have discovered, MBHD has some real issues at the moment, and the devs seem to be MIA... there hasn't been any updates in months!

You have a few options:

1. 'Restore' your seed into "Breadwallet" (iOS or Android)... or "Simple Bitcoin Wallet" (Android only).  These wallets use the same "Derivation Path" as MBHD, so will restore your wallet/addresses/transactions correctly.

2. If you're at all familiar with Python and running scripts, you can use my extractor scripts to get the addresses/private keys containing coins out of your MBHD wallet file

3. You can achieve the same thing as Option 2, by following the manual process below:

• Step 1. Create an offline copy of the BIP39 Mnemonic Code Converter: https://iancoleman.github.io/bip39/ (instructions at bottom of the page)
• Step 2. Put your MBHD seed phrase in as "BIP39 Mnemonic"
• Step 3. Click "BIP32" under "Derivation Path" section
• Step 4. Set "Client" dropdown to "Custom Derivation Path"
• Step 5. Set the "BIP32 Derivation Path" to: m/0'/0
• Step 6. All your addresses/private keys for "Receive" addresses will show at bottom of the page (you may need to click "show more" if you have a lot of used addresses)
• Step 7. Set the "BIP32 Derivation Path" to: m/0'/1
• Step 8. All your addresses/private keys for "Change" addresses will show at the bottom of the page (you may need to click "show more" if you have a lot of transactions)
• Step 9. Sweep (or import) the private keys you have generated from Steps 6 and 8 into another wallet (I'd recommend Electrum)
• Step 10. Be Happy!

You'll probably find that when you uninstalled it, Windows only removed the actual program installation directory in the "program files" directory (ie. C:\Program Files (x86)\Armory)... however the data (including wallet files) is all stored in the "%AppData%\Armory" directory... Windows is actually pretty terrible and uninstalling things properly

So, when you reinstalled and ran Armory, all the existing data would still have been there and that is why it all showed up automagically

Glad you managed to get it all sorted tho... 

If your coins were in that wallet when the snapshot was taken, you should be able to claim them... I wrote some detailed instructions (on how to get access to the private keys you need to be able to claim Lumens from an Electrum 2FA wallet) in this post: https://bitcointalk.org/index.php?topic=1989369.msg19853098#msg19853098

As noted, this method is completely untested by myself, as I didn't have any coins in a 2FA address, but in theory it should provide you with the "1" addresses and private keys you need to be able to create the signed message required.

Did you get a chance to try the little util I coded up for you?

If so, did it manage to extract any addresses/keys from your wallet? If not, did you get any errors?

Yes, from Bitcoin Core, the wallet.dat file is everything... If you have that, it is generally a simple matter of reinstalling Bitcoin Core, running it once so that it sets up a wallet.dat... shutting it down and replacing the new wallet.dat with your recovered wallet.dat. Start Core up and all your addresses should be available. NOTE: unless the new instance of Bitcoin Core is sync'd, you may not see the transaction history or correct balance (but you can still access private keys/addresses etc).

Obviously, you'll also need to know the passphrase (if any) for your recovered wallet.dat file to be able to access the private keys and/or spend coins

Perhaps this could be done via voting for nominated posts of your choosing... ie. while auditing posts for content/quality (or maybe campaign participants could also nominate others that they see making quality posts?)... Pick the top 3-5 posts that you think are of good quality (regardless of rank/post count etc) and put up a post with links to the posts and run a vote for a couple of days?

You'd likely want to make it a self moderated thread to help keep it tidy... and you'd probably want to make it so that only campaign participants can vote to prevent "cheating" by spamming votes using alts? Or make it so only Sr. Members and up could vote?


ps. thanks for accepting me

Just FYI, ChipMixer is now FULL, and looks like it might have something of a waiting list... so probably now classed as CFNP

https://bitcointalk.org/index.php?topic=1935179.msg20385050#msg20385050

Bitmixer was a massive outfit... If you read the closing down thread, Bitmixer claims their service was valued at 5-6 million...
The volume required to be generating that level of value is pretty massive. No doubt that volume is now being spread across the remaining mixers like ChipMixer. I am not surprised there was a "run" on the available stock of chips... A sad day for BTC and privacy, but a window of opportunity for ChipMixer!

What I also expect to see is a sharp increase in the number of "scam" mixers popping up... outright scam sites AND "clone" scams... be careful, double check your URLs etc.

Don't bother with anything either of those two users wrote... My guess is they are either sig spamming... or very confused and didn't read the OP correctly.

One seems to be talking about ETH (and possibly ETC)... perhaps confusing Ethereum and Electrum, when you said you "moved your bitcoin account to Electrum" and believing you had converted your BTC to ETH/ETC The other is just talking rubbish... These days, you cannot realistically mine your own BTC transactions... not unless you happen to own a massive mining pool/farm

Did you manage to get your balance all sorted? And is that error "unmatured" from an English version of Electrum or are you translating that from another language? I ask because I've only seen "unconfirmed" and "unverified"

minrelaytxfee is used to define what the minimum fee should be on a transaction for your node to relay it...

mintxfee is the minimum fee that the client will create a transaction with...

So, if minrelaytxfee is set to 0.00001 your node will happily relay any transactions with that fee or higher (ie. yours and other peoples txes)... however, if you then set mintxfee to 0.00005, then any transaction you create will have that value as the minimum possible fee, but you'll still relay other peoples txes with fees of only 0.00001.

As for minrelayfee and limitfreerelay... you'll see the reasoning if you read here: https://en.bitcoin.it/wiki/Transaction_fees#Relaying

minrelayfee is effectively the "free" level... but relaying rules don't include the 0.01 BTC output minimum requirement (refer: https://en.bitcoin.it/wiki/Transaction_fees#Historic_rules_for_free_transactions).... so, to prevent a DoS attack of a bunch of transactions with tiny outputs and with the minrelayfee, you can set limitfreerelay and your node will only relay X thousand bytes per minute to throttle any spam

In the Armory directory, you should find the debug logs... dbLog.txt and armorylog.txt... they're just text files, open them in a text editor of your choice and scroll all the way to the end of the file... see if there are any obvious errors being output...

Alternatively, copy/paste the content of the log files to pastebin.com and post the links here so people can check for errors.

The english version shows as:

It is just a warning about social engineering really... basically it says "don't just blindly copy/paste commands and/or the output to anyone that asks for it"...

Honestly, newbies probably shouldn't be playing with the debug console anyway But, hopefully the warning is scary enough that anyone looking at the console will properly investigate what a given command actually does before they try and execute it!

what does your dbLog.txt debug file show? Are there any obvious errors being shown there?

You might want to check the armorylog.txt as well... see if there are any errors when spawning the bitcoind and ArmoryDB processes... and double check that the "satoshi-datadir" is showing the correct path to your block folder.

What do you have under "File -> Settings -> General"...

Is the "Let Armory run Bitcoin Core/bitcoind in the background" box checked?

Are the file paths correct for your install? Did you install Core (or setup the Core data directory) in a "non-standard" location? For instance, my Core install is in C:\Program Files\Bitcoin but I set the Data directory to be E:\Bitcoin (dedicated drive for blockchain data):

There is no way for that website to produce anything useful under "wallet name" unless you give them that info... You could call your wallet "My super awesome wallet of awesomeness" and that information resides solely on your PC.

In fact, that website is pretty much guessing at most things... I suspect all they are attempting to do is crawl the web looking for bitcoin addresses listed on websites and tying them to businesses and/or usernames from forums etc... I wouldn't take anything that website says as being accurate.

As for your transaction not showing up... does Armory show that it is up to the same block height as Core? Current blockheight is: 477448... Your transaction into that address was in block #474666:

If Armory has not processed up to at least block 474666, then there is no way for it to show/include your transaction in the history...

2/10th's of not very much... It's small enough that you can run Electrum on a mobile phone without stressing too much about data.

I believe the block headers take up something like ~37 megs on disk (mine is currently 36.4megs)... most of the "heavy lifting" is shifted over to the Electrum Server that you connect to... you send a request (ie. please scan for address "1bitcoinAddress"), the server hunts through the blockchain and returns the relevant data... That is how SPV clients like Electrum operate.