You spent the coins from 1M35ZN address in this transaction: https://blockchain.info/tx/e47783ef0c2cfe0bcbb942c2e778c59543d5103eec62aaf995c410c3ff7a9799It looks like the change was put in 1HQN2NyqfMWGX2wKrq8VxZfNoySSMRH3Gh That address should be in your MultiBit wallet... However if your password isn't working, it sounds like you've been hit with the MultiBit Classic bug that seems to be corrupting wallets and/or key backups... There is no known fix for this at the moment... And given that MultiBit is no longer supported, I doubt there ever will be a fix  If you can export your keys from the wallet, you might be able to rescue the coins but otherwise those coins are stuck  |
|
|
|
|
Any chance you can share how you broadcast it?
Also, it should be noted that your process might only work if you have not conducted ANY BTC spend transactions since Jul 31st.
Otherwise, Armory might not be able to find the correct inputs as they could possibly have been spent.
|
|
|
|
If Ledger and/or Trezor device that the fork is worthwhile (ie. It is actually going to survive and have value)... like they did with Bitcoin Cash and Bitcoin Gold, they'll add support to their wallets and have previously created tools that allow you to basically "click a button" and claim your fork coins. This has historically been "secure" in that it doesn't involve having to export private keys or your seed etc. However, there is no guarantee that any new fork will be supported in the future... But that just means you'll effectively have to do the same process as you would with Electrum ( export keys, import into fork wallet etc) Ledger: https://www.ledgerwallet.comTrezor: https://trezor.io |
|
|
|
|
It's a watching only wallet anyway according to that screenshot... ie. it doesn't contain any private keys... so you can't use that wallet to spend your coins anyway.
|
|
|
|
You are looking at data files on an old mac, some of which are dated from 2/10/2010 and some others are dated from 2015. That's about all we can tell you based on the very limited information you have provided... perhaps some more detail like the file names and/or file extensions and possible the folder names that they're in might make it a bit easier for us to tell you what it is that you're actually looking at  Alternatively... you can try reading this: https://multibit.org/help/v0.5/help_troubleshooting.html and this: https://multibit.org/help/v0.5/help_fileDescriptions.html |
|
|
|
All your questions got answered in your other (identical ) thread here: https://bitcointalk.org/index.php?topic=2533313.msg25829472#msg25829472 Please don't start multiple threads asking the same questions... it will make things very confusing for everybody. It also means that anyone reading these threads later won't see potentially helpful information if it is spread across multiple threads instead of all the information being in one place. I suggest you delete this thread (click the delete button on the first post) |
|
|
|
...there should have been litecoin left in there...
Litecoin?  You probably installed the wrong "Electrum"... Electrum that you get from https://electrum.org/#download supports Bitcoin ONLY! It does NOT work with ANY other cryptocurrencies. If you believe you had Litecoin stored in an Electrum wallet, you probably used Electrum-LTC from here: https://electrum-ltc.org/This is a "fork" of Electrum that works with Litecoin. Try downloading that and putting your seed into it and see if you can see your Litecoin. |
|
|
|
You can... providing the return value of the first command is compatible with the inputs required for the 2nd command. For instance... you can do: deserialize(gettransaction("TXID_HERE")) If however your first command is returning something that isn't identical to the type of input needed for the 2nd command, you'll probably need to do some "python" programming and maybe use a "for" loop or something like that to iterate over the collection of addresses or unspent coins etc... Balance of each address: for theAddress in listaddresses():
print(theAddress)
print(getaddressbalance(theAddress))
PrivateKeys of addresses with balance: for utxo in listunspent():
print(utxo["address"])
print(getprivatekeys(utxo["address"]))
NOTES: - Copy each line one at a time... otherwise weird things might happen - The spaces at the beginning of each "print" line ARE important - You'll need to press enter a couple of times to get it to run |
|
|
|
|
Are you sure that your "vout" value is correct?
Also, are you passing the TXID into the 2nd "signrawtransaction" command?
And as someone else had problems with... is your "amount_of_btg_to_move_here" set to the original amount of BTC or the amount of BTG - fee? (hint: it should be the original amount of BTC)
|
|
|
|
No. You cannot import private keys to a hardware wallet... And that would completely negate the point of using a hardware wallet. You're putting "exposed" private keys onto a secure device! If you have enough BTC to warrant owning a hardware wallet... you can afford a few satoshis in transaction fees!  |
|
|
|
But in terms of someone using electrum, which one would be easier? Or it should be either because electrum would be harder than both right?
You can actually use the Ledger Nano S and/or the Trezor WITH Electrum... Electrum allows you to import a "watching-only" version of your Ledger/Trezor wallet... it works EXACTLY the same as a "Standard" Electrum wallet, except that it contains NO private keys (for obvious security reasons). When you want to send a transaction (or sign a message), you have to have the Ledger/Trezor connected... Electrum sends the transaction to the device... you check all the details and then confirm the transaction on the device. The device will then "sign" the transaction and send it back to Electrum so that Electrum can broadcast it to the network. Your private keys NEVER leave the device. The default Ledger/Trezor wallets are "OK"... but Electrum in conjuction with a hardware wallet is AWESOME!    5. ... im sort of worried that something might go wrong with the device. If something goes wrong with the device and/or malfunctions... what happens to your bitcoin then?
You can restore to ANY BIP39/BIP44 compatible wallet like another Ledger/Trezor (you can restore a Ledger to a Trezor and a Trezor to a Ledger btw)... or even restore it in Electrum if you need to. |
|
|
|
Thanks for all of your input. I already tried --salvage and pywallet, both without success.
What exactly happened when you tried pywallet? It would be useful to know exactly what you tried, and therefore, what you didn't... just on the off-chance that someone might be able to spot a flaw in your methodology... "pywallet didn't work" doesn't really tell us much |
|
|
|
Without knowing exactly how you ended up sending to the "wrong" address... you'll never really know how you could have avoided it. You seem to think you copy/pasted an address from your Bitcoin Core, but you ended up somehow sending to 3DVKD2HVMFpU3c4cLxQonNyysZk8ZNyYm1... so either you're confused and this transaction is not what you think it is, or you pasted the wrong address. Pasting the wrong address could have been a "clipboard virus" that detects bitcoin addresses and pastes the thief's address instead of the one you wanted... or it could simply be that you already had a bitcoin address on the clipboard, didn't "copy" the one you wanted... and pasted an old address (probably unlikely as that address has only ever had the 1 deposit). Are you 100% sure that you remember the who/what/why of this "kaki" transaction? |
|
|
|
WARNING: doing this increases the potential of exposing your Ledger seed... you should seriously consider moving all your coins and then resetting the Ledger to create a new seed if you do this.You'd need to use something like https://iancoleman.io/bip39/Download a copy of it... and run it on an "offline" computer... preferably using a "live" CD/USB with networking disabled etc... The reason for this is that you need to put your Ledger seed into the BIP39 Mnemonic Code Converter this time... not just the xpub... you need the seed so you can generate your addresses AND the matching private keys. 24 word seed goes into the "BIP39 Mnemonic", click "BIP44" tab... it SHOULD show the correct addresses (and matching private keys) at the bottom. If you don't see the 1DHkYjsRSPC6aWgfVcWcxbgyyVmzUv33Y8 address, you'll need to play with the Derivation Paths to see if you can find it... maybe try clicking the BIP32 tab... select "Custom Derivation Path" and set it to m/49'/0'/0' and see if it displays there...
|
|
|
|
|
It means some of the inputs you are attempting to use, don't exist (anymore)... so they've either already been used in a transaction... or you are using the wrong inputs.
|
|
|
|
Probably nothing... unless you happen to have an Electrum 2FA wallet... or a MultiSig wallet... or a SegWit wallet... In which case, your proposed solution simply won't work |
|
|
|
thanks for the detailed explanation HCP
with regard to security of the private key, do you know if there is any way to get the compressed WIF key from the source wallet rather than through a third party site like bitaddress?
To be honest, I'm not even sure you need to worry about converting from "uncompressed" to "compressed" or not... but you can simply export the private keys in Exodus itself and it SHOULD give you the correct key... otherwise, Exodus is broken and should be fixed... In Windows you use "Ctrl+Shift+D" to show the hidden "developer" menu... then: "Exodus" -> "Developer" -> "Assets" -> "Bitcoin" -> "Export Private Keys" When I tried it just now, it gave me the address, derivation path and compressed key: 15bE423j7eWmFKED3ECqqADNMiY3H4cSq2,m/0/0,0,Kx5d2ztErw7KMp7cci5M279xsai1FneM8DG5X4MkTjd4Y7vKUHjB |
|
|
|
Importing the private key returns 'null'
"null" means that the import worked... Your wallet should now contain the address/private key that you imported. Otherwise it would have returned an error message and an error code. To get the transaction history for this address/private key, you may need to restart Bitcoin Core with the "-rescan" option, so that it rescans the blockchain for transactions relating to that address. I'm currently looking for a way to generate a private key linked to the address using my 12 words (BIP39?)
The BIP39 Mnemonic Code Converter can do that... https://iancoleman.io/bip39/ I'd recommend you download the page (right click -> save as...) and then run it on an offline computer or using a live CD/USB with the networking disabled to reduce the chances of exposing your seed to hackers/thieves. The tool itself is pretty easy to use, you just need to make sure you have the correct "Derivation Path"... which can be different in some wallets. Which wallet did the 12 words come from? |
|
|
|
|
Did you check all your change addresses? or only the receive addresses? If that balance showing at 20/10/2017 was accurate, then your BTG are still on your BTC address(es) somewhere!
|
|
|
|
|
One recommendation I will offer is that if you want to check balances, just create "watching only" wallets using xpubs and/or the public addresses... Your seeds and xprvs etc can stay safely offline and you never need to enter them until you actually want to spend.
Plus, it means you don't have to keep installing and reinstalling and deleting stuff.
|
|
|
|
|
Show Posts
