I beginning to wonder if you have been hit with the MultiBit wallet corruption issues that a couple of other users have had...

Either that, or you've been hacked and don't actually have any bitcoins left... have you actually checked your addresses on a block explorer like blockchain.info to see if they still contain coins?

Also, check your PMs...

That is a "one off" charge. By default, TrustedCoin add a small 0.0005 BTC fee to each transaction you make to use their 2FA service. This is NOT a standard bitcoin transaction fee. It is a service fee charge by TrustedCoin. They give you the option to "pre pay" this service fee and get a discount... which makes it only 0.0001 BTC per transaction, if you pre buy 100 transaction credits... for a total of 0.01 BTC.

This means your next 99 transactions using the TrustedCoin 2FA service have already been paid for, so you won't get these service charges for the next 99 transactions you make.

Unfortunately, it is too late to assist with reducing your fees. You seem to have signed up and paid for a service that you don't really understand how it works or how much it costs.

You need to contact the owners of the bitcoin ATM and ask for a refund. It is highly unlikely that your transaction will ever confirm. It has several unconfirmed parents, one of which has 0 BTC as a fee... that transaction has about a 0% chance of ever confirming

https://blockchain.info/tx/baf14088eae660c01cc89a613ed2fafe84c05c46809ccf94b9f69c822b32f4c8

You need to contact the ATM owners and demand that they refund or fix this.

You won't be able to find the keys themselves. A "sweep" generates a transaction that sends from the private key you're sweeping, to a different key (generally one that is contained within your Electrum wallet)

From your Electrum history, you would only be able to see the transaction that shows the coins being sent from the old address to your new address. The old keys themselves are not saved.

The keys would only be kept if you did an "import"

You're using a 2FA Electrum wallet aren't you? You have an icon like this:


If you are, I think I know what has happened. You have created a 2FA wallet, and have just purchased 100 transaction credits from TrustedCoin... that is the 0.01 BTC payment from this transaction: https://blockchain.info/tx/868025e5f2149c8f7e86779e0269d2570f0b1fc3b7560475ee3acb8fec9a503a

that goes to the address: 1NqmwTW3CVyxWTTLaPfejSJisTnxZf5tUp

Another user did this recently... it is an easy mistake to make with the 2FA wallets, once you click the "BUY" button, if you don't clear the transaction and start again, you're going to end up sending 0.01 to TrustedCoin. If you click the TrustedCoin icon, it will probably tell you that you now have 99 Transaction Credits remaining.

This probably explains why Genesis mining only got the 0.000019 BTC, as that was all that was left after TrustedCoin got their 0.01

Also, it is normal for the address to change... the wallet does this after an address is "used" to help prevent address re-use. Address re-use reduces privacy... so it is generally recommended practice to try and minimise address re-use.

DO NOT send any money to this person... until the transaction is confirmed. It has multiple unconfirmed parent transactions which originate from a ridiculous "bitcoin doubler" scam that a user here (amaclin) setup... Those transactions will NEVER confirm and you will NEVER get those bitcoins... DO NOT send any money... and I would suggest that you do not do any further business with that person.

Fees are based on the "size" of a transaction. The size of a transaction is determined as follows:

(Number of Inputs * 148 bytes) + (Number of Outputs * 34 bytes) + 10 bytes

[Note: this is assuming compressed keys, for old uncompressed keys it is (Number of Inputs * 180 bytes) + (Number of Outputs * 34 bytes) + 10 bytes]

Notice, that it is based on the number of inputs... NOT the number of addresses... you can have 10 inputs from 1 address or 1 input from 10 addresses... it will still work out to be 10 inputs and the transaction size will stay the same. If you have more inputs, the size is increased and so is the fee.

If I'm reading this correctly... you transferred all your coins to one address... and then imported that private key into Electrum? If you did this, then when you attempt to send coins, you will have only 1 input... as all your coins got "merged" into one Unspent Transaction Output (aka UTXO) so the transaction size is smaller and the fee is less.

If you then receive another 10 different payments to that same address, you'll find that if you attempt to send all your coins somewhere else, you will be faced with high fees again, because you would have 11 inputs and your transaction size would be increased again... and the fee would go up.

Ahhh OK... so that is specific to the Trezor (and possibly other hardware wallets with screens)... I know the latest Ledger Nano S has a screen, but I'm not sure if it uses the same method for seed generation. The earlier Ledger Nano had no screen.

I guess that is definitely something to consider when looking at purchasing a hardware wallet!

I would be inclined to believe that the OP has been infected with Malware or their system has been compromised in some way... someone has access to the private key(s) for that address and were obviously monitoring the address for activity.

Upon seeing the large deposit to that address, they've then broadcast a transaction sending it own to their own address using a 7000+ sat/byte fee to guarantee it got mined in the next block.

