Sorry... that is my mistake for creating the confusion about the "watching wallet"... wrong terminology

What you want to do is sync the Ledger Nano S with Electrum (it is effectively a "watching wallet", but you set it up differently)... follow the instructions from Ledger here: https://ledger.groovehq.com/knowledge_base/topics/how-to-setup-electrum-nano-slash-nano-s

"File -> New/Restore -> Standard Wallet -> Use a hardware device"... It should detect your Nano S and then sync everything from it (except the private keys of course )

You should then be able to see all the transactions... and you should also be able to see your Receive and Change addresses etc.

Looks like "just under 2 hours" was the answer to your question... "Included In Blocks 477796 ( 2017-07-27 11:25:53 + 114 minutes )"

I see BTC.com mined it... did you give up waiting and use the BTC.com accelerator? Seems like AntPool and ViaBTC weren't having much luck finding a block around the time your transaction was in the mempool...

Well that's a good start Hopefully it'll sync up and all your transactions will show...

Given you're on Windows, the only thing you should need to download is the file named armory_0.96.0.4-testing_win64.exe

That is the 0.96.04 testing build for Windows (64 bit)... the .deb file is for linux

Awesome... thanks for the debug!

It was indeed choking on a multisig address... I think I have it figured out, I should have been using a different library to extract the addresses

Try this version: https://pastebin.com/bB6qS4Vi

It should hopefully no longer break on multisig script outputs... so theoretically it should run without error and find your UTXOs now... fingers crossed. Let me know how you get on.

Fairly sure you cannot use the commandline in Windows... that is a Linux/MacOS feature only.

https://bitcointalk.org/index.php?topic=1660947.0
https://bitcointalk.org/index.php?topic=152183.msg1616752#msg1616752

As far as I'm aware, command line support was not added back in to the Windows version

This forum is more focussed on the BTC Electrum... not so much the LTC fork.

You might get more help on the IRC channel: https://electrum-ltc.org/#three
or by creating an issue here: https://github.com/pooler/electrum-ltc/issues

Wait... you exported the keys from Electrum... and you're trying to sweep them into Electrum?

Anyway, you cannot "sweep" a private key unless it contains some bitcoins (as it creates an onchain transaction that will require a fee to be paid!)... so you need to figure out which of your addresses have coins in them, and sweep just those keys!

