Download Mycelium onto your phone. Use that to import the private key of your paper wallet into Mycelium so that you can spend the funds. It can scan the QR code for the private key, and if you encrypted it, it can decrypt it too provided you know the password.

Yes. That is exactly what happened.

No. That "extra spend" that you see is called change. The Bitcoin is yours and is being sent back to your wallet.

 Bitcoin works by creating and spending transaction outputs. When you receive Bitcoin, you get a transaction output which you can spend from. When you spend from that output, it must be spent from fully. Thus when you spend from that output, some of it goes to whoever you wanted the Bitcoin to go to, the rest returns to you as change. You still control that Bitcoin and your wallet handles everything in the background, which is why you don't see the change anywhere in the GUI.

Change for Bitcoin is much like change with fiat money. For example, you have a $20 bill and buy something that only costs $8. You will receive $12 as change. The same happens with Bitcoin, except that the "bills" are outputs and can have variable value.

Should be fixed now.

Read the section on "Asking miners for help" on this thread: https://bitcointalk.org/index.php?topic=1802212.0

That is impossible to know. Again, given the complexity of the web of unconfirmed transactions, it could be an extremely long time, from several days to a few weeks. It is also possible that the transaction will never confirm.

All you can do is ask miners to confirm all of the unconfirmed transactions that your transaction depends on. However, given the complexity of the web of unconfirmed transactions, I don't think many miners will be willing to help you.

The problem is that your transaction fee is too low. Read https://bitcointalk.org/index.php?topic=1802212.0 for what you can do about it.

Since you are using blockchain.info's web wallet, there is not much that you can do.

No. It is recommended that you use a wallet with dynamic fees. Do not use a fixed fee or fixed fee rate.

He probably submitted it to ViaBTC's transaction accelerator. Submitting it there (or to any other transaction accelerator service) does not guarantee that your transaction will confirm within a given amount of time. It just means that the transaction has a higher chance of being confirmed.

Your transaction spends from two unconfirmed transactions. Those two unconfirmed transactions spend from a number of other unconfirmed transactions. Your transaction cannot confirm until all of the unconfirmed transactions which it depends upon (the ones it spends from, the ones that those spend from, and so on and so forth) are also confirmed. Since you have a huge mess of unconfirmed transactions that your transaction depends on, it may be a very long time before your transaction confirms. It may be possible that your transaction will never confirm if any of the several unconfirmed transactions ever gets double spent and the double spend confirms.

You paid a fairly low transaction fee. Read https://bitcointalk.org/index.php?topic=1802212.0 for what you can do about it.

Try doing
instead. The default (without any parameters) is to have a minimum of 1 confirmation. With that one parameter, you set the minimum confirmation requirement to 0, so it should return the outputs for unconfirmed transactions.

You are going to have a problem after making the 25th transaction. Core will not allow you to have unconfirmed transaction chains of more than 25.

Try doing Help > Rescan Balance.

Interesting. You need to get it to reindex the databases. Go to the Bitcoin Core datadir and find the file named bitcoin.conf or make it if it doesn't exist. Then add the following line to it:
Then start Bitcoin Core. It will be reindexing the databases. Once it is done, go back to that file and remove that line so it doesn't reindex every time you start the program.

Rebroadcasting a transaction means that you are reminding the network that the transaction exists. Otherwise the transaction would get evicted from nodes' mempools after some time if it remained unconfirmed. It does not actually help a transaction confirm faster. Rebroadcasting just makes the transaction reach more nodes and remain in nodes' mempools.

Yes.

Only one of those transactions can ever confirm, not that one will confirm first.

Are you absolutely sure that the address is correct? Make sure that you aren't missing a character and that everything is exactly as Armory gave you.

Read https://bitcointalk.org/index.php?topic=1802212.0 for what you can do.

Since you are using blockchain.info's wallet, there is not much that you are able to do except ask miners for help.

Transactions can be rebroadcast. It possible that someone rebroadcast that transaction after it had been "forgotten" by the network.

It can confirm, but I think it is unlikely.

You could make another double spending transaction but include a much much higher transaction fee. However, since one of your transactions contains an ok transaction fee (still quite low, but way above the minimum), such a double spend may not work.



You should upgrade to Bitcoin Core 0.14.1.

Which versions of Armory and Bitcoin Core are you using? Can you also post the armory log files (armorylog.txt and dbLog.txt)?


Yes, you control that address as it is a change address.

Did you attempt to make a transaction of 0.007 BTC since April 25th?

Since you control the change address, you will at worst lose 0.007 BTC.

Yes, but I wouldn't recommend it since you already have multiple conflicting transactions.

No, not bad at all. That site uses Bitcoin Core in the background and if it receives a transaction which conflicts with another in its mempool, that conflicting transaction will be rejected. What happened here is that it received the 3rd transaction first thus it rejected and did not keep the other two transactions.

If they have a copy of your wallet file and the password, then there is nothing you can do. However, I think it is unlikely that your computer is compromised. Rather I think the issue lies in Armory doing something wrong because of multiple broadcast failures.