You could set armory's data directory to your flash drive. It would have more than just the wallet file though. That would include all of the logs and databases that armory generates in addition to your wallet file.

That transaction has a dust output. A dust output is an output that is less than or equal to 0.00002730BTC. Transactions containing dust outputs are considered nonstandard and are not relayed by most nodes. Most miners will also reject those transactions.

Since it has been a few days since this transaction was broadcast, many nodes have likely forgotten about it so you can try sending the Bitcoin again. But this time make sure that there are no dust outputs. Do this by either lumping the extra dust into the fee or into the other output.

You are still syncing. You do not need to wait 1 year, that just means that the latest block it has is from 1 year and 31 weeks ago. That means that anything that came after that block (including the transaction that sent Bitcoin to your address) is not known and thus the balance is not there. All you have to do is wait for it to fully sync. It will take a few hours and up to a few days at most.

Yes. If your wallet.dat is stolen, then the thief will be able to steal all of the Bitcoin from you. It doesn't matter if you or anyone else has it open, as long as the thief sends a transaction spending the Bitcoin in your wallet before you or anyone else does, they can steal the coins. It is best to password protect the wallet with a strong password so that even if the wallet is stolen the Bitcoin cannot be stolen. Even so, if your wallet is stolen, you should move the coins out immediately.

It isn't possible to use the same blockchain data with more than one instance of bitcoin core. There are locks on the files which prevent that from being possible.

They usually are different API/RPCs but you might be able to find some that are similar.

He did? Since when?

If you want to accept incoming connections, you need to open port 8333. That helps the network more but simply running bitcoin core and having connections to the network also helps.

Wallet functionality in a pruned node was disabled because it was still untested when 0.11.0 was released. It will be enabled in 0.12.

You should still be able to broadcast transactions using a pruned node, but I don't know about getting outputs since there is no wallet and txindex is disabled with pruning.

However you can just build the master branch from github for now and get the wallet functionality and then upgrade to 0.12 whenever they release it. It should be coming out in a few weeks.

Bitcoin core supports pruning. You can set it using the -prune=<size> where <size> is the size of the blockchain you want to store. The minimum you can do is 550 Mb. Unfortunately you can't use the wallet yet but that will be fixed in 0.12

Your fees might be a little low, but the problem in those transactions are that one of the outputs in each transaction is a dust output. Dust outputs are outputs that have amounts less than or equal to 0.00002730BTC. Transactions that have dust output are considered nonstandard so they are less likely to be relayed and less likely to be mined as most nodes will reject such transactions. That is the problem with your transactions. All you can do is wait and hope they either get confirmed or are dropped by the network. If they are dropped, then you can resend them but without the dust outputs by either lumping the dust into the other output or into the fee.

No. Just look around at mining pool threads and see if they say anything about supporting nonstandard transactions. You can also PM the pool operators about it.

Of course you can use nonstandard transactions. But they are nonstandard, which means that they do not adhere to the standard rules. The vast majority of nodes will reject nonstandard transactions, which is why nonstandard transactions typically do not propagate very well. If you want to push it to the network and get the transaction confirmed, you will need to find a miner that will include nonstandard transactions into their blocks and you push it directly to them or their node.

So by those definitions Satoshi is the sole founder since he is the only creator creator of the thing we call Bitcoin. The other guys, sirius, hal, etc. are founding members since they are of the original cypherpunks group who were interested in Bitcoin and joined the project after its announcement. They are not the founders.

No there was not. There was only one entity called Satoshi Nakamoto which penned the original Bitcoin Whitepaper and wrote the code for the original v0.1 Bitcoin client. He was also the guy that mined the genesis block and did a lot of the early mining. Other people jumped on board to help in the early stages but they only joined after Satoshi wrote the whitepaper and they only contributed to code and hash power after Satoshi released the original client. Therefore they are not founders since they did not create Bitcoin themselves, they are only super early adopters.

Possibly. I don't know as I haven't checked or tried, but it may be possible to create a custom script which requires different private keys. I think the OP codes have enough options for that logic, but as I said earlier, I do not know. You will need to try this yourself.

The best way is to spend it like normal money. There aren't many places that accept Bitcoin, but some online stores take Bitcoin, and you can buy things from amazon using purse.io. AFAIK Newegg, Tigerdirect, and dell accept Bitcoin. There might be some stores in your local area that also take Bitcoin, so you should check some maps and merchant directories like coinmap.org

I don't think that is possible. It may be possible to do if address B was a p2sh address that used a custom script, but I don't think it will be possible.

There is a minimum, not at protocol level but at the node level which is set by default to 0.00005. Any fee under that is not relayed by the node.

Also, the stress tests do not send transactions with 0 fees. They always send with enough fees.

There is nothing you can do to speed up the sync, and if you think you have corrupted blocks then it would be best that you do a full resync. Also make sure that all of your software is fully up to date.

The actual bootstrap.dat is not compressed. The one you are downloading is, but it isn't the official one that was maintained by jgarzik.

There is talk on the mailing list about block compression and ways to speed up syncing, but I don't think that any of it will be coming in the next release. It either isn't ready or there isn't any particular need for it. Using the actual bootstrap.dat (not the one that you used) is not actually faster than simply letting it sync.