Das offensichtlichste... nichts.

Die Person weiß rein gar nichts über dich.

Es wurden einfach alle öffentlich zugänglichen Mail Adressen genommen um diese Mail an die Adressen zu schicken.
Einige Leute werden Angst bekommen und das für was ernstes halten und zahlen.. So oder so wird nichts passieren. Das ist einfach eine automatische Mail die an alle geleakten Adressen raus ging.

Du brauchst dir wirklich keine Sorgen machen.

The xpubs always have been stored in plaintext.

The file app.json contains all necessary information for ledger live (xpubs, accounts, balances, timestamps, ...). It is not encrypted. The ledger live password is only used to lock the view.
It does not encrypt/decrypt anything. It is purely just for locking the application. All data which is shown inside of ledger live is still visible if you look at the raw file.

The new update didn't make it worse. It always has been like this. 

Schön zu hören, dass du wieder Zugriff zu deinen Coins hast.

Ist natürlich in dummer Zufall, dass die ersten 12 Wörter deines 24 Wörter langen Mnemonic Codes auch einen validen BIP39 Mnemonic Code ergeben.
Die Chancen liegen dafür bei 1/16. Das zusammen mit dem Ausversehen nur dieser Wörter beim ersten mal zu verwenden... ist schon ein Pech.

Aber immerhin hast du es rausgefunden. 

Unfortunately this is the beginning of your log file and doesn't contain any relevant information and doesn't show anything which would cause the issue you have.

