The words are simply encoding 11 bits of data... so out of your groups of 11 bit sequences, if you have two that are identical, you'll get the same "word" shown in your mnemonic.

It's not that uncommon... I helped a fellow out a while back who only had 23 words written down out of a 24 word seed mnemonic. Turned out, after my script managed to bruteforce the correct seed mnemonic, that the missing word was identical to the one next to it, which explains why he missed it out when writting it down!

---

The thing to be more concerned about is that Coinomi is broken! Yet another reason to avoid it at all costs   Definitely contact their support and let them know...

Yes... there is... you need to disable "full file encryption".

Goto "Wallet -> Password"... enter your password and make sure that the "Encrypt Wallet File" option is NOT checked:



Electrum has three levels of "encryption":

1. NO encryption... if you have NO password, then the whole wallet file, including "secrets" like private keys and seeds are stored in plaintext and readable in a text editor.
2. Password ONLY... if you have a password, but disable wallet file encryption, then the wallet is still "plaintext", but secrets like private keys and seeds are stored encrypted. Password is NOT required to just open the wallet file.
3. Full wallet file encryption... If you have a password and select "encrypt wallet file", then then entire wallet file is stored encrypted on disk and the password is required to open the wallet.

By selecting Option #2, you will be able to open your wallet in Electrum and see transactions/balances etc... but will NOT be able to send transactions or sign messages (ie. anything that requires access to a private key) without the password... just like Bitcoin Core

If it's "wallet.dat" and you found it with "gigs of data" in the AppData/Roaming/Bitcoin folder... then it is most likely the wallet file from "Bitcoin Core".

Firstly, make a couple of copies of "wallet.dat"... this is your "golden ticket", so you don't want to lose it.

But the video looks like it follows the steps that I would personally do... ie. Download, then install the latest version of Bitcoin Core... Run it once... once it starts "syncing", shut it down. Then replace the new wallet.dat in the C:\Users\YOURUSERNAME\AppData\Roaming\Bitcoin directory that it will have created with one of the copies of your old wallet.dat and restart it again.

It should "update" the wallet file to be compatible with the new version of Bitcoin Core, and you'll then be able to dump out the private keys etc. if you don't want to download and process 350+ gigs of blockchain data while syncing Bitcoin Core

NOTE: You will probably NOT be able to see your transactions/bitcoin until Bitcoin Core has synced up to the date that you originally received the coins into your wallet. So, don't be surprised if there is balance of 0.00000000 BTC when you first open it!

---

Once you have the wallet loaded into Bitcoin Core, then your options are:

1. Let Bitcoin Core sync... could take hours/days... but is probably the "safest" way to recover your coins as you don't have to expose private keys etc.

or

2. Export your private keys from Bitcoin Core (using dumpwallet which dumps ALL the private keys from the wallet file, or dumpprivkey which outputs specific private keys for nominated addresses) and then import those private keys into a "light" or SPV wallet of your choice... ie. Electrum

---

It's because you're a "newbie" account... you can't embed images until your account ranks up or you buy a copper membership


If you need any help, just ask.

Are you thinking of CPFP (Child-Pays-For-Parent)? If so, that works the other way... when you're trying to get one of the descendants confirmed quickly, you have to take into account all of the ascendants.

ie. if you have the following chain of transactions: TransA -> TransB -> TransC -> TransD -> TransE

And you bumpfee on TransA... then B, C, D and E will become invalid as the hash of TransA will change, making B invalid.

If you're wanting to get TransE confirmed quickly, then you would need to take A, B, C & D into account as well, to make sure that the fees are big enough for miners to want to get all 5 transactions included in a block.

Which OS? Ubuntu run natively... or Windows with Ubuntu in a VM?

If you're running Ubuntu natively from an external disk, it'll likely run slower from an external disk than from an internal one depending on interfaces being using USB vs USB2 vs USB3 etc and also due to the fact that your 2TB drive is more than likely an HDD and not an SDD.

