0.96.2 is out. The use of SegWit has been enabled on the mainnet starting this release. SegWit availability is checked through your node's WITNESS service bit, i.e. connecting Armory to a node that does not advertise this bit will disable SW in the GUI.Changes:Binaries:Note:OSX and offline RPi packages are on the way.

== Added == - Enabled SegWit on the mainnet. Running against a node with WITNESS service bit flagged will allow you to create SegWit addresses. - Improved DB scan speed (~80% faster) and stability. - Reduced DB memory usage (~20% less). - Supernode DB mode. This isn't optimized for consumer grade computers, use at your own risk. - The MAX button in the Send dialog has been changed to a checkbox, effect is now binding. Maximum value will be calculated on any change. - You can now create OP_RETURN outputs from the Send dialog. This feature is only available in Expert mode. - You can now pick the signer of your choosing in Expert mode. - Added BCH on top of the legacy and 0.96 C++ signer. - Improved verbose on ZC broadcast failure. == Fixed == - Fixed benchmark timers on POSIX systems. - Fixed several Linux build configure bugs. - Properly update RPC state in GUI on connect/disconnect events. - Various zero conf bugs. - Scan progress notification. - Properly display comments for non legacy addresses. - Digital exports will be saved under the proper file extention in Windows. == Removed == - Removed armoryd from the repository. armoryd was moved to its own repository (https://github.com/goatpig/armoryd)

There are several different types of Bitcoin clients. The most secure are full nodes like Bitcoin Core, but full nodes are more resource-heavy, and they must do a lengthy initial syncing process. As a result, lightweight clients with somewhat less security are commonly used.

I'm running Ubuntu 16.04. The debs will not install (my GCC version does not match either) and the build steps just simply fail. I'm probably missing something here...All this as root:git clone https://github.com/goatpig/BitcoinArmory.git cd BitcoinArmorygit checkout v0.96.2git tag -v v0.96.2makeOn make I get:make: *** No targets specified and no makefile found. Stop.On the git tag command I get:object 95dc55907f26cf79fdec7f8efa4228f7efd696cctype committag v0.96.2tagger goatpig < moothecowlord@gmail.com > 1504047291 +0200v0.96.2gpg: Signature made Tue 29 Aug 2017 04:54:51 PM MDT using RSA key ID 4922589Agpg: Can't check signature: public key not founderror: could not verify the tag 'v0.96.2'(Previously I tried to add a key in Kleopatra but that didn't seem to help...)Any ideas? Can't access my bitcoin since segwit.

That would mean a lot work to shoot your self in the foot.Probably harder than sending coins to a wrong address...Most users will probably just click receive funds and don't change the address type at all and if they do a warning would be enough.Probably also most newbies will run a current bitcoin node on top with segwit enabled.I guess users who do non standard stuff know what they do as well.The worst what could happen is that someone generates a Segwit address and is running armory on top of Bitcoin Cash and sending those to his segwit address.But that need a lot intention to mess things up.

Is there a way to export pre generated addresses from watch only wallets? I can't pre generate segwit addresses yet on the offline device and I can't find an export function to the pre generated addresses in the watch-only wallets... Edit: I removed the checks my self in the source and now I'm able to pre generate addresses on my offline device.