You can see which addresses have coins by going to the 'Coins' tab (NOTE: you may need to use "Wallet -> Coins", if you can't see a 'Coins' tab)

The short answer is yes.

Press the "Add key" button on the accounts page:



Scroll to the bottom and press "Advanced":



Pick your "import" method, 'Scan', 'Paste' or 'Generate' (Take note of the warning about needing to do backups!):



Your new "one off" key/address displays under "Other Accounts":

Have you:

- Checked the transaction on a block explorer instead of coinbase? Is it showing as confirmed there?
- Checked the addresses contained in the transaction... is the output address actually one of the ones in your Ledger wallet? Although given that you scanned a QR code, it shouldn't really have gone anywhere else.

It might just be a glitch in the ledger wallet app... have you tried creating a watching wallet in another app like Electrum and see if it detects your coins? If all else fails... try contacting Ledger support.

Just FYI, it will work if you are using an HD wallet... also, the "dumpwallet" command will give you everything in one go... it will dump the "extended private masterkey" and all the keys/addresses and derivation paths into a text file:


EDIT: Obviously, you will need to take necessary safety precautions... not only with the text file, but in generating it... "dumpprivkey" displays the key in the console... so it exists in memory and on screen, it will only be on disk if it gets paged out of memory... "dumpwallet" dumps it onto a file on your disk in plaintext.

This should not be done without due consideration of the implications this has on your private key security!

This is where the following comment fails:

As the two coins operate on a common history and effectively use the same technology... including the same private keys and hash algorithms... the signatures on transactions are effectively valid on BOTH networks.

A replay attack is where someone takes a transaction from BTC network, and broadcasts it on BCC network to execute the same transaction. This is usually where you send someone coins on BTC, they can then effectively execute that exact same transaction on BCC network, and get BCC from you.

To prevent this, you would normally need to execute some carefully crafted transactions in a specific sequence/timeframe... the idea being that it "splits" the coins... so they are in different "outputs" on each chain... so a transaction from BTC can no longer be sent on BCC network (and vice versa) because there is no longer that common history, so the signatures will be different.

I believe that the BCC devs have attempted to address this issue... and transactions use a different sighash algorithm which prevents transactions from one network being replayed on the other... refer: https://bitcoin.stackexchange.com/questions/56867/bitcoin-cash-replay-protection/56874#56874

It isn't directly linked... jjacob is theorising that people are cashing out their GBYTEs for BTC so that they can get more BCC on August 1st... The sell-off of GBYTE is driving the price down due to simple supply and demand economics.

No worries... Happy to help

MultiBit HD records all the transactions for your addresses in the wallet file... and groups them in various pools (SPENT, UNSPENT etc)... Basically, my script hunts through your wallet file, looking for "Unspent Transactions" and then attempts to match an output address in the transaction with one from your wallet and then outputs the matching private key.

I had another user with that same error report it on the github, but they never responded after I requested more info to try and replicate and debug.

The error is being generated in another Python library when it attempts to write out the script bytes from a transaction... I believe that this is being caused by there being a multisig (aka "3") address involved in that transaction and the library isn't able to deal with the output script for that address...

Can you look at the Transaction ("f82....") and see how many output addresses there are... I suspect there are more than just the 4 that you see, but obviously can't confirm it

As per the github issue posting, I created a slightly modified version of the script that will output some additional info: https://pastebin.com/1EUMusyR

Can you please run that and sending me the "script_bytes" data that it outputs (It isn't sensitive data, it is info that is already publicly recorded in the blockchain )... and also the TransactionID... Feel free to PM me if you want to keep the info private.

Hopefully, that will enable me to figure out what is causing the issue and fix it so the script will complete properly and you can get your keys/coins

So, if I'm reading right... when you re-installed Electrum, it didn't go through the first time install process, as it found the wallet generated last year. So, you never completed the seed generation/confirmation procedure... is that right?

Guessing you have tried your usual/casual passwords that you might have used at that time? Would you have bothered generating a strong password if you were just testing the wallet a year ago? or would you have used a simple password for testing?

And both are almost impossible to buy immediately

Although, looking at the shop on Trezor.io today... the shipping date is supposedly August 1st (and the finally have the black one listed! gah!)... compared with Ledger currently being early Sept:

At the end of the day, I went with the Ledger... because Trezor didn't have the black available for purchase at the time only white and grey (and the Amazon resellers with black were asking for 2-3x the price!!?! )... and, more importantly, the price... I could get the Ledger (including shipping) for less than the cost of just the Trezor (not including shipping)

The trade-off being that I will need to wait a month longer to actually get it


I also checked out the digital bitbox, but it seems to lack integration with the wallet(s) I use... as for the KeepKey... well, after the total mess that MultiBit HD has become since they took over, I'd never give them $$$ or trust my coins to anything they touch.

I was almost tempted to buy a "BWallet" (a chinese Trezor Clone) just to have a fool around with the hardware...

No, you need to add the argument to the END of the target line... like this:


NOTE: the first part of the target has simply scrolled off the side as the entry is so long... but it includes the FULL path to the bitcoin-qt.exe...

I'm fairly sure that the so-called "priority" system has been (or is due to be) deprecated...

refer:
https://bitcoin.org/en/release/v0.14.0#minimum-fee-rate-policies
https://bitcoin.org/en/release/v0.14.0#removal-of-priority-estimation
https://github.com/bitcoin/bitcoin/pull/9602

As I told the user here: https://bitcointalk.org/index.php?topic=2046536.msg20389628#msg20389628

You have a number of options... Have you tried "Simple Bitcoin Wallet"... or do you only have an iPhone?

Failing that, you can use my Python recovery scripts (you want to use the one called "find_unspent_multibitHD_txes.py")...

Or, if you're not able to use the python scripts, you can follow the steps described in the other post to get your addresses/private keys from the BIP39 page that LoyceV linked (don't forget to check your change addresses for coins!)

Who said this and/or where did you see this claim? In any case, it is rubbish...

If a fork occurs, as long as there are transactions that assign value to your private keys recorded on the blockchain in any of the blocks prior to the fork, you are good to go...

I'm not sure why you would want move to a non-HD wallet, but iff you're switching to another app that doesn't use seeds... you can very easily export your private keys from Electrum. You don't need to be running the latest version, or for the Electrum network to be running to do this.

It is also possible to make a couple of minor modification to the BIP39 Mnemonic Code Converter webpage (https://iancoleman.github.io/bip39/) and it will convert the Electrum mnemonic into addresses and private keys. Basically, I just disabled the phrase validation (it always returns true) and changed the default Passphrase from "mnemonic" to "electrum"... the page then outputs the same addresses/keys as generated by Electrum