And be mindful of the fact that ViaBTC still measure in the "old school"... so if the fee you have used is 10 sats/vbyte... it will not be calculated by them as 10 sats/byte if you're using SegWit!

When you say "empty", do you mean the balance is zero but there are transactions listed? Or do you mean that there is no transaction history showing either?

Also, is your Bitcoin Core actually fully synced?

Where is your Bitcoin Core synced to?

That previous transaction was confirmed on the 9th December 2020, in block 660607... so if your Bitcoin Core has not synced up to that block, it won't show the correct status for that transaction. Once it has synced, the status of that transaction will be shown correctly.

If your Bitcoin Core is already synced past that block, and it still isn't showing correctly, you may need to use rescanblockchain from the console.

Excellent... glad you got it sorted.

Also, a big "hi-five" for coming back and explaining the exact steps you took to get it working rather than just saying "I fixed it" and then disappearing. This will hopefully help someone else in the future who stumbles across this thread while trying to solve a similar problem.

The "datadir" is where the "blocks" and "chainstate" folders are... so what you have called "The Bitcoinfolder". So, create a file in that folder called "bitcoin.conf"... then add the "server=1" line... then restart Bitcoin Core.


To fully understand why things are not running correctly, you would need to post your log files. Copy/Paste the contents of your log files (armorylog.txt and dbLog.txt) to pastebin.com and then post the URL that is generated when you click "create new paste"

Note: you can also use the "Export log file..." File menu option within Armory to create the log files.

It doesn't need to version match for coin control to work... You just might find some issues with the format of the unsigned transaction data being unable to be imported into older versions for signing.