Blockchain.info is showing that there was an attempted double spend, so I'm not sure if the OP had tried to rescue the coins, or there were multiple hackers trying to steal it... it's impossible to see as one of the transactions is no longer visible after the 7000 sat/byte fee got confirmed.

That address has now received 0.04066727 BTC in transaction: https://blockchain.info/tx/16dfa89f2ebe7cffa476b587e786f33db186f69021303319d2af279909ecf019

It looks like a giant "Pay To Many" transaction, so I assume that Paymium were just batching up a number of transactions before sending the coins out. In the future, you should always contact the Sender to find out why coins have not been sent, especially when it is a commercial service that you're purchasing from.

I'm still not entirely what the use case is here... Why would you be wanting to automatically generate a receive address from another app?

Would you not be more likely to be wanting to make a payment from another app? So you click the "pay now" link (ie. a bitcoin: URI with address to send to and the amount) and your wallet opens up and creates a transaction ready to be sent.

But I can't quite get my head around wanting to get a receive address while I'm in another app... and needing that app to be able to communicate with my wallet in a programmatic way...

What's wrong with MultiBit? It's very old and outdated and is no longer maintained. In addition the fee system is problematic as it does not allow for fees higher than 0.0005 BTC/kB (around 50 sats/byte) which can prove very problematic when fees are 300+ sats/byte

Even MultiBit HD seems to be no longer maintained. It has some serious problems with the "password did not unlock the wallet" issue which has been waiting for a fix since April!!?! And I suspect this issue can also affect MultiBit classic, and that might be the reason you get the "null" error, but you'd have to post the error logs to be certain. If you do want to post logs, please use pastebin.com

I'm still not sure why you are so adverse to the whole "Seed" concept? It is a far more reliable backup method being able to recreate your entire HD wallet from a seed phrase than trying to manage backups of digital files and/or "random" private keys and remembering to do so whenever you generate a new address. If you receive coins to a new address, forget to backup your keys/wallet... and your system dies... those coins are gone. With and HD Wallet (ie. using the seed)... all you need is the seed and all your addresses can be recovered at any time.

Well obviously you have to import unencrypted keys. There is no "standard" that is used for encrypting keys, so there is no way for any given wallet to know how a key has been encrypted by some other program and how it should go about unencrypting it.

If you're worried about creating unencrypted key files... then do it in an "offline" environment like a virtual machine using Virtual Box... or turn off all the networking features of your PC while you generate the keys and import them into Electrum... ensuring your set a wallet password and make sure the "Encrypt File" box is checked.

Actually, I did miss it... that's what you get for looking at messages in the middle of a 12hr shift at 0400 hrs!

I found the Derivation Path from Google I found a a stackexchange thread regarding BIP32 derivation path for electrum. So, I tested it with the BIP39 page and confirmed that the m/0 path worked for me...

Note that I'm not sure if this is the Derivation Path for standard Electrum HD wallets, or if it is just for the MultiSig "addresses" being generated from a MultiSig Root Key... which in this case, is the 2-of-3 xprv's that we've generated by restoring the 2FA wallet.

so you put them into electrum as:

Which address are your coins in? Is it shown in that screenshot? You've checked on a block explorer that this addresses definitely contains your coins? Is it under the "Receiving" section or "Change" section?

