If you sent to a custodial bitcoin wallet (like an exchange, gambling site or marketplace) that does not give you access to the private keys, you will most likely be unable to recover this LTC. If you sent it to a desktop/mobile or web wallet where you can access the private keys (or the seed/seed mnemonic) then there is a good chance you can recover the LTC.

I assume the BTC address started with a 3? Was this a SegWit wallet... or was it a MultiSig? Which wallet did you accidentally send the LTC to? Was it in a wallet you personally control and have access to the private keys (ie. desktop or webwallet) or does it belong to an exchange/website?

"Ledger Wallet Bitcoin" chrome app is still functioning... I just installed it... simply select "Bitcoin Cash" here:


Then to access the BCH from the fork... make sure you select "Main" (DO NOT select "Split"):



This will show any forked coins that the device still holds. That is to say, any BCH that is sitting on BTC derivation paths (m/44'/0'/0'...). If you use "Split" it uses BCH derivation path (m/44'/145'/0'...) which will only show non forked coins.


Nope. That won't work as you can't export your private keys from the Ledger by using Electrum. Electrum simply imports the appropriate XPub creating a "watch only" version of your wallet. So, all private key actions are still done within the Ledger itself... and part of the core of HW security is to never expose private keys

Yeah... it's a relatively well known issue with Mycelium where it can take a while for it to properly scan and display all your addresses/wallets if you do a reload/refresh.

It's one of the issues of relying on their infrastructure. It seems a little unreliable at times

If it was actually compressed into a ZIP or RAR file... and not simply renamed, then you probably can't simply search for a hex code as the output from the compression will be fundamentally different from the input.

You will probably need to decompress every archive, then search the decompressed files for the "wallet.dat hex code".

This thread: https://bitcointalk.org/index.php?topic=2857580.0 has some step-by-step stuff on how to go about looking for matching hex using WINHEX

In addition to simply rebroadcasting... the receiver could actually execute a CPFP (Child Pays For Parent) transaction that spends the UTXO from the unconfirmed transaction with a large fee to push the original transaction through.

As others have said, unless the sender attempts to also spend the coins in a second transaction, it isn't double spending, it's just a really bad scam attempt

I don't think you need a webhost... It's meant to be able to be downloaded and run locally... so you should be able to simply download the .zip associated with a release (you might need to click the little "assets" link to expand it to see them for older releases)... extract the .zip file and then open the index.html in your webbrowser. That should work.

MyCrypto (which was a fork from MEW due to some "differences of opinion" of the devs etc) seems to have .exe and AppImages available as well...

"Ledger Manager" was only useful for updating firmware and/or adding/removing "coin apps" from the device. It has no wallet functionality.

The "ETH wallet" chrome app , simply brings up a screen telling you to install Ledger Live... and indeed, that support download page says:
This happened way back in December of 2018... So, it's not a recent occurrence.

One other thing might be trying an "old" version of MEW or MyCrypto? You can check the GitHubs here: https://github.com/MyEtherWallet/MyEtherWallet/releases and here: https://github.com/MyCryptoHQ/MyCrypto/releases

If that is a bust, Ledger Support is your last best option

Yes... he means that someone could hack the Electrum website and put a fake copy there (hasn't happened as yet as far as I'm aware)... OR, more likely, you as a user, could download from a fake Electrum website (this is the most common reason people lose coins)

There is a step by step guide (with screenshots) on how to download and verify the Electrum installer for MacOS here: https://bitzuma.com/posts/how-to-verify-an-electrum-download-on-mac/

It is important to ALWAYS check that you're actually connected to https://electrum.org/ when trying to download the installer... AND then to verify the installer it legit by following the steps in that guide. Doing this will ensure that you have a 100% legit "official" version of Electrum and not a fake version.

Well, given that the CPFP is simply spending the UTXO from a previous (unconfirmed) transaction (with a high fee), it's technically, no more or less "linked" than any other "normal" BTC transaction.

However, if one were to analyse the transaction fees of a given block... and possibly the "Received Time" of a transaction (such as displayed by blockchain.com)... it might be possible to identify CPFP transactions.

Basically, you'd be looking for the following conditions:
- 2 transactions in the same block (Transaction A and Transaction B)
- Transaction B spends UTXO created by Transaction A
- Transaction A has a "low" fee relative to current fees being paid by other transactions in the block
- Transaction B has a "high" fee relative to current fees being paid by other transactions in the block

Less conclusive indicator would also be looking for Transaction A to have been received several "blocks" before Transaction B... as theoretically someone attempting to do this on purpose could broadcast Trans A and then immediately broadcast Trans B.

That Super8 is the definition of a "shitcoin"™... It is listed on only two relatively obscure exchanges that I could find.

One is SatoshiShift, which has zero buy orders (and a bunch of people trying to dump their worthless coin)
Second is Ex4ange, which has one buy order... @ 0.01 DOGE/SB for only 10 S8

Even if we could take that rate for all 200k... 200,000 * 0.01 = 2000 DOGE ~= ~$5USD

No one is going to loan you $1200-$1300 based on $5 of collateral

The short answer is: NO, it does not matter.