If it's in a VM, it'll always run slower than it would natively... having said that, if you're just wanting to use it to compile Bitcoin (as per the thread), then running Ubuntu in a VM is "OK"... I run Ubuntu with Oracle Virtual Box on an i5-3570k with only 8Gig of RAM and Windows 10... it's not the fastest config, and multitasking is painful, but it's perfectly "adequate" for single "one off" tasks like compiling Bitcoin.

I also use Ubuntu with WSL on this machine depending on what I'm trying to test.


Depending on your specs, your mileage may vary

Not as far as I'm aware. The Windows Subsystem for Linux (aka WSL) which allows you to install various flavours of Unix into Windows is part of Windows 10... it's not available for Windows 7. Your only option on Windows 7 would be to install Ubuntu using Virtual Machine software like Oracle Virtual Box or VMWare or similar.

Let me guess... Your Antivirus/Antimalware was blocking the installer and/or the application from running?

Either that, or simply running as Administrator would probably have solved the issue.

True. I had forgotten about that part of it... it's been a busy couple of weeks with lots of very early starts

So, I'm wondering if it just a Legacy/SegWit thing then?

It simply reads and copies the data... it doesn't move any data from the original drive. So, using a clone should yield the same results as working from the original devices (assuming the clone is in fact an exact 1:1 copy)


Any wallet.dat file created by PyWallet should theoretically be a "valid" wallet file... it might be empty and contain no keys, but the file itself should still valid. If it said "no keys" found, then it probably won't have any keys... you can verify by using the PyWallet --dumpwallet command.

No, it is not possible to determine a derivation path from an address.

An ETH address is simply the last 40 chars from a Keccak-256 hash of the ETH private key, with "0x" prepended... There is nothing encoded in this address which would give any indication of the derivation path used to get it... or even if a derivation path was actually used, as it is entirely possible that the private key was generated by coinflips/dice rolls or some other RNG process.

I have a suspicion that o_e_l_e_o is correct... It's starting to look a lot like the classic "have (valid) seed for a different wallet" scenario

I've seen a few instances on these forums of users that have been experimenting/testing wallet applications and have setup multiple wallets (accidentally or deliberately). Then they end up with a situation where they think they have the correct seed mnemonic written down, but are in fact using a wallet derived from a completely different seed.

Inevitably, "Murphy's Law" strikes and they lose access to the wallet (computer failure, lost password etc)... then they go to restore... only to discover the seed they have derives a completely different wallet and they're like "W.T.F??!?"


What I find a bit confusing tho, is that apparently you found some transactions/coins... but not others??!?

As I mentioned earlier, it's possible that the wallet was doing strange stuff and had both Legacy/SegWit addresses... and so was actually using multiple derivation paths for the one wallet... or it was generating SegWit address off "Legacy" derivation paths or vice versa...

So, the address that you couldn't find... it it SegWit or Legacy?

They go to your default "Downloads" folder:



On Windows, this appears to be: C:\Users\YOURUSERNAME\Downloads

and they should be named something like: lily_wallet_config-MMDDYY-HHmmss.txt:

Just... wow!

I'm guessing the fact that he retweeted the Ledger "Phising" warning, and then publicly apologised to Ledger is the biggest indicator of what happened:



100% he either entered his 24 word recovery phrase into either a fake version of Ledger Live or a phishing website etc when he reset his seed a week ago.

Sucks his lost so much, but I'd have way more respect for him if he explained what actually happened instead of these somewhat "vague" tweets which are the twitter equivalent of "nevermind, I fixed it" posts on forums

I have vague recollections that there were some issues with Ledger Nano S and ETH back in the day... in that the "Ledger Ethereum Chrome Wallet" was using a "non-standard" or, more correctly, "different" derivation path than other wallets... They didn't start using the actual BIP44 standard until Ledger Live I believe.

Indeed, we can see things like this: https://github.com/MyCryptoHQ/MyCrypto/issues/2070

Try looking for your address at: mycrypto.com

