|
The blue dot next to the manager has been there for a while I think... I vaguely recall seeing it in previous versions of Ledger for previous updates to coin apps.
|
|
|
|
Yeah... Bitcoin Core works with Legacy (P2PKH), Nested Segwit (P2SH-P2WPKH) and Native Segwit (P2WPKH) all at the same time without issue... my current wallet.dat has all 3 types in it... and I certainly don't have problems sending anything. I even sent a transaction today. There must have been something peculiar to your specific setup that was preventing the transaction from being sent... either your node or the wallet itself was in some state that was preventing it from broadcasting the transaction to an external node. Did you attempt to broadcast the transaction using an external service as suggested above? If that worked, it would have ruled out issues with the transaction itself... or highlighted issues with the transaction, if it didn't. I guess we're not likely to find out given that it sounds like you have since moved the private keys (or coins) to Electrum and then sent from there...  |
|
|
|
I don't think you will be able to use that site, as there are some other background things happening that I don't think that website supports, but assuming you can decrypt the master key, then it should theoretically be possible to then decrypt individual private keys. As for decrypting the master key, I found this project which claims to be able to extract the encrypted master key, salt, IV etc from a wallet.dat: https://github.com/brichard19/core-decryptThere is also an OpenCL based project included (and a precompiled .exe  ) that claims to be able to test the master key decryption using a password dictionary. The idea being that you can identify what the wallet passphrase is... it doesn't decrypt individual keys, and it doesn't show the decrypted master key etc. It just seems to test the "encrypted master key" decryption using passwords you pass in. If this information regarding wallet.dat encryption is still valid: https://en.bitcoin.it/wiki/Wallet_encryptionThen it looks like you would need to start playing with your wallet passphrase, SHA512 and OpenSSL "EVP_BytesToKey" functionality (along with the extracted IV, Salt, iteration count etc as extracted by the python script) to derive the "key" needed to decrypt the "encrypted master key"... and then once you have the "unencrypted master key", you should be able to decrypt the individual private keys. |
|
|
|
I have rememberd I think
I have found pycrypto software which i need to run in python. This will probably solve the text and password.
pycrypto is just a Python library that offers "easy" access to various encryption algorithms... while it may be possible to use it to decrypt the cipher text using your password, you still won't be able to do so without knowing the correct encryption algorithm to use. I guess one advantage is that you'll be able to try the decryption locally using Python and pycrypto instead of relying on external tools etc. The downside of course is that there are quite a large number of algorithms that you will need to try. Good luck! |
|
|
|
cant load my wallet which is why i'm trying to get the private key this way, the wallet is corrupted. i have the public address that the coins been sent and about the ''malware on that computer, you'll probably lose your money'' i'll be doing it off line so i should be good but thank you for the heads up
Have you tried the salvage feature of the "wallet-tool" that comes with newer versions of Bitcoin Core? Not sure if this is actually available in Litecoin Core as yet. In which case you'd need to use the -salvagewallet option when starting Litecoin Core and see if that helps. Alternatively, you can use PyWallet to try and recover data from Litecoin wallet.dat's... you just need to use the --otherversion argument and provide the appropriate version... which for litecoin would be 48. As always, only work with copies of the wallet file! |
|
|
|
Not only that... but there are several instances in the BIP39 list where the addition/subtraction of a letter can still result in a "valid" word... like "kit" and "kite"... or "law" and "lawn" etc To be honest, the BIP39 list isn't that great at achieving some of it's stated goals of "distinct" words |
|
|
|
|
Indeed... usually if it is not accepted by the external node when broadcasting, you will receive some sort of error message.
Attempting to rebroadcast the transaction manually from the console using sendrawtransaction should either get it going or at least return an error message that will hopefully give some indication as to why it's failing.
Alternatively, the OP could try and cancel/abandon the transaction given that it hasn't been successfully broadcast, and then they could just try and create/send the transaction again from the GUI.
|
|
|
|
Well it starts with K so i presume 5 is needed to add on it. But so it is confirmed that electeum does not take old bitcoin private key. Also how do i add my old address on bitcoin core latest.. it only has button saying create new address.
There is no button to press, you have to do it manually through the consoler. So, goto the console: "Window -> Console" Then type: importprivkey YOUR_WIF_PRIVATE_KEY_GOES_HERE
Also why does electrum wallet does not take old 2009 bitcoin private key. Do i have to change it to some other format.
You cannot import a private key into a "standard" Electrum wallet that was created with a 12 word seed. The reason for this was that the dev's felt that it was "dangerous", as some users might not understand that by importing a private key, it would not be backed up by the 12 word seed... and they might not take adequate precautions to ensure the private key was also backed up manually. To use that private key in Electrum, you have to create a completely new (and separate) wallet in Electrum (as outlined above using "New\Restore -> Import Bitcoin addresses or private keys"... This will allow you to import your private key. Once you are finished, you will note that the wallet type will be displayed as "[imported]"... note that you will need to ensure that you have the imported private key(s) and/or wallet file safely backed up. |
|
|
|
1. We don't know the data is private key, public key or other data (maybe it's possible by check HEX length).
Should be easy enough given that the Database Schema is public knowledge... Even some basic "trial and error" type testing using PyWallet output or other known data (private keys/public keys etc) should mean it would be relatively simple (if somewhat time consuming) to be able to determine which outputs in the db_dump are the private keys etc. for instance: page 4: btree leaf: LSN [0][1]: level 1
prev: 0 next: 84 entries: 90 offset: 2432
[000] 8148 len: 39 data: 04636b6579210201df7814f1bfdc65694230553d9fea229e34fc096b27611881e5924e045e955e
[001] 8064 len: 81 data: 305048baa5553a6e650272560b11709abe027d96d01a6cdb67646632ebb3d39bafdeb5af63e8386e899c5f03194afd925e5a0dea80180867296864761c6d4a583d21dc7b6ac7a7cea38c2eea0825a25aef
[002] 8020 len: 39 data: 04636b6579210201e1dadb18af47c2f457aeb9892e9bc9986101d2a5a32cb85fce217b191472f9
[003] 7936 len: 81 data: 300f05de99d0a5bcaa86f15d9fc7d809b45a61f6826e559d0041f48f5fa4568b495cb973d7d8238a85e5afabce56e5fcfb0d7e0f66e7379f04fc181544273bfdde701587c745ce0d552d25546bcf01c69c
From PyWallet: "keys": [
{
"addr": "1NU7VwXy3Ugb1NPFYy9Y76Q6DvzMtrihuj",
"compressed": true,
"encrypted_privkey": "5048baa5553a6e650272560b11709abe027d96d01a6cdb67646632ebb3d39bafdeb5af63e8386e899c5f03194afd925e",
"pubkey": "0201df7814f1bfdc65694230553d9fea229e34fc096b27611881e5924e045e955e",
"reserve": 1
},
{
"addr": "18NvdAH4yGytm6C9vpPAvrHHXLdKwaERFK",
"compressed": true,
"encrypted_privkey": "0f05de99d0a5bcaa86f15d9fc7d809b45a61f6826e559d0041f48f5fa4568b495cb973d7d8238a85e5afabce56e5fcfb",
"pubkey": "0201e1dadb18af47c2f457aeb9892e9bc9986101d2a5a32cb85fce217b191472f9",
"reserve": 1
},
We can see that the pubkeys are in the "len 39" data with a prefix of "04636b657921": "pubkey": "0201e1dadb18af47c2f457aeb9892e9bc9986101d2a5a32cb85fce217b191472f9"
[000] 8148 len: 39 data: 04636b6579210201df7814f1bfdc65694230553d9fea229e34fc096b27611881e5924e045e955e We can also see that the encrypted privkey data is in the "len81" data with a prefix of "30" and a unique trailing sequence of bytes: "encrypted_privkey": "5048baa5553a6e650272560b11709abe027d96d01a6cdb67646632ebb3d39bafdeb5af63e8386e8 99c5f03194afd925e",
[001] 8064 len: 81 data: 305048baa5553a6e650272560b11709abe027d96d01a6cdb67646632ebb3d39bafdeb5af63e8386e8 99c5f03194afd925e5a0dea80180867296864761c6d4a583d21dc7b6ac7a7cea38c2eea0825a25aef The real issue is extracting the encrypted data... I'm not sure if the db_dump "-P" parameter is actually able to decrypt the encrypted keys or if it is meant for some other purpose. I can't get it to produce the unencrypted keys in the db_dump output. |
|
|
|
|
If it's a watching-only wallet from an HD wallet... and they have access to the master public key in it... and they somehow gain access to just one of your private keys, then, technically, they could derive ALL the private keys from your wallet.
otherwise... someone getting your watching-only wallet is more of a privacy issue than a security issue.
|
|
|
|
|
Why is a mistake possible with only one device?
Reset device, create new seed (backup new seed!)... get master public key, create watching only wallet in something like Electrum... reset device, enter old seed... send ALL coins to mixer... get addresses from "new seed" wallet using watching only wallet... send coins from mixer to new seed addresses.
Reset device, enter new seed... live happily ever after.
Having 2 devices would definitely make it easier, but there is no reason you can't do it with only 1 device... it's just a bit more tedious.
|
|
|
|
Given the information provided so far... I'd say the chances of recovering the wallet are, unfortunately, pretty low. Unless you still have the old harddrive (that got erased) and you're able to somehow recover the original wallet.dat from that hard drive using data recovery applications, then you're not going to be able to do anything. The email address, the password, the bitcoin address etc are all useless without the private key... which is contained in the wallet.dat... which has been erased. |
|
|
|
oh man... if I had known you just wanted a little local Electrum server... I would have recommended electrs  I thought you were trying to get your own public facing Electrum server up and running.  I have successfully had electrs running under WSL+Ubuntu (reading a Windows based Bitcoin data directory and connecting to it from Windows based Electrum)... it works a treat and has a relatively small footprint. It "syncs" relatively quickly if it's been offline for a few days, although the initial build+initial sync process can take a while. |
|
|
|
No there is * at the end of the pass but there is no =
Oh snap... I just realised you said the * was at the end of the "pass"!  I'm an idiot! this is what the tex looks like
AQAAxxxxxxx+AAUxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxR0RR
xxxx are numbers and letters no other signs
It likely is a Base64 representation of some encoded text... I was experimenting here: https://encode-decode.com/blowfish-encrypt-online/and discovered that with a 12 character password ("password1234"), there are several encryption algorithms like Blowfish, des, cast etc that return 76 character encrypted text when you encrypt a private key. ie. Blowfish: L5RGSf2pShsFAbtUXeQwdsCWWuo4qLkaVaSJX2nVCTupAxhCU3Gk
BT33LMVnYpnNk+eCy32KI3aQaBzeH8TQZtUvs0WZ1TO5ndJGiBP0JcnNq9WsKRNH8icgHWeCbAQ=
Now, I DO NOT recommend that you go an put your cipher text and password into some random encoder/decoder website like this... but it might be worth seeing if you can find some reputable encryption tools that you can use to try testing various encryption algorithms with your cipher text+password. |
|
|
|
|
That looks pretty good. A solid description of the error... what you were doing when you found it and the steps required to reproduce it. I like that you also mentioned that file/usb work OK.
About the only other things I would add to the report would be:
- OS on online machine
- OS on offline machine
- Version of Electrum on online machine
- Version of Electrum on offline machine
and possibly the firmware on the Ledger device and the version of the Bitcoin "coin app" installed on your Nano S.
|
|
|
|
what are the exact first 4 characters and the exact last 4 characters of your "text"? I've been trying to figure out what format it is in... and I'm wondering if there is more to this that we realise from your description. Again, obviously, don't post the whole thing as it is apparently only protected by a 12 character password |
|
|
|
My guess is that you are using a 2FA wallet!
I concur... given there are only 5 UTXOs... it doesn't seem like a (transaction size * high fee rate) == HUGE total fee issue... it sounds more like a 2FA wallet trying to add in the "prepay" transaction output. If Electrum says [2fa] in the titlebar next to the wallet name... then you need to read this: https://api.trustedcoin.com/#/faq#feesIf you are not willing to pay for these fees, you have 2 options: 1. click the Blue Shield in the bottom right corner and select the "prepay 20" option... that will only require 0.0005 BTC instead of 0.00125 BTC to buy 20 credits instead of 100. or 2. Restore your wallet from your 12 word seed phrase and select "DISABLE" when prompted to "keep or disable" 2FA functionality. This will put 2 of the 3 sets of private keys into your restored wallet which will enable you to send without using the 2FA functionality and means you won't have to pay the 2FA service fees. |
|
|
|
It would appear that the QR Code encoder (or decoder) is not including something during (de)serialization that the Ledger plugin requires... It's quite possible the code that fixed the issue for the other issue was not included into the Ledger plugin, but should have been. If you haven't already, I would suggest that you log an issue on Github: https://github.com/spesmilo/electrum/issuesInclude the relevant log file date in your issue report and don't forget to mention that you're using a Ledger Nano S. |
|
|
|
|
Who had access to one/some/all of the keys? Just you or were other parties involved in this multi-sig setup? What devices were these keys stored on? Are they all clean? Have they been audited? What other activities are these device(s) used for? What OS(es) are being used? What security protocols are in place to secure the devices?
|
|
|
|
You're not wrong that a physical box can be a big blinking warning sign to thieves. I have heard anecdotally from acquaintances in law enforcement about situations where a house has been burgled... the owners made insurance claims etc getting all new stuff like TVs/Laptops/Phones/Computers etc... and then put the boxes for all the new toys/gadgets/applicances out for recycling... basically, like a giant sign to the thieves "Hey, we got all new stuff!" aaaaaaaaaand then they got burgled again a day or 2 later! 
Having said that, it should be easy enough to dispose of the packaging for a hardware wallet without it being obvious... most come in relatively small packages... so destroying it shouldn't be that hard... a knife/scissors, or some fire would work well and if you're paranoid that someone may be "dumpster diving" your trash, go for a walk around town and drop it in a random trash can or dispose of it in the trash at a McDonalds or something. Even if someone finds it, it won't be able to be tracked back to your address. |
|
|
|
|
Show Posts