Could you please upload the whole log file to pastebin or any similar service, then provide us the link.
Feel free to replace all personal information (you can use the replace all feature in most text editors to replace your username with some x's).

You wouldn't always need to carry your air-gapped wallet with you.

Depending on the situation, you might be able to get the address you'll need to send the funds to prior visiting the store.
Then you could already create and sign the transaction at home (not broadcasting it!) and take it with you to the store.

When making the trade, broadcast the transaction there.

This would obviously require you to know the address and the amount you are going to sell before going to that store.
I don't know how applicable this is to your situation.

Just for the purpose of a safer backup, you don't necessarily need a multi sig wallet.
This just makes any transactions bigger in size and therefore more costly.

I mean, that's definitely an option and better than a single point of failure. But i'd prefer a secret sharing scheme over multi sig as a backup spread between multiple locations if N out of M pieces should be required.

The upside is that you can basically store any sensitive information that way. Private keys, mnemonic codes, passwords etc..
And always the property holds that if someone has N-1 shares, no information about the secret is leaked.

You didn't verify the authenticity yet.

All you did was to compare that the hash of your downloaded file matches the hash posted on github.

What you additionally want to do is to verify that these are the correct hashes.
The file you have linked (sha256sum.txt.asc) is a signed file. You need to check that the signature matches goatpig's PGP key, which can for example be found on github.

Only after that signature matches, you can be sure that your downloaded file needs to have that hash to be the original file signed by goatpig.

Could you provide the complete log file?
This snippet is not showing whether there is an error between the connection of armoryqt and armorydb or armorydb and core.

You can upload your logs using pastebin or any other similair service.

Also, since you went online once.. did you change something afterwards? Any configuration?

You can create that file with a text editor, but you need to save it as bitcoin.conf and not as bitcoin.conf.txt

If you are on windows (what i am assuming), then it might be helpful to enable the option to show file extensions, which makes it easier for you.

You can choose the correct fee rate yourself.

Visit https://core.jochen-hoenicke.de/queue/#0,8h and scroll down to the 3rd graph (Mempool Size in MB). Check the very right (hover over it with your mouse).
You need to choose a fee within 1 MB of the tip at the moment a block is being found/built to get your transaction included.

So, for a confirmation in the next block, a fee of 40 sat/vB would be required.
If you don't need it to be confirmed within a a few blocks, a way lower fee (e.g. a few sat/vB) is absolutely ok and saves you your precious BTC.

Laut deren API, verwenden die kein Hardening und der Derivation path für Segwit Empfangsadressen ist

Hast du diesen Pfad schon einmal probiert?
Zudem finde ich es sehr komisch, dass du einen xpub bekommst wenn es sich um segwit adressen handelt.

Leider ist es auch nicht immer so einfach den xpub einfach in einen zpub zu konvertieren.

Wenn es mit dem oben erwähnten Derivation Path und deinem konvertierten zpub nicht funktioniert, bleibt dir wohl nur übrig BitGo's Recovery Tool zu verwenden.
Eine andere Möglichkeit sehe ich jetzt nicht.

Ist schon alles sehr non-standard was BitGo da macht..

Dem kann ich nicht zustimmen.
Bei mir läuft Kraken immer so wie es soll.

Gelegentlich gibt es Wartungsarbeiten, ja. Aber das hält sich meiner Meinung nach im Rahmen.
Kann da wirklich nicht klagen.

Sicher, dass es nicht an deinem Internet (oder den anderen Personen die deine Leitung mitbenutzen) liegt?

If i am not mistaken, satoshi himself said that mining will be somewhat concentrated in the future.

And this does not contradict with the fact that every person running a full node validates the complete blockchain, every block and every transaction coming in.
Validating is not mining.

Mining at home with your pc isn't feasible for quite some years now. And IMO there is nothing wrong with it.

This is only possible if you have send the coins from coinbase to the wrong address i.e. not to the address given by your ledger.

Since you know the address you sent the funds to.. does this address appear in ledger live or electrum?

Do the addresses shown by electrum start with the same char (1.., 3.. or bc1..) ?
If not, you need to choose the correct script type:

• P2PKH for addresses starting with 1..
• P2WPKH for addresses starting with bc1..
• P2PKH-P2SH for addresses starting with 3..

If the first char matches and you don't see the address in your address tab in electrum, there seems to be something wrong.
Do you see the possibility that you have used the old (and wrong) address to send funds to instead of getting the address directly from ledger live?

A watch only is a wallet with only address(es) or the master public key imported.
It does not contain any private keys and therefore there is no way to spend from that wallet.

How did you set up that watch-only wallet? You must have imported an address / public key / master public key. Where did you get it from?

Without the missing secret information (the private key), you won't be able to spend the funds.
It is crucial for you to find the wallet you have used to "export" the address from.

What did you do with the wallet file?

Did you download it from the internet? Did you restore it through file recovery? Did you store it on a dying hard drive?

It seems odd that electrum crashes when you are trying to open the file.
If you have copies of the file (before opening it with electrum), definitely try to open it with older versions. But please always with a fresh copy, and never work on the "original" file.

The 3 most likely things which might have happened are:
1) You used a malicious application to generate the seed in the first place, such that it for example wasn't random at all.
2) You somehow entered the mnemonic code somewhere you shouldn't have entered it (malicious application, website, etc..).
3) Your device which has/had the wallet file stored is/was compromised.

Could you please answer..

• What software did you use to generate the seed?
• Where did you enter your mnemonic code?
• Do you remember anything from the day your coins got stolen? Any new software installed, anything?

Entering your mnemonic code via the PC is never good.
Even tho the search space is way smaller now, 6.2 x 10²³ is still way too much to simply bruteforce it.

If your device was compromised, the attacker would have all of your words of the mnemonic code, but not their order. This still makes it 24! possiblities (actually a little bit less than 6.2 x 10²³).
Definitely not bruteforceable.

No. Read my last reply.




You don't need to trust ledger to not block you out of your coins.
They don't have any access to your coins. That's what a hardware wallet is made for.




Yes.
Any kind of wallet where you hold the keys.

So, basically.. any hardware wallet, cold wallet storage, paper wallet, software wallet or mobile wallet.

First.. if you bought that file or were given it by someone: Be assured, there are no private keys associated to any funded address inside of it. In this case, you got scammed.

If this however is not the case and the wallet was created by you with core, then could you please list the exact steps you did to partially recover the private keys from that wallet file?
How many chars does your encrypted private key have?