the outgoing transaction is for 0.000016 not 0.00001. those 0.00001 transactions are incoming ones.

He needs 2 out of 3 xprivs or 2 out of 3 address specific private keys since it's a multisig wallet.

Best option is to contact trusted coin as you said. If he controls the email he used to create the wallet I'm sure he can get them to reset 2fa for him.

electrum tends to slow down after a few thousand addresses so you'll have to rotate wallets every so often. also use addrequest instead with the --force switch.  see `electrum help addrequest` . you can specify any amount to addrequest. it doesn't have any effect on how much people can send you.

eth would have a different coin type code than bitcoin so the derivation path will be different. find out what derivation path is used there. see bip44 for more details: https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki#Coin_type

electrum getfeerate --fee_method eta

Who said anything about recovering the private keys from the address? OP makes no mention of any such thing and neither do I. He says he's being asked for the hash of the address. Sounds like they want the hash160 which they can recover from the address itself.

Sometimes when you are trying to bruteforce a wallet you want public keys, addresses or extended public keys relevant to the user. This way you have something to check against. This is my best guess as to why they would want the hash160 of the public key.

Use the option in the file menu to backup your wallet.dat file. If it says HD in the bottom right corner of the bitcoin qt window you only need to backup the wallet file once. If it doesn't then you need to back it up every 90 or so spending transactions.

If you don't have a GUI then see whether getwalletinfo says you have an hdseedid or not and act accordingly: https://bitcoin.org/en/developer-reference#getwalletinfo

It tells you the fee per kb in satoshis. You then find out the size of your transaction and set a fee accordingly.

If you do `electrum help getfeerate` it displays some useful info: http://termbin.com/7d62

You can also see the code here: https://github.com/spesmilo/electrum/blob/3.2.3/electrum/commands.py#L660

The options for fee method are eta, mempool or static. Not sure how the static fee is set.

Another thing I found is that if you set the fee estimation option under tools > preferences > fees tab to mempool you don't have to supply a fee when using `electrum payto`. Just the destination address and amount are sufficient. It sets a suitable dynamic fee itself.

give them the address and let them figure it out. if they can't then they won't be able to recover your wallet either.

Right click on the transaction in the history tab where it says 'local' and click on remove from the menu that appears. Then try to create a new transaction again via the send tab.

As for the unconfirmed transaction if it shows up on the history tab you can increase the fee. Note that you don't have to do this if you intend to spend these coins straight away. Spending these coins will confirm the parent unconfirmed transaction as well.

If electrum won't let you spend coins from an unconfirmed transaction go to tools menu  > transactions tab and uncheck spend only confirmed coins.

The reason you can't lookup addresses on the blockchain is because most block explorers don't support bc1 addresses yet. smartbit.com.au is one that does

your coins are in both wallets since they were both generated from the same seed. just use the 3.2.3 wallet from now on.

you will have problems because they changed the unsigned tx format in recent versions:

https://github.com/spesmilo/electrum/blob/master/RELEASE-NOTES#L48

The flash memory in microSD cards isn't designed to sustain so many write operations. It'll wear out quickly. You're better of buying an SSD and using that.

There is no registering of private keys or addresses on the blockchain. That is just not how bitcoin works.

- If you're looking to import the private keys into different wallet software NOW then <some key> is what you want to import/sweep. You can ignore the rest.

- If you're looking to save this dump file for import years later then just don't. Instead use the backup wallet file option in the file menu of bitcoin core.

Yep.


No you need the private key behind that public key to generate a valid sig. As far as we know only thomas has that and he hasn't been hacked. So if you trust him not to include malware and not to get hacked you can use this software. Alternatively go through the code line by line so that you don't have to trust anyone!


Nope. Always compare the long fingerprint as above and not the shortened one (0x7F9470E6) because it may be possible to create another key pair with the same short fingerprint.

It's not possible to test all possible seeds. The numbers involved are too large. However, hash functions are involved so if by some miracle you are able to test all seeds it's possible that there could be a collision like that.


You can do this over the command line with the make_seed option. The command line is only available to linux and macosx users. Here's how you would do it:


The above will generate a spanish language seed. Do `electrum help make_seed` for more information. Also mnemonic.py lists the language codes you can use.

If you don't have access to the command line you could try changing the language in your operating system's settings before running electrum. Electrum must be picking up the default language based on the regional settings set there.


The more places you use your seed the greater the chance of being robbed. The teams behind altcoin clients are less reputable than the bitcoin client team so I wouldn't recommend it.

Hardware wallets connected to an online PC do not count as being offline. They do provide some protection against malware though since they can only run software signed by the vendor and by design they are not supposed to reveal the seed or private keys to the PC.

No you sent to a single sig address not a 2fa address. The address you sent to begins with 1 right? The addresses in your 2fa wallet are p2sh ones that begin with 3. You need to follow the instructions in that guide. You can do 1-3 offline. From 4 onwards it would be easier to create the wallet with the xprv on your online device and then transfer the coins using that to a new wallet.

If you don't want to do 4 onwards online you can do it all on the offline device. However, to spend the coins on the online watch-only wallet create an unsigned transaction on the send tab, click preview and then click export to save it to a removable drive, carry that to the offline system, open the single sig wallet (the one created with the xprv from the 2fa wallet), load it via tools > load transaction > from file, click sign to sign it, export the signed transaction to a file on the removable drive, carry the signed transaction to the online device, load the signed transaction via tools > load transaction > from file and click broadcast.

Some people like to be able to view their wallet from multiple devices. A watch only version of your wallet lets you do that without risking any of the co-signer xprivs.


If you prefer that then go for it.

Just so we are clear the coins you sent from coinbase are not in your 2fa wallet. The watch only wallet corresponds to a single sig wallet and not a multisig 2fa wallet. You need to follow that guide in the first link i posted above in order to get access to your coins. You can then send them to a new standard wallet if you like.