You don't have THAT many addresses... but just out of curiousity... I'm wondering if maybe the "3" address that you have that holds your coins is one of your "Change addresses"?? If it is under the "Change" section (don't forget to look in the the "used" section)... you will need to use the Derivation Path: m/1

Did you make sure you entered the public keys in the correct order when you were generating the redeem script? did the "3" address that Electrum displayed with the redeem script actually match the "3" address that you are trying to use to claim from?

if you didn't get the order right, your redeem script (and "1" addresses) will be wrong.

How many addresses are in your 2FA wallet?

Hey guys... I have posted instructions in the other thread on how you can (might?) be able to sign a message from 2 of 3 addresses so that you can claim Lumens...

Please note that the method is UNTESTED, as I didn't have any coins in a 2FA MultiSig address when the Lumens snapshot was taken, so the claim form won't let me try and sign a message etc.

I have posted instructions in the other thread on how you can (might?) be able to sign a message from 2 of 3 addresses so that you can claim Lumens...

Please note that the method is UNTESTED, as I didn't have any coins in a 2FA MultiSig address when the Lumens snapshot was taken, so the claim form won't let me try and sign a message etc.

Ok... I *think* I might have this all figured out... I can't test it, as I don't have any coins in a MultiSig address, so the Lumens claim form won't let me get to the message signing part. So, this method is 100% UNTESTED!

NOTE: Please consider the risks of potentially "exposing" your xprv's... you should run offline copies of all websites, and run them using non-networked Virtual Machines or air gapped PCs or "Live" distro's if possible. I will not be held accountable for any loss of coins should you choose to follow these instructions!

HCP's extremely complicated 12 Step Method for claiming Lumens from an Electrum 2FA MultiSig Address

Step 1. Before you start, create offline versions of:
https://coinb.in/#verify
https://iancoleman.github.io/bip39/

Step 2. Retrieve your redeem script. This can be achieved following the previous instructions here: https://bitcointalk.org/index.php?topic=1989369.msg19830190#msg19830190

Step 3. Once you have your redeem script, you can identify the P2PKH (aka "1") addresses that you need to sign your message with by using the following site: https://coinb.in/#verify  Again, you should really download an offline copy (link provided at the bottom of the website!)


Step 4. "Restore" your Electrum 2FA wallet ("File" -> "New/Restore" -> Call it "restored2FA" and click "Next" -> "Wallet with two-factor authentication" -> "I already have a seed" -> [Enter your seed] and click "Next" -> "Disable" -> Don't enter a password and click "Next" WARNING: This creates an unencrypted wallet that has your xprv in PLAINTEXT hence the warnings about doing this OFFLINE!!!

Step 5. Find your "restored2FA" wallet file (%appdata%\Electrum\wallets) and open it in the Text editor of your choice. You should find sections labelled "x1/" and "x2/" that contain your two xprv "rootKeys":


Step 6. Using your offline copy of https://iancoleman.github.io/bip39/  - Put the "x1/" xprv into the "BIP32 Root Key" section (leave mnemonic empty). Select "BIP32" under Derivation Path. Set "Client" to "Custom Derivation" and set the Derivation Path to "m/0":

NOTE: if your original "3" address was a "Change" address (check the address tab in Electrum), you need to use "m/1"



Step 7. Hunt through the list of generated addresses until you find one that matches one of the "1" addresses generated in Step 3 (The PubKey should also match one of the PubKeys used to generate your redeem script in Step 2):


Congratulations, you now have the private key for one of your 3 "MultiSig" addresses.

Step 8. Repeat Steps 6 and 7 using the "x2/" xprv... you now have 2 of your 3 private keys!

Step 9. Import those private keys into a "standard" Electrum wallet ("File" -> "New/Restore" -> "Standard Wallet" -> "Use public or private keys" -> Copy/Paste the private keys and click "Next"... and use them to sign the Stellar/Lumens verification message as required.

Step 10. Make sure you have deleted the unencrypted "restored2FA" wallet. or alternatively, move all your coins out of your 2FA wallet as you should probably consider it compromised.

Step 11. Enjoy your Lumens

(Optional) Step 12. Consider a tip if this actually works!

---

As an alternative to using the https://iancoleman.github.io/bip39/ website, you can just create a new Electrum wallet, and import the xprv: "File" -> "New/Restore" -> "Standard Wallet" -> "Use public or private keys" -> Copy/Paste the "x1/" xprv and click "Next". Your wallet should generate the required address. Check the "address" tab, you may need to select "Wallet" -> "Addresses" if it is not visible:


You can then right click this and "Sign/Verify Message"... you will need to then "restore" another wallet using the "x2/" xpriv, and sign the message using the 2nd required address.

Personally, I think I prefer the BIP39 website method as it creates only one wallet that has both the private keys for signing the message.

You're confusing transactions and messages. The OP is wanting to sign a message... mostly likely to prove ownership of the address for some reason (ICO payout maybe?).

Glad that you got it working... so just to clarify, you had to update the ledger firmware and then install the new chrome wallet app and that allows you to choose and address to sign a message with? I'm a little confused about the issue you had tho... you're saying that the ledger wallet generates two signature lines? Can you provide a screenshot?

Probably not... most online services have a minimum deposit amount, usually around the 0.001 region... anything less than that will be considered a "donation"

So be careful that you don't lose any coins attempting to send dust payments to exchanges etc.

Where are you getting these inputs from? Fauceting? Cloud mining? Can you not set the minimum payout amount to 0.01 or higher? That way you won't get as many UTXOs and your transaction sizes and fees won't be made unnecessarily large.

Poloniex has this to say about minimum deposit amounts:

So maybe your consolidation plan will work... but bear in mind that you have no control of the fees they choose to send your transaction out with...

No, you can't simply export your wallet to bitcoin core.... but if you want to move all your coins to Bitcoin Core, and minimise fees then you can import your seed to Electrum (using the BIP39 seed option during seed input)... then send all your coins to your Bitcoin Core wallet using a "manual" fee... set it to at least 10 sats/byte (or 0.0001 BTC/kB as Electrum uses)... and then use the ViaBTC TX accelerator to push it through.

This should enable you to move all your coins without incurring a large fee, but it does have a risk if the accelerator fails to work that all your coins could get "stuck" while you wait for the transaction to confirm.

If the seed is never "shown" to any computer, how do you get the seed in the first place? The hardware wallet has to be connected to the computer... and the seed has to be displayed/output on the computer so you can write it down doesn't it?

At which time, malware that takes stealth screenshots or does desktop video recording could capture your seed right?