The 2 options to look for are, "Ledger (ETH) (m/44'/60'/0')":



and "Default (ETH) (m/44'/60'/0'/0)":


MyCrypto will give you multiple addresses (and show the balance)... it's possible that years ago, you didn't select the (default) "0 index" address... but selected one of the higher index addresses...

If that doesn't work, you might need to select the Custom option and start experimenting with other combinations.

---

If you're more comfortable with MEW, you can actually click the "Ethereum" title:



And then select "Custom Paths" at the bottom:



Then click on the dropdown box again and select "Add customs paths - custom":



This will allow you to select any custom derivation path that you like:

Opening the wallet files in an old version of the software shouldn't do anything "bad"™... if you're concerned, simply make sure you have copies of the original files and work on the copies.

Once you have the wallet open, you'll be able to export your keys from "Tools -> Export Private Keys":



And then set up the export as follows:


NOTE: "Do not password protect export file" is necessary, otherwise the output file will be encrypted and you won't be able to read the private keys!

Then you'll be able to open the export file with a text editor and see your private keys... you can then import them into another wallet like Electrum and you'll be away laughing.

---

I also wrote some Python scripts (a while back, when MultiBit was shutdown) that can read the .wallet and "key backup" files directly and extract the private keys: https://github.com/HardCorePawn/multibit_recovery


If you need any assistance, just ask. You can PM me if you like.

You'd probably need to edit the backend code so that when a user clicks the button these hidden fields of yours are actually used/processed by the server code when creating the "invoice".

Also, this probably isn't the best place to be asking for help for BTCPayServer... you'd be better off using the BTCPayServer communities: https://btcpayserver.org/#communityCTA

I'd recommend trying the "MatterMost" chat or "Telegram" group.

Well... it "only" took 5 days for the firmware update to show up in Ledger Live...



The update itself was easy and painless:



And it prompted to re-install the apps I had prior to the update:



And, having updated all the apps a day or 3 ago, I can definitely say that it installed them a lot faster this time! So, that's a nice little bonus I guess... but as we can see, we have indeed lost 4kb of storage... now down to 156kb from 160kb prior to update.

Don't worry, your coins are not "gone"... you'll be able to get them back!


If Electrum won't accept the key, there is likely some minor formatting issue with the key, like extra text or spaces etc.

Assuming the Armory address you sent BTC to starts with a "1", then the private key you want to be pasting to Electrum will start with a "5"... If the address you sent coins to starts with a "3", let me know, because the instructions will be slightly different.


 if you followed my guide, then you should have made sure that the "Omit spaces in key data" box was checked, it's VERY important... extra spaces will prevent you being able to paste into Electrum!



If you got something that looks like this:
That will not work with Electrum... so make sure that the "Omit Spaces in key data" is checked!


Yo need to have output in Armory that looks like:

Then you simply need to copy just the PrivBase58 value... so you want to copy this part only: 5Kb8kLf9zgWQnogidDA76MzPL6TsZZY36hWXMssSzNydYXYB9KF


Then you can paste that into Electrum, using "File -> New/Restore -> Import Bitcoin Addresses or Private Keys":



Paste in the private key, and click "Next":



You'll be asked if you want to add a wallet password, you can enter one or leave it blank, then click "Next", and the wallet will be created with your address and you should be able to see your transaction history and balance etc:

In that case, follow my guide here to find the private key for the address that you sent your bitcoins to. Simply look through the list of address until you find the one you sent coins to (should be right at the top), then import or sweep that private key (will be labelled as "Plain Base58") using a "light" (aka SPV) wallet like Electrum.

NOTE:
- You should only download Electrum from: https://electrum.org/
- And you should really take the time to verify it as per the instructions here: https://bitcoinelectrum.com/how-to-verify-your-electrum-download/

As someone else mentioned... that looks like a "TestNet" address... if you start Electrum using the "Electrum TestNet" shortcut on Windows (or using the --testnet commandline argument) it'll recognise that address just fine: