I wouldn't recommend Exodus, tbh. Neither Jaxx, Coinomi or any other closed source and/or poorly coded software.

It is your choice, but i wouldn't store more than you are willing to lose on Exodus.

Das lässt sich nur bestimmen, falls eins der folgenden bekannt ist:

• Mnemonic Code
• Master Private Key
• Master Public Key

Dass die ersten beiden geleakt werden ist eher unwahrscheinlich (Bzw. falls doch, dann hast du größere Probleme  ).
Das einzige was realistisch eine Gefahr wäre, ist der Master Public Key. Der ist auf deinem Rechner gespeichert (Unverschlüsselt bei Ledger Live oder in deinem Electrum Wallet).

Wenn jemand an die Daten ran kommt, dann ja. Ansonsten ("von außen betrachtet"), nein nicht möglich.

Hoffe das beantwortet die Frage einigermaßen genau 

Ich kann dir zwar nicht sagen wo du GPUs finden wirst.. aber wenn du weißt wo, dann kann ich dir bei Online Vorbestellungen sagen wie: Mit Bots.

Einige GPU Modelle scheinen momentan ja sehr gefragt zu sein. Sobald diese Online zur Verfügung stehen, würde ich mal davon ausgehen, dass sie innerhalb von Sekunden reserviert/ausverkauft sein werden.
Ein Bot der die GPUs auf den Webseiten direkt nach Erscheinen kauft, wäre eine Option.


Aber generell.. wenn du BTC minen willst, dann wird das mit GPUs nichts mehr. Das hätte vielleicht vor 8 Jahren funktioniert.
Mittlerweile brauchst du für BTC Mining ASICs.

I'm glad you got it sorted out.

But.. Bither has to store the data somewhere. And this "somewhere" is the address.db file, right?
So replacing an useless (empty) address.db file with yours should be sufficient? Even without an "import" function?

Why can't you just download Bither and use that to open your wallet file by providing the correct password?
It seems you have all the necessary information.

Trying to find a way without using Bither, given that you seem to have everything you need, seems to be not worth the effort. What am i missing?

Basically any information which identifies you. Nor necessarily directly you, but anything which describes a subset of possible entities.

An example would be the script type you use. Bech32 transactions make up a total of less than 10% (estimated; a year ago it was roughly below 7%).
Together with for example the usual quantity you transact with and/or specific timeframes you usually transact, this further reduces the anonymity set.

This could be used with non-bitcoin related pieces of information to make your profile more specific.
Just as you are being tracked across the internet. Not through your IP address, but through cookies and other specific configurations such as your screen size, color depth of your screen, language, specific browser and/or OS version, etc..
I remember reading (don't know where currently) that such information (a pc/browser configuration) can be used to track one person out of a million. With ~5 million people for example visiting a specific website or using a specific service, your anonymity set could be shrinked to 5.


Obviously this shouldn't be generalized, and i am not saying that you are being tracked or are surfing/transacting with an anonymity set of X, but it's not as easy as changing your IP address to not get tracked / identified.
This applies to an electrum server as well as browsing the web.
Using Tor also doesn't guarantee you perfect privacy. People doing illegal stuff there get caught relatively often. Sometimes it is because of the link to their real identity (e.g. cash flow) but sometimes it's because of their behavior and/or "wrong" configuration.
The whole privacy- and anonymity aspect is not as easy as one might think.

Leider kann man da nicht mehr machen als zu warten.




Kannst du nicht.
Sicherheitstechnisch betrachtet macht es Sinn, dass (so gut wie) niemand auf die Keys zugreifen kann.
Der einzige Weg erfolgt über den Support. Die Chancen stehen aber nicht sehr gut.




Ja, coinbase hat ja die Keys. Ist ja deren Adresse.




Da kann dir wirklich niemand außer Coinbase helfen.




Die LTC gehören jetzt Coinbase.
Die TX-details sind öffentlich zugänglich. Jeder kann sich die Daten anschauen (Blockchain).

Damit kann nichts geklaut werden.




Das bedeutet, dass die Coins noch auf dieser Adresse liegen und noch nicht weiter geschickt worden sind.
Ist eigentlich zu erwarten, da Coinbase nicht automatisiert alle BTC Adressen nach LTC durchsucht. Würde ja auch keinen Sinn machen.




Die Coins gehören nicht dir.
Coinbase ist Besitz deiner Coins. Was du mit deinem Wallet machst ist komplett unabhängig von Coinbase.

Die Aussage dient eigentlich insbesondere Neulingen. Aber wenn ich das dazu schreiben würde, hält sich keiner dran weil ja jeder erfahrener ist als der Durchschnitt. 

Aber im Prinzip geht es auch nicht um den Fall, wo alles richtig gemacht wird und alles klappt.
Sondern eben falls z.B. eine falsche Chain ausgesucht wurde (Hilft theoretisch auch nur beim Abheben). Oder man die Coins irgendwo hinschickt, wo die dann auch innerhalb von X Stunden/Tagen ankommen müssen (z.B. die meisten Payment Provider).
Bei Service/Exchange <-> Service/Exchange gibt es keine Möglichkeit die Transaktion zu beschleunigen (RBF / CPFP). Alles was man da machen kann, ist warten.

Für Neulinge -> Würde immer empfehlen zuerst auf das eigene Wallet zu senden.
Die größten Kosten sind meistens ja eh die Abhebegebühren, und nicht die Transaktionsgebühren an sich.

If you just want to recover your BTC and don't care about getting Core up and running, you can skip the blockchain synchronization.

You can use the dumpwallet command to export all private keys. Then use a SPV client (which does not need to download the whole blockchain) to import them (e.g. electrum).

However, if you want to have Core up and running, you won't benefit from exporting/importing them.
In this case, waiting is the better option.

If the outputs already have been spent, then there is no way for you to get this old transaction confirmed.
This also means, that you already have spent those UTXO, which should be visible in Core.

Check bitcoin core whether there is still an outgoing transaction waiting to get confirmed.

What?

In Europe, online banking does not work like that.
No one has to "approve" the recipient of a transaction.

A SEPA transfer works by entering the recipient and the amount. That's it.
Just like a BTC transaction with the difference that you not only enter a recipient-identifier, but also the name of the recipient and that your bank is in control of your money instead of only you.

It doesn't make much sense to me to whitelist recipients.

You don't need to.
Updating the application does not erase the user data.




Those reviews are most likely from people who failed at backing up their mnemonic code properly.




In this case, you might want to make a backup of your current wallet.
I guess you are aware of the risks storing crypto on a mobile wallet as opposed to a desktop- or hardware wallet?




This might also be the case now.
If you aren't in a hurry, just wait a day or two. If you are in a hurry, use your mnemonic code to restore your wallet on your desktop system (e.g. via electrum).

What exactly do you want to achieve? Do you just 1) want to access your BTC to send them somewhere else or do you want to 2) get armory up and running properly ?

