I've honestly not seen that message from decrypt_bitcoinj_seed before... but it sounds like your BTC might have been on imported keys? and NOT on addresses that were generated from the HD wallet seed mnemonic?  It should be possible to dump the wallet file out, but it would require some Python hacking... I have a version of decrypt_bitcoinj_seed which just dumps the decrypted/parsed wallet data to a text file... it may or may not have encrypted keys in it tho... which requires more work  As for why your addresses on the phone are different from the BIP39 tool... I can only theorise that the addresses you are seeing are not being generated from your seed phrase? Those are definitely the correct derivation paths... I've just tested it with my phone. |
|
|
|
Also I tried the trick of importing the aes backup file into the old version of Multibit. That succeeded and I see a notice 1 private key imported. But how can I get that private key on my screen to copy it and rush to my wallet to take the cash since 4 years?
Did you look in the "Tools" menu in MultiBit? There is an "export private keys" option... when you select that, DO NOT password protect the output file (that encrypts it)... once the export is done, simply open the output file in a text editor and you should see your private keys Video here (Ignore the stuff about importing to Electrum ): https://youtu.be/LaijbTcxsv8?t=21s |
|
|
|
|
I forget if I moved my BTC first... I think I sent it to a hardware wallet first... then I just copied the Electrum wallet over to ElectronCash and sent the BCH to my hardware wallet. Copying the wallet file is maybe a little safer than typing your seed in... it avoids keyloggers capturing your wallet seed.
I did something simliar with Bitcoin Core and Bitcoin ABC... Transferred BTC first, then loaded wallet up in ABC and transferred BCH out.
It was all done on the same computer.
|
|
|
|
I'm confused... you say "I did it, there're now coins imported"... then you ask how to import coins to a new wallet??!? Isn't that what you just did? You just imported the coins using a private key? What are you ACTUALLY trying to do? |
|
|
|
and if they knew how to crack my simple passwords (brute force) they would have a nice treat.
How simple is simple? Are we talking <10 characters? only letters and numbers? If so, it's possible that you could brute force that... anything longer or more complicated and the odds reduce significantly... |
|
|
|
There seems to be an unhealthy level of suspicion regarding ElectronCash... providing you have downloaded the official ElectronCash app from the official page: https://electroncash.org/#download you should be fine to use it. The source code was forked from Electrum and is open source. The commits listed on the github don't add anything nefarious into the code base. And if you're concerned about running pre-built binaries, you can easily run it from source and/or compile it yourself... Having said that, it is still a good idea to move your BTC prior to attempting to get your BCH, simply because getting your BCH will require you to either enter your seed or export/import your private keys... Both of these procedures could potentially compromise your wallet and coins. So, if your BTC is already moved, you know it is safe and only your "forkcoin" is potentially at risk. Sound risky to me, is there any other wallet which is 100% safe for BCH and support Electrum seed ?
The only thing that supports Electrum Seed is Electrum and forks of Electrum... like ElectronCash... No-one is going to be able to give you a "100% safe" guarantee for any bitcoin wallet. If ElectronCash was unsafe, we'd know about it by now... the initial rush after the fork and the recent big pump and dump have seen so much BCH action that if ElectronCash was doing anything "bad", this forum would be full of threads telling us. EVERY time someone has had coins stolen is because they exported private keys on a compromised PC or downloaded a fake version of the wallet. I've not seen one substantiated claim that ElectronCash stole someone's seed/privatekeys or coins in the 3 months that it has been operational. If you're that concerned about it, install a VM like Oracle Virtual Box... and create an online/offline system... so the "offline" ElectronCash system restored from seed is on the VM with networking disabled. If I export all of my BTC address' private keys from Electrum then add them to blockchain.info will I be able to use all the BCH I received after the hard fork ?
Assuming b.info supports BCH then yes... you should be able to see it. I would say that exporting your private keys and then entering them into a website is more risky than using ElectronCash. |
|
|
|
This post has seriously grabbed my attention. I very foolishly have managed to lose my password and seed (I know, I know) for my Electrum wallet.
After reading this:
"I see you've figured out how to decrypt the new seed from scene 2 using the console"
And seeing this:
>> import aes
>> from electrum import wallet
>>wallet.pw_decode('bBbGXH3ivbmwapRODeAn7wp7VviwDkpNOcaRdW9EDiA5xeYXj8CtrUidHvRbCubIJhMaPjlEOfO0kQM 13RB6Zw==','125')
u'431a62f1c86555d3c45e5c4d9e10c8c7'
Am I right in thinking it is somehow possible to decrypt the password? I do have the original wallet file in full.
No... what that function is doing, is decoding he encrypted seed from the wallet file... using the password!I think you missed the bit where he said his password was '125'... ...
Now I need to figure out how to push this info in this function-
Wallet pass = 125
Seed = 431a62f1c86555d3c45e5c4d9e10c8c7
You have to give the function the password as the second argument... hence: wallet.pw_decode('bBbGXH3ivbmwapRODeAn7wp7VviwDkpNOcaRdW9EDiA5xeYXj8CtrUidHvRbCubIJhMaPjlEOfO0kQM 13RB6Zw==','125') Interesting. Question: Do you use the phrase "hex" here to imply the base 58 encoded string? Hex traditionally meant base 16 eg 0-9 and a,b,c,d,e,f.
No... he meant "hex"... the "seed" which is essentially just a big number... was previously stored in the wallet file in hex... as per the OP: Scenario 1: I have an unencrypted wallet i.e. no password was set for the wallet. I have the wallet file; when we I open the file as text I could see ....
"seed": "431a62f1c86555d3c45e5c4d9e10c8c7",
....
|
|
|
|
Seems like a normal transaction. I assume you purchased around US$13 worth of Bitcoin... the site you bough from, transferred your 0.0018879 BTC to what I am assuming is your address: 1M1ZRPDhaSsPDfTr8JPvUBPFdBzWRw2Lu8 The other value that was sent to the "3" address, is what is known as "change". You can read about it here: https://en.bitcoin.it/wiki/ChangeYou can read why change gets created here: https://en.bitcoin.it/wiki/Coin_analogyBitcoin does not work like typical money in a bank... you don't have a balance that you can spend exact amounts from. You have a collection of "coins" all of varying sizes... if they amount you want to send is not exactly the same as a coin you have you'll end up with change. The transaction output being labelled as "unspent" just means that that particular coin has not been used in a transaction yet. You can see that the output is now "spent" because the output has been used in a subsequent transaction. |
|
|
|
The 1.21974373 BTC is what is known as "Change". You can read about it here: https://en.bitcoin.it/wiki/Change"Change" is created because of the way Bitcoin works... it doesn't send just the amount you request, it has to spend whole outputs generated from previous transaction. So if you received 0.5, and you want to send 0.1... it spends 0.5, sends 0.1 to the other person and you get 0.4 back as "change". I suggest you read this to help understand: https://en.bitcoin.it/wiki/Coin_analogyAgain... "change" "seen by peers" just means your transaction has been broadcast... it still needs to be mined into a block to be confirmed. Which isn't likely to happen for a long time... given your fee is "Fee per byte 1.499 sat/B"!!?!  Current recommended fees are like 150-300 sats/Byte... check: https://bitcoinfees.earn.com/ and https://btc.com/stats/unconfirmed-txAgain... a low fee... not as bad as the other one, but still... Fee per byte 29.412 sat/B. Also, this transaction is spending an output from the previous unconfirmed transaction. It will never be able to confirm until that transaction with it's 1.499 sat/byte fee confirms... Which is likely to take a LONG time. — What can i do to get my BTC from this «transaction's space» to wallet?
Basically... you wait. The network isn't quite as busy as it was a few days ago... https://blockchain.info/charts/mempool-count but still ~50,000 unconfirmed transactions waiting... a lot of which pay more in fees than yours  Also, you should really stop using both MultiBit Classic and MultiBit HD. BOTH of these are no longer being developed or supported ( https://multibit.org/)... BOTH of these have issues which will make sending your bitcoins difficult (MBC sets fees way to low and no way to change, MBHD uses slightly higher fees but still way to low... it also has the dreaded "Password did not unlock the wallet" bug) I would suggest you follow the instructions on their blog post ( https://multibit.org/blog/2017/07/26/multibit-shutdown.html) to enable you to migrate to Electrum. They even have videos walking you through the process. Multibit HD: https://youtu.be/E-KcY6KUVnYMultibit Classic: https://youtu.be/LaijbTcxsv8That's the reason why I'm here. My Multibit Classic version is the newest and there is no way to adjust this fee.. so all my transactions never get confirmed.. If anybody has a workaround I'll be glad to hear  Likewise... drop MBC... don't use MBHD either... switch to a different wallet... MultiBit is DEAD. |
|
|
|
Anyway I now have to exchange Komodos through exchange but was hoping to exchange it directly in Exodus. Thank you for your response.
You realise that all Exodus does is push your coin exchange through shapeshift.io right? The only benefits of using Exodus are that all your coins are in one place... and I think they may get slightly better exchange rates due to the large volume they're likely generating, but I'm not 100% sure about that. However, in effect it is really no different than going to the website, setting up the exchange transaction and then sending the coins from your wallet yourself. |
|
|
|
Exodus don't hold your private keys... you do. You have your 12 word backup seed. This is BIP39/44 compatible and easily portable to any other compatible wallet. As far as I'm aware, your seed/private keys are only stored on your local device. Exodus have NO access to this, so there is no way for Exodus to "exit" scam. Unless they've filled their software with backdoors that allow them access to your keys... but you can just check the source code to see if tha... oh... wait.  |
|
|
|
Yeah... I mean, who wants a wallet that takes up less than 50 megs of HDD space, loads up and syncs in a matter of seconds... when you can commit 180+GB of disk storage and a week of your life to syncing Bitcoin Core? Lightweight SPV wallets have their place and their use cases... just like full nodes, brain wallets, web wallets, paper wallets, hardware wallets and mobile wallets. Just because they don't suit your particular needs, does not make them inherently bad. |
|
|
|
I've had issues on other websites due to adblockers and "ghostery". Do you have any browser addons loaded that block cookies/javascript etc that might be interfering with the exchange functionality? Aside from that, all I can suggest is that you contact b.info support and see if they can explain why their system is broken |
|
|
|
Basically, at this point you are down to "brute force"... btcrecover ( https://github.com/gurnec/btcrecover) is probably your best option... If the password was correct, but the file was corrupt, you'd probably get weird output from my multibit_recovery scripts... But you're getting password is incorrect, which tends to indicate exactly what it says... the password is incorrect.  |
|
|
|
okay, but seatbelts exist for a reason.
Yes, they do... And how many people die each year from not wearing seat belts? Which, sadly, proves my point... |
|
|
|
|
Installing that PWI as described should install pywallet and all the dependencies...
Did you try it to see if it works? Are you getting errors?
The web browser is just the fancy front end to make using pywallet easier. It isn't strictly necessary.
After you use the PWI, you will find a pywallet.py file in the location you extracted the files to... You can execute that script using the command line if you don't want to use the web browser
|
|
|
|
There is a "Truism" that states: 'Make something fool-proof... and they'll just invent better fools' It doesn't matter how many warnings people put up, or how simple you make something... someone will always find a way to screw it up... that's just human nature. And you won't be able to stop the tide of scammers, hackers and thieves... wherever there is a dollar to be made... someone will always find a way to make it... that's just human nature. There is another saying that says "You can lead a horse to water, but you can't make it drink"... some people just don't want to take the time to read and learn, they just want their #freeMoney as quick as possible so they can move on to the next "ShitCoin"™ fork... |
|
|
|
Just one thing to add regarding this... as your Armory is not synced (and never will be without the Bitcoin Core block data to work with)... you will need to make sure that you tick the box that says "include unused (Address Pool)"... Otherwise, NONE of your private keys will show up. I'd also recommend ticking the "Address String" box as well... that way you can find the private key for the address you actually used... rather than importing ALL of them |
|
|
|
|
Show Posts