"Coin Control" will simply prevent Armory from using any "unselected" UTXOs to create the unsigned transaction. They just won't be included as inputs. So, once the raw unsigned transaction has actually been created without the dust UTXOs by the online machine, then the offline machine won't care... it will just be signing the transaction (it shouldn't be modifying inputs/outputs etc).

Any "valid" seed will allow you to generate a wallet and restore the addresses... empty or not. Electrum allows a user to create multiple wallets. It would appear you have written down a "valid" seed, but for a different wallet.

Electrum always highlights your "receiving" addresses as green... your "change" addresses as yellow... whether they are used or not, and whether the wallet has any history. A completely empty and unused wallet will still show "green" addresses.

If the "history" tab is empty, then your wallet has no history and you have the wrong seed.


You don't have to wait for large sum... he was saying that if you're still mining, you should increase the payout threshold. Having a lot of small value UTXOs, will make any transaction you attempt to send have a large total data size... because the total fee paid for a bitcoin transaction is based on the total data size (regardless of the value actually being sent), then because your data size is very large, the fee will end up being very large too.

This is why people who got tiny amounts of faucets and mining etc end up paying huge fees to send their bitcoins By increasing the payout threshold to something like 0.001 BTC, it helps avoid some of those fee costs.


most likely "default_wallet"... any extra wallets get named "wallet_1", "wallet_2" etc... unless you changed the name when creating the wallet. Then it is impossible to say what the file would be called. Note that Electrum does not use any file extension like .wallet or .dat etc.

Depending on the OS you were using, the wallet file(s) would be stored in a folder called "wallets" in one of these locations:

Not in a single transaction, you're only allowed a single OP_RETURN. So, you'd need to create multiple transactions, each with an OP_RETURN.


The issue  you're going to face with that "solution" is that while your node would then ignore the OP_RETURN data size and try to send the transaction out, every other node would reject it... unless you could find a friendly miner that agreed to manually include the transaction directly into a block, your transaction would not propagate across the network well (or at all) and would not be seen by any miners.


ps. The Bitcoin blockchain is not really designed for storing "arbitrary" data like this... it's borderline "spam"

Double check that the addresses that have been created in Electrum start with a "1"... if they don't, then you've selected the wrong script type when restoring the wallet. Make sure that you select "Legacy (p2pkh)" and then set the derivation path as: m/0'

If they do start with a "1"... and you had the derivation path selected correctly... and there is no history showing in Electrum, then unfortunately it would appear that your father has a "valid" recovery phrase, but not the one that was for the wallet where he received the coins.

Note that MultibitHD allowed a user to create multiple wallet files. So, if your father has no other seed phrases, I would suggest taking BitMaxz's advice and looking for mbhd.wallet.aes files in the "C:\Users\...\AppData\Roaming\MultiBitHD" folder.

I believe what is required for an "attack" like that is:

- The Master Public Key
- At least one Private Key

As described here: https://bitcointalk.org/index.php?topic=657205.msg7385160#msg7385160

If you just have 4 private keys that get compromised, then there is no way to derive the other keys.

It also depends, to a certain extent, on whether or not the keys are "hardened", as per this Trezor wiki entry:

I don't believe you can "freeze" the UTXO... the best you can do is use the "expert" feature of "Coin Control" and just make sure that any "dust" UTXO is not selected when you're sending coins.





Correct... to avoid any compatibility issues, the online and offline versions of Armory that you're using should be the same.


Armory, by default, creates and uses change addresses if that is what you're asking... you don't have to explicitly set the change unless you want full control over the exact address that the change is actually being sent to.

It'll be your setup with Bitcoin Core... by default, Bitcoin Core doesn't have the the RPC enabled for other apps.

Shutdown Armory and Bitcoin Core. Then, add the following to your "bitcoin.conf"

Then restart Bitcoin Core. Then restart Armory.


NOTE: you may need to create the bitcoin.conf as it is not created by default. It should be place in the Bitcoin Core "datadir"... you can find the location of this directory by looking at "Window -> Information" dialog in Bitcoin Core.

Ideally, you should have your Armory "Root Key" paper backup somewhere... this would allow you to easily restore your wallet in a new installation.

Theoretically you could simply copy the .wallet file over to the new install, but I wouldn't recommend it unless you have no other option for recovery.


To get Armory up and running on the new computer, you'll need to:

1. Download the latest version of Bitcoin Core: https://bitcoincore.org/en/download/
2. Install Bitcoin Core and get it fully synced (do NOT enable "prune" mode!)
3. Download the latest version of Armory: https://btcarmory.com/releases/ (currently v0.96.5)
4. Install Armory and run it

Once you have Armory+Bitcoin Core running successfully, let us know what files you have available to continue with the recovery.

Is it similar to this case about old blockchain.info "Alias Identifiers"?

In any case, I would recommend that you contact "blockchain.com" support and ask for their assistance. They'll be in the best place to advise on how you can go about regaining access to your wallet based on what you currently have and/or can provide in the way of account id.

When bitcoin-qt is first run, it should automatically create a .bitcoin directory in the users "home" directory aka ~/.bitcoin and it should prompt to ask where to set the datadir to. If you've already used that, you can try a couple of things to "move" the datadir:

In the .bitcoin directory, if you create a "bitcoin.conf" file... you can add the datadir option and set that to where you want the blocks stored...

Alternatively, simply start bitcoin-qt using the "-choosedatadir" option... it'll prompt you again to choose where you want the datadir to be set to.



NOTE: be wary of the "discard blocks after verification" (prune) option... that could cause problems later if you need to import private keys or rescan/reindex. I would suggest leaving it "UNCHECKED" if you have the storage space to store the full blockchain (350+gigs)


Also note that neither of these options will "move" the current contents of the datadir to the new location... so bitcoin core will start syncing from block 0 again.

Yes, you can use rescanblockchain command on the console (windows -> Console)... or you can shutdown Bitcoin Core then restart it with the -rescan parameter. That will force Bitcoin Core to rescan all the blocks on disk looking for transactions relating to your wallet.

If rescan fails to find the "missing" transaction, then you can try using -reindex and that will force Bitcoin Core to reindex all the blocks (so anything that is corrupted/missing will be redownloaded and rescanned etc).


NOTE: If your node is "pruned", rescan and/or reindex will force a redownload of everything!!

Try using bitaddress.org (download and run offline)... click on "wallet details" tab, paste in the "5" WIF key and get the "compressed" WIF that starts with a "K" or "L"... then import that into Electrum, see if that shows your funds.

If it doesn't, then blockstacks was doing something "weird" in regardless to private keys etc... or that key isn't the one that holds your coins.

Most likely has the "Fiat" value set to BTC in Tools -> Preferences -> Fiat:

Starting with a "5" seems like it is an "uncompressed" WIF private key... try importing it into Electrum and see what you get. It should generate an address that starts with a "1".

That sounds like it/7Yes, theoretically, that should all work out...

Once you have all the .bitcoin folder copied over... when you start bitcoin-qt and select .bitcoin as the location for your datadir, it should find the blocks, start up and continue syncing without needing to redownload everything

Let us know if you run into any more issues... as mocacinno said, someone should be around to help out