For 1), you can just export the private key(s) of the address(es) which contain your BTC and import them into another SPV wallet (e.g. electrum):



Regarding 2), please upload the complete log file to pastebin (or any other similar service) and provide us the URL.

Leider war die Transaktion von einer Börse zu einer anderen zu senden, ein Fehler. So etwas sollte nie gemacht werden.
Die Problematik die du gerade hast, ist ein Beispiel dafür. In Zukunft: Ein eigenes "Zwischen-"Wallet verwenden.

So.. nun zur technischen Seite deines Problems:
Der Besitzer des Private Keys der BTC-Adresse (Also: Coinbase) kann deine LTC wiederherstellen.
Heißt, du musst Coinbase kontaktieren.
Aber: Das bedeutet, dass jemand (ein Mitarbeiter, Software, Prozess, etc..) auf den Private Key zugreifen muss. Ein "einfacher" Mitarbeiter wird da nicht die Befugnisse haben. Vermutlich hat so gut wie niemand die Berechtigung dazu.
In der Praxis wird es wohl darauf hinauslaufen, dass du das als Lehrgeld akzeptieren musst, da dir Coinbase nicht helfen wird.

Yes, that is correct.



Electrum uses its own infrastructure composed of clients (e.g. your wallet) and server (electrum server) who are directly connected to full nodes.
It is different that the "classical" SPV approach implemented in the BitcoinJ library (which is used by most mobile wallets).

Is electrum connected to the network (green circle in the bottom right) ?

A wrong derivation path might be the issue.
Can you confirm that you have recovered a legacy wallet (addresses starting with 1..) and not nested or native segwit (address starting with 3.. or bc1..) ?

It means that the wallet software is using Simple Payment Verification and therefore does not require to download the whole blockchain to verify that transactions are included in a block.
You can read up on that in the bitcoin whitepaper or on one of those dozens websites explaining SPV.




Because a SPV wallet still needs to download the block headers (= synchronization).
To accomplish that, it connects to other peers.




Maybe.
If you tell us what you believe to know, we can point you into the right direction.

Besides the fact that this obviously comes from your outdated version.. such an error can never be because of the "receiving wallet".
There is no "receiving wallet". Such a concept does not exist when sending a transaction.

You were given an address. You put that address in the "to" field. Your wallet creates new UTXO's which can be spend by fulfilling the conditions of the unlocking script (which is "represented as the address"). That's it.
At no point is there any "receiving wallet" when sending a transaction. No wallet receives anything. The "recipient" checks the blockchain for transactions which affects his address.

Ja. Auswahl erfolgt nach Ledger Live's Algorithmus (Kp wie genau der welche UTXOs präferiert).




Ja, korrekt.
Die verschiedenen Accounts werden durch unterschiedliche Derivation Paths realisiert:
m / purpose' / coin_type' / account' / change / address_index

UTXOs aus verschiedenen "Accounts" werden nie vermischt.
Brauchst also keinen zweiten Ledger, die Account-Hierarchie ist ausreichend.

The MAC address is completely irrelevant since it can be spoofed. No one cares about the MAC address of your wifi/ethernet card.
Further, linking those addresses together can be too information already.

This means all of your purchases can be linked to one entity. Each of those purchases tells something about you. While a single one wouldn't even be close to deanonymize you, all of them might be.
Because you are that single person in the intersection of all those purchases.
People seem to be obsessed with IP addresses. That's not the only thing which makes you vulnerable. By far not.




Yes.
Wasabi is probably the best one, followed by Samourai.