I assume you mean 0.92.3... You should definitely upgrade to 0.93.x and see if it helps, since the whole backend has been overhauled in that version. It'll force a rescan, but 0.93 is much faster anyway, an it's also compatible with Core 0.10 (which syncs much faster too).

Is there any reason you don't build a 32-bit offline-only version of Armory on Windows?? I think considering people usually use old PC's for offline wallets this might make sense, and the security argument isn't very relevant if the PC is not even connected to the network (the biggest attack factor IMHO is autorun, and Armory could have an option to disable it; that would be neat!)

On a similar topic, I installed the 32-bit Linux version on a 32-bit laptop after upgrading my bitcoin "safe" to Wheezy (downloaded using the secure downloader and double-verified using existing sigs on the offline laptop)... Works great, but now I'm looking at the download page and I see no 32 bit version there. As expected s/64/32/ on the download link works but why is it not even showing up there?

Ok, this last one is really getting me offtopic, but talking about offline features, what I'd like to see is an intuitive way to launch the install on the offline wallet... maybe a signed package that you can extract with Armory? The reason is simple: when I download Armory from the online computer, even with the secure downloaded, how can I trust Armory hasn't been infected with malware so it downloads and validate a malicious version? And if the offline computer is truly offline, then it's still my only choice -- well at least for the common user that never used gpg command-line

Regards,

Thomas

I've tried it yesterday and indeed mSIGNA is definitely on the advanced side. Unless you've fully read BIP32 and *understands* it then you'll easily get lost as soon as you diverge form the online instructions. BIP32 is a very powerful wallet format and this application should be targeted at brokers and eCommerce developers.

For the average joe that wants more security, what I would recommend is either an hardware wallet such as the Trezor or an offline wallet using Armory (either use an old laptop with wireless disabled - ideally a fresh install - or a rasberrypi). The offline side needs very little resources.

As with any other wallet, make sure you create a backup, destroy your wallet and *restore it* before you even put any bitcoins in it, and keep the paper backup somewhere safe like a safe-deposit box.

Just for the heads up, it *is* possible to send bitcoins to a wallet you haven't fully set up yet although if you got a public address there must be a private one too (make sure it's saved and backed up asap). Since a simple transaction merely sends coins to a public key *hash* you can even create a public key out of thin air by hashing random data without ever having a private key for it (you'll obviously lose these bitcoins).

On the other hand, a bictoin pubkey uses a special encoding that includes verification data. The goals of the public key encoding are multiple:

1. Shorten the length of the key representation by using letters and digits
2. Avoid look-alike letters (O & 0, I & l...)
3. Avoid typing mistakes by validating key using 4 extra bytes
4. Differentiate between address types

#1 & 2 are done using bitcoin-specific Base58 encoding (similar in spirit to Base64 but using a custom table and without the letters above)

#3 & 4 are done with special algorithm designed specifically for Bitcoin - see https://en.bitcoin.it/wiki/Base58Check_encoding#Creating_a_Base58Check_string

Because of all this it is not easy to type random bitcoin addresses in the normal form, however any sha256 hash (and by extension anything 32 bytes) can be transformed into a well-formed bitcoin address.

Just posting... I'm curious how that newb restriction actually helps...

dERMOTH