The long answer is:
The "source" value that you select in Electrum is just a display feature. It does not impact on how much BTC you will receive. THAT is defined by the exchange you use for purchasing your BTC in the first place.

Electrum is NOT an exchange. It is just a software wallet that can hold your BTC private keys (or LTC if you choose to download and use the unrelated Electrum-LTC software that is NOT developed nor endorsed by the Electrum developers).

The "source" value simply queries whatever service you select for their current BTC-$$$ exchange rate so it can display a $$$ value in Electrum. It is pretty much meaningless other than to give you a general idea of the value of your BTC holdings. All the value in your Electrum wallet is actually stored in BTC and is only really worth whatever you can trade BTC for on whatever "exchange" you choose to use to convert it (ie. web exchange, localbitcoins, P2P trading etc).

Changing that "source" will not affect your ability to receive BTC from ANY source you choose (so you can select Source X and receive coins from Source Y etc).

To expand on this a little... you will need to use "File -> Open" from within Electron Cash... or click the "Choose..." button on the wizard when you first open it:


You will then need to browse to your Electrum wallet directory (refer: https://electrum.readthedocs.io/en/latest/faq.html#where-is-my-wallet-file-located) and select the wallet file you wish to open.

There are also 3rd party projects like this one: https://github.com/FarCanary/ElectrumSeedTester

It is based on Ian Coleman's BIP39 Mnemonic Code Converter, but works with Electrum seed mnemonicss (which are NOT BIP39 compatible). I've tested this one and it works.

I had previously even created my own here: https://github.com/HardCorePawn/electrumBIP39 ... but mine was wayyyyyy less polished, and is more of a "hack" (I basically just edited Ian's code to ignore the checksum errors and changed the "passphrase prefix" from 'mnemonic' to 'electrum' )

The odds of ALL of this information disappearing at the same time is essentially zero... you will be able to recover your funds should Electrum stop working tomorrow

How do people end up in this situation? Without that backup seed mnemonic, users are sitting on a ticking time bomb... one small accident and all their funds are gone.

For ETH recovery, try following the instructions here for connecting to MEW: https://support.ledger.com/hc/en-us/articles/115005200009-Set-up-and-use-MyEtherWallet

If that doesn't work, then I would contact Ledger Support and see if they are able to assist with a way to access ETH on an old firmware without updating. They recently added a dedicated Support Twitter account:  https://twitter.com/Ledger_Support

Or you can try researching other options (including logging a ticket via their online form) here: https://support.ledger.com/hc/en-us

Can't help with the Atomic wallet issue, but just wanted to point out that if you're concerned with privacy (which I think you might be given the redacting in your screenshot)... it would appear that you left your (real?) name unredacted in the email correspondence

For all intents and purposes... BitPay == CoPay


If you really wanted Copay, you can always try compiling it yourself: https://github.com/bitpay/copay

---

I'm kinda hoping you got your xprv's and xpub's a bit mixed up there... your 2-of-3 setup would be relatively useless with every device having 2x xprv's

To be an effective 2-of-3 multisig, it should be something like:
Laptop: xprv1,xpub2,xpub3
Phone: xpub1,xprv2,xpub3
USB: xpub1,xpub2,xprv3 (unless this was supposed to be your emergency recovery unit, in which case it might want 2 xprvs)

I don't quite understand how this "fast-forwardable seed" system is any different to simply deleting the old wallet and creating a new wallet?

You're just replacing one seed with another (granted in the fast-forwardable system it is a hash of the original seed)... but in both instances, there is no way to recover the old seed from the new seed.

Are you imaging a system where you can go "old seed -> new seed" in a repeatable way?

Sounds like one of your machines is infected with the clipboard jacker... and when using RDP, the "shared clipboard" feature means that the clipboard jacker is able to detect and change the bitcoin address.

This particular malware seems more advanced than most, in that it appears to have a database of "similar" addresses that it uses to try and avoid detection.

In any case, you should go and run some full scans on all your machines (as a bare minimum)... either that, or backup your important data and then re-format and re-install all your OSes

That's why I said "in this instance"... OP has 1 BTC input that they don't want to break. So zero fee would be required to preserve the 1 BTC... which wouldn't get relayed.

If you don't mind "sacrificing" a small amount of your original input (or you have a small amount extra), then "yes", you can totally send with min fee and then CPFP to get it pushed through (assuming that min relay isn't enough to get it confirmed)

The problem would be that no node would accept your original transaction with zero fee (zero fee required in this instance to avoid "breaking" the 1 BTC input).

The only options the OP has are:
1. Include a 2nd input in the transaction (thus connecting the 2 inputs)
2. Sending a small amount to the original wallet to cover the fee (essentially doubles the total fees as it means creating a 2nd transaction)

Option #1 is arguably bad for privacy
Option #2 is more expensive and arguably just as bad for privacy as you can track the coins being sent to the address anyway... but this way you can't for certain claim they were both "owned" by the same person.

If privacy is the overriding concern, then, as stated earlier, you'd probably be better off dumping all your coins into a mixer/coinjoin and then creating fresh 1 BTC outputs from there.