Well I think we are getting off topic here - but just wanted to add my support to etotheipi's idea as I have also created an offline tx signing system (which has no blockchain and just does signing) and it would very much benefit by knowing the tx fee.

As I use QR codes and want to keep the information transferred offline to a minimum I think something along the lines of his suggestion would be a very good idea.

Did you mean to say "in your bitcoinBTC feature" (as in "feature length film")?

If so I will be sure to give it a prominent role.

The problem is that you cannot send the same tx whilst the old one is known to the network (any attempt to do so will simply be ignored as a "double spend" attempt) so it is not something that can very easily be handled by clients (basically you have to wait until the old tx has been "forgotten" before you could send a "replacement" tx).

A couple of times I have resorted to doing a "getrawtransaction <id>" then pasted the raw tx into https://blockchain.info/pushtx (and that has actually worked).

In this case I would be reporting a bug (those higher level RPC commands should not be like the raw tx ones).

The bitcoin-qt client will keep trying to resend the tx forever until you remove it (my advice for a tx like that would be to use pywallet to delete it then wait for a day before trying to send another tx that has an appropriate fee).

Certainly right now clients should probably all be at least including the minimal fee at the moment (I changed my bitcoin-qt's setting to 0.0005 after having several very slow and later two stuck txs).

The other problem here is simply that currently (as in the current version of) Bitcoin does not scale - so until this is better resolved then there is simply nothing else that can be done (although at least if miners included closer to the 1MB of txs per block we'd have far less backlog).

It's a bit annoying (and it would be good if there was an option to remove this *feature*) but the -000 (or -001 or other number) is the "vout" for the transaction item listed (am assuming the reason is if you send to more than one address that you end up with one transaction item for each although I haven't actually tested that).

If your transaction is not showing up on blockchain.info then it hasn't been broadcast to the network.

Your client will periodically attempt to resend it but if it needs a fee and doesn't have one (possible if your bitcoin-qt isn't up to date) then it simply won't be forwarded by any peer (and therefore will never even make it to a miner).

If this is the case then you could use "pywallet" to remove the offending transaction from your wallet or if you don't think you're up to doing that then you are probably best to ask for someone to help out.

There is no "code" transmitted via QR - just an unsigned raw tx (which you can check before signing).

So it is not a question of malicious code - there is *no code* at all.

I use an old e-book that has a built in "slideshow" function for all the photos in a directory - currently am only using it with my offline computer (to move new addresses to the online computer) but am thinking of buying another one for the online computer (as they are dirt cheap devices).

It appears they are delaying deposits until long after they are being made (and this could be being done on purpose to try and prevent a crash although I'm sure they wouldn't say so).

Exactly - I use QR codes for the CIYAM Safe and it does feel a lot safer to be completely "air-gapped".

It shows multiple numbers on the main screen (mine currently has 3).

You just need to make sure you add each new account with its secret key (can be done via QR code assuming your phone has the software).

Authenticator handles multiple accounts so should be no problem with that (and yes I have tested it with more than one website).

It just looks like the "change" was sent back to the original address (easy to do using "Coin Control" or by rolling your own "raw transaction").

There should be a setting in your Bitcoin client for a "minimum transaction fee" - I would advise setting that to at least 0.0001 and perhaps to 0.0005 to get a higher than average priority (if an even higher fee is required the client should warn you and get you to accept adding that fee before the transaction is sent).

And important to note that a "0 confirmation" tx could end up disappearing altogether despite being "valid" if it has not managed to gain sufficient priority after a certain amount of time (which generally occurs due to no fees being paid for the tx) - so I would recommend you always at the very least wait for 1 confirmation.

Your computer(s) is/are irrelevant as only "miners" are involved in constructing new blocks which are the "confirmations".

So just be patient and wait - and for smaller amounts (especially in person) I myself am normally satisfied with just one or two confirmations.

Also try not to get too excited about the price - it tends to go up and down quite a bit when you decide to get on board the "Bitcoin ride".

Yes - do this (same goes for brainwallet.org).

To download just click on the "Download ZIP" button on the right side of the page.