Rolo, don't rush yourself.  If your coins are already offline, you are in no hurry to switch.  But arguably, you are right:  you have a paper backup, what could go wrong? 

The best thing thing to do is delete the offline wallet and restore from paper backup.  It'll calm your nerves a bit, knowing that you are using the exact same wallet you'd be using if something went wrong and you had to restore again (but they are the same, I promise).  And also load the offline wallet and online wallet and generate about a dozen addresses on each.  Verify that the generated addresses are the same.  Once you see that, hopefully that that niggle will go away.

Then as extra credit, move a couple BTC to it, and transfer 0.1 BTC to yourself a couple times using the USB key.   Even though I wrote the program, it still felt a little bit like magic that it works.  But it's easy to get used to

Yeah, I noticed that today, though I haven't been following the discussion.  I noticed slush using the term "cold storage," which probably refers to some custom-scripted offline wallet solution.  I wonder if I should somehow tie in the phrase "cold storage" into the Armory description:  I assume it's the same thing...

yeah, cold=offline.

eto, will Armory's offline main wallet run on Windows Vista?

I just released version 0.55 (final).  It can be found at http://bitcoinarmory.com/index.php/get-armory.  The only difference (from RC2) is a proactive security upgrade to the message signing.  But it was something that probably couldn't be exploited, anyway, so it's not critical if you are already operating with 0.55-RC2.

I noticed recently that some of my transacations are failing to be acknowledged by Armory, but do actually end up in the blockchain.  I witnessed the same thing when I went back to 0.55-RC1, so it's clearly not a completely fresh bug.  But I'm going out of town for a week, and it appears that Armory transactions still work: you will just get an error message, followed by seeing the transaction show up in the next block.   If this really bugs you, you can go back to Armory version 0.51.  Or maybe I'm the only person seeing it...?  I will investigate further in a week!

you should be ok. from my limited testing i haven't found any serious bugs.

Sounds like there's a lot of little problems here.  Armory will probably go into offline mode of it can't find the blockchain maintained by bitcoind.  However I intended to put in a CLI option for specifying the dir holding the blockchain if it's not standard.   I don't remember if I ever implemented it,  and I'm on my phone right now not in a position to check.  But you can check yourself by going to the github project page and searchingfor "optparse" in Armory.py.   

As for the other issue,  I bet that you did not mark the wallet as your own.  Is the wallet identified on the main screen with a standard white background or with the dark blue?  Does it say "Watch-Only",  or "Offline"?  My guess is that it isn't marked as belonging to you,  and the default filter on the mainstream is set to "My Wallets. "  you can change the filter on the bottom left of the main screen to "All Wallets" which will start including "watch-only" wallets. 

To avoid this in the future,  click on the "Belongs to:" field in wallet properties and check the checbox.  The wallet will then appear with dark blue background and it's balance will be included in your main balance.

As for why it shows offline,  I'm not totally sure without more info.  My guess is that it's the lack of blockchain,  even though it's technically connected to bitcoind.

Holliday,  the primary issue is that the blockchain is not being loaded.   I think all other problems will clear up when you get that.

Also, when you import a watching-only wallet, it will default to not being yours.  This is to prevent an inexperienced user from being persuaded to import someone else's wallet and believing the money is their own.

So,  once you import the watching only wallet,  you have to go into the wallet properties and change the belongs-to field.   I thought I had that in the instructions... I will add a pop-up windows for when you import a watching-only wallet, that asks whether it is yours,  or that this step can be skipped entirely.

Since I'm not in a position to check whether the is a blkdir option, maybe someone else who doesn't mind looking at the python code could check for me and report back.   I honestly can't remember if I implemented it!  If not,  then you'll have to put your bitcoin dir back to default,  or wait a couple days for me to get access to a development system and commit a fix :-(

just looked at the code, there is no such option, you can only specify a path for the armory settings file.

i just looked into it and its like this when you have a different datadir:
no matter if the bitcoin client is running or not you end up with an armory client in offline mode, a wallet balance of "(...)" and -1 satoshi funds.
the armoryengine function for loading the blockchain already has a parameter for the path, armory is just lacking that one line in the optparse section + another line to pass the parameter along.
just tested it and it works like a charm 

Fornit, I see you're learning quickly    Unfortunately, now that I'm distributing full binaries, I cannot just push new .py files, I have to do a full recompile and re-distribution of binaries.  So it sounds like Holliday is going to have to wait.  What a great time to leave town for a week!  


Yeah, the requirement is 1+ confirmation for tx from other people, 0 confirmations for change-back-to-self outputs.  It appears that I did introduce a bug recently, and now I'm out and won't be able to attend to it for a week  Glad to hear it's still usable, at least...

PS what OS are you in that you experience the same problems?