This bump (and a few moments of spare time) dropped me into the Ledger Live + SatStacks + Bitcoin Core rabbit hole...  I'm just spent a couple of hours trying to get this working... it's not terribly user friendly... it creates a new "satstacks.dat" wallet in your Bitcoin Core datadir... and then effectively "locks" your Node:  AND "locks" your Ledger bitcoin accounts while it rescans the blockchain for your new satstacks.dat wallet  Additionally, you need to run the "lss.exe" (aka Ledger SatStacks) application in a separate process... and have it running alongside LL+Bitcoin Core to make it all work. Also, as soon as you try and setup your "accounts", they all get deleted from Ledger Live until you've finished getting it all configured and then manually re-add them Another negative is that all your accounts/xpubs and the RPC user/password are stored in plaintext!!?!  in the lss.json file in your Ledger Live userdata directory. On the plus side, actually adding the accounts to Ledger Live is super fast compared to when you try to do it via the Ledger servers. It added all my accounts pretty much instantaneously! But given how long it actually took for it to setup/scan them all in Bitcoin Core anyway, that's kind of irrelevant  Honestly, it's definitely a good thing that they're offering this functionality and attempting to get this working to give users the opportunity to utilise private nodes instead of the Ledger servers, I'm just not terribly impressed with the execution so far. It was far easier to simply setup an Electrum server (I use electrs) and then connect my Ledger to Electrum that is configured to only connect to my local node: electrum --oneserver --server=localhost:50001:t
|
|
|
|
In August I noticed the Nano S firmware needed an upgrade so rather than risk any problems I transferred the full balance (all BTC native segwit) to Coinbase. Then I reset the Nano S by incorrectly entering the PIN multiple times and then set it up as a new device with a new 24 word recovery phrase.
I then transferred the full balance back from Coinbase which showed up correctly in Ledger Live both on my Macbook and on my phone.
Can you remember what the error message was? I am a little concerned here that your Ledger Live was still showing your old accounts and had not synced up properly to your new accounts. If this is the case, there is a chance you have sent your coins to an address from your old accounts, in which case they would be lost unless you can find the original seed phrase.
I concur... When you reset your Ledger and then reconnect it back to Ledger Live, it does not automatically remove your old accounts... So, when you got your "new" Ledger "receive address" (the one that you sent the coins back to from Coinbase), did you actually connect your device to Ledger Live and complete the "receive address" confirmation process?  Or did you just click "Receive" and then "don't have device" and then copy/pasted the (unconfirmed) address that is shown?  If you didn't confirm it... it's possible that you actually used an address generated from your old Ledger seed... which sounds like it could be problematic because you no longer have access to that seed |
|
|
|
then it was only pure wallet.dat file or does it json-rpc can you lighten me up a bit,
To the best of my knowledge... it has always been a "wallet.dat" wallet file. The JSON-RPC stuff seems to have been first added around version 0.3.0, in early 2010 (February)... based on this commit in the old repo on sourceforge: https://sourceforge.net/p/bitcoin/code/60/Passwords (wallet encryption) were added to Bitcoin-Qt in version 0.4.0 (released 23 September 2011): https://bitcoin.org/en/release/v0.4.0 |
|
|
|
If your 12 words don't work here: https://login.blockchain.com/#/recover and your 12 words don't here: https://login.blockchain.com/wallet/forgot-password?guid= and your 12 words don't work when you import into Electrum using the BIP39 option... then you don't have the same issue as that user. You know your walletID which is a good start... but the way blockchain.info worked, your 12 words were either a "password recovery" option, or they will restore your "HD" wallet (which were created in around 2016). In any case, you said originally that you had your funds in an Electrum wallet in 2014... so I'm a little confused as to why you're now talking about blockchain wallets and providing blockchain wallet IDs? Based on the info you provided earlier, the 12 words you have seem to be creating an "old" Electrum keystore... which means that those 12 words will not be BIP39 compatible. Are your 12 words all found in this list: https://github.com/spesmilo/electrum/blob/master/electrum/old_mnemonic.py#L31 ? |
|
|
|
|
"Parsing Tx Hashes" shouldn't take very long... certainly not more than a few minutes...
If it is stuck, you'll need to post up the latest version of your log files. Alternatively, you can try using the "Help -> Rebuild and Rescan Database" option and then restart Armory.
|
|
|
|
If you use the -i on it's own and a mask like this: Hashcat will actually try: ?a ?a?a ?a?a?a ?a?a?a?a ?a?a?a?a?a ?a?a?a?a?a?a ?a?a?a?a?a?a?a ?a?a?a?a?a?a?a?a It is essentially the "brute force" mode... So if you only use -i and --increment-max, it'll start at length 1... and go up to the max. Seems somewhat pointless, as you could just set the "max" with the length of the mask and setting max to something less than the mask length seems a bit pointless  The --increment-min is probably more useful. |
|
|
|
While I didnt figure out how to open python 2.7. in the folder I created for unzipped files and the key / wallet file - I could only open powershell, which says there is no python -
Don't use powershell... you need the "standard" windows "command prompt"... you'll need to press the "start" button, then type cmd (or press "Win+R" and enter cmd) So I installed openssl but I dont know what to do with it. When I open command console in windows and enter the recommended line it says the commando openssl is not known. If I go the folder where the .key file is in and open powershell there, I get an error msg (I will translate whats not english):
It's saying that because "openssl" is not installed in your "PATH"... when you type commands, windows looks in some very specific places to find the command/app to run... if you haven't told Windows where to find "openssl", it won't be able to find it. Again, don't use powershell... that won't help. However, read below... it should solve your problem and make it easy for you to run the scripts without needing to use the command prompt I was able to open .key file by simply drag and drop it onto decrypt_multibit_classic_keys.py . It asks for the pw; if I enter it wrong it says: "incorrect password". If I enter it correctly, python just shuts down.
When I use drag and drop for .wallet file onto decrypt_multibit_classic_walletkeys.py python only opens for a split second and then closes again.
Do you have an idea how I can get the desired output instead of python just shutting down?
It's because there is no "pause" in the script, it's just dumping output and then the "py.exe" window will be closing immediately. A small oversight on my behalf, as I never imagined anyone would use "drag and drop" So, I have just updated the scripts... and they now have a "Press any key to continue..." prompt at the end of them. If you redownload the scripts: https://github.com/HardCorePawn/multibit_recovery you should find that you can use the drag and drop, enter the password when prompted and it'll now wait at the end and you can see the output I've even updated the "Readme" to include a note about "drag and drop"... thanks for the idea! Also please note: I think I have my key allready unencrypted, however it looks off. Its format goes like this:
U2Fs........................................................................... ....
Wdo............................
No... that is encrypted... the "U2F" indicates that you have an aes-256-cbc encrypted file. |
|
|
|
|
I don't think a new licence can apply to old versions of the code... you can't (or at least, you shouldn't be able to) retroactively change the rules like that. Imagine if you have a repo that people had been forking for years and then just suddenly decided "you must pay $1000 to use this code".
Anything created after the date of the licence change should be covered by the new licence... but anything that was done prior to that, should be covered by the old licence.
|
|
|
|
First off, thanks for being patient with me. I copied and saved the wallet to a differ folder. When I click on the link you provided to see the list of download, I see the 2.9 that I originally had but there are a number of differ names so not sure which 2.9 to download.
If you're using Windows, I would recommend that you use the "portable" 2.9.3 .exe from here: https://download.electrum.org/2.9.3/Note that you should use the "portable" version only for this task... and only because it won't interfere with (nor be interfered with by) the currently installed version as it creates it's own "local" data directory etc. and won't try to use the common Electrum data directory in the "AppData" directory etc. |
|
|
|
This tries all ASCII characters. Unfortunately there is no shorthand syntax for ranges of passwords.
Yes, there is Have a look at -i, --increment-min and --increment-max as described here: -i, --increment | | Enable mask increment mode |
--increment-min | Num | Start mask incrementing at X | --increment-min=4
--increment-max | Num | Stop mask incrementing at X | --increment-max=8
So, if you know the password is between 6-8 chars... hashcat -m 22500 -a 3 multibit_hash.txt -i --increment-min=6 --increment-max=8 ?a?a?a?a?a?a?a?a
will only check the masks that have 6-8 chars in them |
|
|
|
Today I walked in with my 12-word phrase that I had kept in a neat notebook.
What else have you done with that 12-word phrase? What other wallets have you entered it into? Did you claim any bitcoin forks? Did you try and claim any airdrops by entering your phrase into a website? |
|
|
|
Oh sounded like he was doing it on other wallet software how you'd recover a key in emergencies.
Originally, yes... that is what the OP was doing to confirm they had the correct seed. All the users here pointed out that doing that is a "bad idea"™ because entering your seed into a "normal" wallet like Electrum etc is effectively negating the entire purpose of the hardware wallet (ie. it is exposing the seed) OP was then instructed to try the official Ledger "recovery check" app (needs to be installed via Ledger Live/Manager) and use that to confirm they have the seed backed up correctly... which they eventually did. I don't see electrum doing the seed in hardware?
I'm not quite sure what you mean by this? |
|
|
|
Have you tried shutting down and then restarting Bitcoin Core using the -reindex option since you used reconsiderblock? That should hopefully help Bitcoin Core find and remove any corrupted blocks stored on the disk... |
|
|
|
hello i have 1 word missing from my seed and i need help to find a program to restore my BTC. i have just that 11 words, no addresses or other details as this was years ago. Thank you in advance
- What wallet did you use to create this 12 word seed? - Do you know what position the missing word is supposed to be? - Are the 11 words you current have in the correct order? This isn't the "best" case scenario... but it's not "bad"... not knowing any addresses will slow you down as you'll need to manually check every valid seed combination that you can generate from your 11 words +1 "guess" word and see if any of the first 5-10 addresses have "history" to know if you're found the "correct" seed. Not ideal, but a script and a blockexplorer API should be able to work that for you. |
|
|
|
Also, it's possible to use the "multibit2john.py" script (that is part of JohnTheRipper) to extract a hash from either a multibit .key (preferred option) or a multibit .wallet file (VERY slow to crack as it is encrypted with Scrypt). The hash output from multibit2john.py will look something like this (for a .key file): cwoern.key:$multibit$1*0b4989bdf01e4746*02d61e0c77e7131cb12a638ed742f571ba884621f4e0bebdfc900357cd9a310a
Once you have the hash, you can use "hashcat" to attempt to crack the password. To do that, we copy everything after the ":" and put it into a .txt file like this: $multibit$1*0b4989bdf01e4746*02d61e0c77e7131cb12a638ed742f571ba884621f4e0bebdfc900357cd9a310a
And then the hashcat commandline should be something like: hashcat -m 22500 -a 3 multibit_hash.txt <PUT YOUR HASHCAT "MASK" HERE>
You can practise using the hash above... and the mask ?a?a?a?a?a?a: hashcat -m 22500 -a 3 multibit_hash.txt ?a?a?a?a?a?a
And it should find the password "abc123" relatively quickly. For your .key/hash, you'll need to experiment with different "masks" based on what you believe the password is likely to be... refer here: https://hashcat.net/wiki/doku.php?id=mask_attackFinally, unless you have a fairly good idea of what the password was likely to be, and that it's relatively short... your chances of bruteforcing it aren't great |
|
|
|
Inputting your seed unnecessarily decreases your security. Just test it once on your ledger and that's it. Your seed is your backup.
The "recovery check" ledger app is designed exactly for that purpose. You really aren't decreasing your security at all as you are entering it on the device... not typing it into a PC etc. It's basically just like entering it during a full device restore. |
|
|
|
In response to HCP reply-Forgive me a as I'm new to this. How do I go about doing that? Note: I was able to get in the original wallet initially but wasn't no longer able to get in after I updated to the new version and do not have the seed.
Follow khaled0111's advice and download the old version from https://download.electrum.org/ (hopefully you remember the exact version you were using!) Note that attempting to open with an older version may not work if the "new" version of Electrum that you tried (and is now crashing) modified the wallet file and "upgraded" the wallet version before it crashed. If it did, you will likely find that the old versions will now refuse to open the "updated" wallet file Do you have old backups of the wallet file or did you make copies of it before attempting to open with the updated version of Electrum? |
|
|
|
Absolutely brilliant. The rescan worked and the transaction showed up. I was initially confused by the fact that the missing transaction was essentially the same as the transaction sent to the change address.
Excellent... glad you managed to get it showing up properly! Always concerning when unexpected things happen The fact that neither the sending or receiving addresses in the Bitcoin Core interface didn't show the new change address was also confusing and a little scary (I thought for a while that my wallet had randomly sent funds to someone else's address!!), but everything seems to be there and working as it should now.
Yes, Bitcoin Core likes to keep "change" addresses hidden from view... they're almost completely internal to the application and not easy to see. They won't show in the "Sending Addresses" nor "Receiving Addresses". The only place I've seen them within the application is if you enable coin control and then click the "Inputs" button on the send tab... Also, if you use the getaddressinfo command, the "ischange" value will be true. And of course if you use the dumpwallet command (not recommended as it risks exposing private keys etc), you can identify them based on the "hdkeypath" (should be m/0'/ 1'/...) and once "used", will change from reserve=1 to change=1) |
|
|
|
Alternatively, you could send 0.00000031 BTC back to the address you received it from using a 2 sat/byte fee when the mempool is low. This would get all the dust out of your wallet, send a useless amount of dust to the person who dusted you, and donate the rest to Bitcoin miners.
That's a good idea... except for the fact that creating an output of 0.00000031 BTC would put it below the dust limit and mean that your transaction is likely to be rejected by other nodes if you attempt to send that. There is a reason why these pests create UTXOs of 0.00000547 BTC |
|
|
|
I clicked on the Electrum application on my desktop, created a new wallet and able to access it successfully. I closed the window, clicked back on the Electrum application on my desktop and entered my password for the new wallet again and was still able to access it When I close and reopen the Electrum application on my desktop, access the original wallet and enter password, the box or window closes. However, if I access the new wallet and click on file, open, click on the original wallet and enter password, I get an error message, I'm unable to post the image but it says.
Unfortunately, that sounds like your old wallet file is corrupted!!?! Do you remember what the old version you were using was? If so, you might be able to reinstall a copy of that older version, open the wallet file, extract your private keys (and/or seed) and then import the private keys (or restore from seed) into the new version of Electrum. |
|
|
|
|
Show Posts
