It said it was an invalid seed and to my knowledge I did not go in and enable any extra options.
It would seem that you have copied one (or more) of the words down incorrectly.  I would advise to check each of your 24 words against this list: https://github.com/bitcoin/bips/blob/master/bip-0039/english.txtIf you find a word that isn't on that list, have a look for very similar words... If that doesn't help, you'll need to use seedrecovery.py. - I used seedrecover.py and my xpub key from Ledger Live to check if there was 1 big typo (one completely different word) and no luck
NOTE: the default version of seedrecovery.py will ONLY work with older legacy ("1" addresses)... and, unfortunately, Ledger Live defaults to using "3-type" (p2wpkh-p2sh) addresses these days. However, the good news is that there is a version of seedrecovery.py that works with SegWit addresses. The pull request hasn't been accepted into the main btcrecover repo as yet... but you can find the modified version that supports the p2wpkh-p2sh (3-type) addresses here: https://github.com/madacol/btcrecoverAlso, I'd say that the "xpub" you get from Ledger Live probably isn't the best way to search either... I'd suggest searching for a known address from Ledger Live (perhaps look through your transaction history and pick the first "3" address from your first transaction). The reason why is that you're using p2wpkh-p2sh addresses, which should be generated from a "ypub"... but Ledger Live still exports it as an "xpub"... and i don't think seedrecovery.py will generate the test addresses correctly. |
|
|
|
I would love this feature too. I think I have asked similar questions here or some other places without getting a satisfactory response.
I think firefox was fully open-sourced in around '95 so it should be easy if someone has the time on their hands and fancies doing this?
Did you all not read the post above by tomahawk9? Maybe the firefox (it's also on Chrome) add-on called "Advanced Profanity Filter" might work? It has option where you can pretty much filter or substitute any word you want on websites you visit...Haven't tried it, though, so watch out for giving it too much permission on your browser.
Here is the link: https://addons.mozilla.org/en-US/firefox/addon/advanced_profanity_filter/I've tested this on Firefox on Android and it does exactly what you want. You can configure specific words that you want either censored or substituted... you can whitelist certain domains etc... it seems to work quite well. I set "bitcoin" to be substituted with "Cryptographic Money"     |
|
|
|
|
comma's? it should just be spaces...
|
|
|
|
I'm completely baffled by the events that occurred a few days ago. For one, I tried to send a transaction and I kept clicking confirm on the ledger then before I knew it the device was reset (I did not type the PIN wrong 3 times). I simply clicked confirm transaction but it still didn't go through.
Never heard of a device resetting itself unless you enter the wrong PIN... very odd. I figured I was fine as I had the 24 word recovery phrase but I tried it out and it did not work whatsoever. I have all 24 words.
How did it "not work"? Did the wallet say it was an invalid seed? or did it just generate an empty wallet? Also, did you utilise the "2nd PIN" option and/or extra passphrase option that Ledger provides? Refer: https://support.ledger.com/hc/en-us/articles/115005214529-Advanced-passphrase-security |
|
|
|
... I am almost certain that I have the correct seed and the problem stems from something else. I suspect it to be either the conversion from string to hex or some kind of change concerning the Electrum seed system.
Honestly, that is the most likely issue... Addtionally, there is no real way to "error check" your string to hex conversion. Does a given hex seed generate the same addresses in version 2.7.9/3.0.0 and the most recent version 3.3.6? If so, that would likely rule out any behind the scenes code changes and indicate that the seed itself is wrong. Having said that, it is possible that it is simply a derivation path error... if the default "legacy" one (m/44'/0'/0') is not working, then common ones to try would be m/0 and m/0' but I'm fairly sure the derivation path for BIP39 seeds has not changed. Maybe try asking your question on the Electrum "issues" register on GitHub... the devs are a lot more active there and might have better insight into whether derivation paths or BIP39 seed handling has changed. |
|
|
|
Failing that, you can always just specify the appropriate directories in the armoryqt.conf and armorydb.conf files. Refer to the Armory "Pathing" docs for more info: https://btcarmory.com/docs/pathing |
|
|
|
In the mean time I also found an alternative wordlist, with the mnemonics words that are in by bitcoin cash mnemonics seed.
Different wordlists?? Not to my knowledge... where did you read about this?  Looking at the wordlist in the Electrum source code and the wordlist in the Electron Cash source code... They're identical. And so they should be... because, AFAIK, they both use the BIP39 wordlist.With BCH however, It says :
- peach not in wordlist, did you mean beach?
No, I did not say beach, I said peach :-)
I suppose I need another wordlist.
For the record... peach isn't in the BIP39 wordlist... there is a "peace" or "beach"  |
|
|
|
If you check the readme it says you can gmake it search for 12 words instead of 24.
Yes, you can... and I like said... The number of valid seeds generated falls in the 1400-1600 range. I tested it with an actual block.io 12 word seed... and tried 4 tests (deleting the first word, last word and a couple of "random" words from the middle). First word: 1586 valid seeds generated Last word: 1532 valid seeds generated Random Word test1: 1456 valid seeds generated Random Word test2: 1580 valid seeds generated |
|
|
|
|
The "data" (in this case, the details of the transaction) is secured once the transaction has been "signed". After it has been signed, any modification to the transaction details will cause signature validation to fail and the transaction will be rejected by any node you attempt to pass it to. Likewise, if the data is NOT signed, nodes will reject it as "unsigned". You can think of the "signature" as like a tamper proof seal wrapped about the transaction details. Nodes are configured to reject transactions if the seal is "damaged" or "missing".
So, what happens is that you first create an "unsigned" transaction in the software that you are using in conjunction with your ledger (ie. Ledger Live or Electrum or MEW etc)... Note that this "unsigned" transaction is built using the public keys that the Ledger device will export to the software so it can determine which UTXOs you are able to spend (ie. which public keys/addresses are "yours"). The private keys are safely stored on the Ledger device in the secure element and are never exposed.
Once you're ready to send, the "unsigned" transaction is first passed to the Ledger device for signing. This is why it is very important to double check the info that the Ledger device displays, with the info being displayed in your wallet software... if the info matches and (more importantly) is what you were actually trying to achieve (ie. send 2 bitcoins to public key X), you "confirm it" by pressing the "yes" button on the device and then the device will go ahead and sign the transaction using the appropriate private keys inside the secure element, and then it will pass the "signed" transaction back to your wallet software.
At this point, the transaction can not be modified in any way... so, you're free to broadcast this "signed" transaction to the network, safe in the knowledge that no-one can modify it because of the "tamper proof seal"
|
|
|
|
It's going to be very difficult to brute force that... block.io generates MultiSig addresses using a combination of the 12 word mnemonic and the "secret PIN". So, attempting to use something like the "seedrecovery" script in btcrecover will not work, as it will not be able to simply convert the mnemonic "guess" to a seed and then generate an address from that seed and compare to a known address... So, you would need to manually create all the valid seeds possible using your "11 words" as the base... then manually "test" the values in the "Settings" page to try and change the secret PIN. I had a quick look at the brute.bip39 tool, and while it will generate valid BIP39 seeds... it doesn't generate only 180 valid combinations. Because you only have a 12 word mnemonic (instead of 24 words) it ends up generating somewhere in the 1400-1600 range of valid seeds!  ... so that is going to take a while to work through, but I would say that it is certainly doable in a few days/weeks |
|
|
|
And for the BTC, luckely I already have all the information, but I tried anyway.
And It gives an adress that I recognise as one of mine, (I wrote it down one day) on top.
But that's one without any bitcoin on it.
The one adress that I am looking for, is not in the list, even if I generate 200 adresses.
I tried generating more adresses, but somehow the tiny Raspbeerry is too little for the browser, and the pages times out every time.
It'll most likely be because you're looking for a change address... and the ElectrumSeedTester generates receive addresses by default... You need to change the BIP32 Derivation Path... If your seed is generating Legacy addresses (starts with 1), by default the derivation path will be m/0... change it to m/1If your seed is generating Bech32 addresses (starts with bc1), by default the derivation path will be m/0'/0... change it to m/0'/1That should show you the address you're looking for |
|
|
|
You guys may want to read the OPs other thread: I tried to install the newest electrum on a rasberry pi with OS Raspbian Stretch
OPs options for OSes is pretty limited... because they're trying to use a Raspberry Pi (ARM architecture). Likely, the port of Python and/or libraries to ARM is the issue here. But your other info is very usefull.
Your link did not produce the right answer right away, but that's probably because I am confused by all the information like BIP39 and other numbers and things.
But a quick search on the internet gives me plenty of new starting points, so I guess I will sort this out eventually.
All you should need to do is enter the 12 word seed and the converter should detect SegWit or Legacy and then display the correct addresses/private keys at the bottom... If it doesn't... errrr Is your Electrum wallet 2FA or something? |
|
|
|
Version 1.8.1. of Ledger Live is meant to fix the update from firmware 1.3.1... Fixes firmware update for Nano S 1.3.1.
and there is a 1.9.1 version coming that will apparently assist with these "Bootloader" issues: New Features
Accounts now have a dedicated section
Manager detects Bootloader mode and recovers it
Repair tool is now shown in the manager when connection issues occur
...
Bug fixes
Fixes Ledger Nano S 1.3.1 firmware update support
And then you have some users claiming that downgrading to 1.7.0 is what enabled them to recover... You can get 1.7.0 here: https://github.com/LedgerHQ/ledger-live-desktop/releases/tag/v1.7.0At the end of the day, the device is recoverable... I've had it stuck in a "Bootloader/MCU needs to be updated" loop before and as long as you follow the instructions you'll be able to get it repaired. Ok I try it out, just to confirm its windows 10 safe mode not windows 7 safe mode and the repair mode in app is the only way to fix this and the repair doesn't ask for 24 word seed?
Just try Windows 7 safe mode if that's what you have... If you have Windows 10, Ledger Live will work fine without doing anything extra. I can't remember if repair wiped the device and needed the 24 word seed mnemonic to be re-entered. I just tried "repairing" mine now and it didn't ask after flashing the bootloader... but the device didn't actually need repairing, so I'm not sure if it actually did anything. My advice would be to make sure you have your 24 words handy just in case. |
|
|
|
Is there a trimed down version of electrum, that I can use to only import the seeds, and get my keys out in return?
Not a trimmed down version of Electrum, but a user here modified the Ian Coleman BIP39 Mnemonic Code Converter so that it will work with Electrum seeds (instead of BIP39 seeds): https://github.com/FarCanary/ElectrumSeedTesterShould theoretically work with the Electrum-LTC and ElectronCash seeds... as I believe they didn't change anything in the seed generation. Give it a try and report back if it works! Also, Electrum works on the commandline on Linux (and Mac OSX I believe)... Not sure that not using the GUI will solve your issue however... seems more like a Python versioning issue. |
|
|
|
To the best of my knowledge... there isn't any way within Ledger Live itself to see a list of your receiving/change addresses. You would need to export the "xpub" and generate the list of addresses in another app (like Electrum) or by using . |
|
|
|
|
Nope, that's still true. If you have a pruned node, Armory will be unable to find any transactions in blocks that have been "pruned".
You need a full node that has the full blockchain for Armory to run correctly.
|
|
|
|
I installed an earlier release available - 0.96.1, and I was able to open it.
I restored my wallet from the root key.
BUT - I dont see any option to make it show/export the private key.
only thing I can do is "back up" the wallet, which is useless.
How can I see the private key to my wallet?
anyone?
"Backup wallet" is exactly the option you need... it's just that the private key export is a little bit hidden. Try this old post of mine: https://bitcointalk.org/index.php?topic=4746784.msg43255691#msg43255691If you can manage to get it running... you can export your keys and then import them into another wallet like Electrum... If you just want to get it open, and 0.96.4 still won't run for you, you can try the older version and do the key export without worrying about syncing with Core etc. NOTE: exporting keys should not be taken lightly. There is a chance your keys may get compromised if your computer is not secured and you could suffer coin loss as a result.To export your keys, you can use the following menu options in Armory: - Wallet Properties - Backup This Wallet  - Select "Export Keys List" (top left box) - Click "Export Keys List" (bottom box)  - Select the following options: "Address String", "Private Key (Plain Base58)","Include Unused (Address Pool)"... and make sure "Omit spaces in key data" is checked  You'll end up with a list of all the addresses and private keys displayed in the text box. The private keys will be labelled as "Plain Base58" You can then "import" or "sweep" those private keys using the wallet of your choice (like Electrum or Bitcoin Core). I would highly recommend "sweeping" (as opposed to "importing") as the private keys could potentially be compromised/exposed during the export/import process.
|
|
|
|
|
Show Posts
