Which dialog is this happening in?


I'll push a new testing build for 0.96.1 on Sunday.

1) Run expert mode

2) Make sure checkboxes like "hide unused" are unchecked. The offline machine does not know that these addresses are in use or not if you never signed a spending tx from them.

3) If the list is still empty, click "Receive" to reveal new addresses. While the wallet maintains a lookup of the address chain, it won't just display addresses that have never been requested (whether they are used after being requested or not).

That's if you're just an offline wallet and never setup the online part. Other, go through the steps to get a WO wallet sync'ed to the network.

Click the "Receive Bitcoin" button to reveal new keys. The code won't just spit out keys that are in the lookup but were never requested.

There is really no "quick and dirty" reply to this question because of all of the implications that come with contentious forks.

The reply to your question could be broken down this way:

1) Can I create and sign transactions with Armory post fork?

Yes. If you control the private keys, you can sign anything you want. Armory has no mechanism to lock you away from your wallets arbitrarily. It won't hold your hand either in this matter.

2) Do I need to upgrade my software to use my coins post fork?

You need to run at least 0.95 to operate on the SegWit chain, as previous databases will choke on SegWit blocks. You do not need to upgrade to run on the legacy chain.

3) Do I need to upgrade my software to create SegWit transactions?

You need to run 0.96+ to create SegWit transactions, both on the online and offline side. If you do not want to create SW transactions, refer to 2).

4) Do I have to migrate my wallets to use Armory post fork?

No. Regardless of what version you use and what side of the chain you want to operate on, you do not need to change anything to your wallets nor backups.

5) Which side of the fork will Armory operate on?

The one you make it operate on. Armory needs a node to run, it does not care what fork the node runs on as long as it's close enough to Core's own handling of blockchain data.

6) What are the risks to spending coins post fork?

You want to read this, written during the BU fork threat:

https://btcarmory.com/armory-and-hard-forks/

The same principles apply.

7) What's the safest course of action?

Basically, be patient. Prepare pre fork if you need to sell BTC for your living expenses, then just let the 2 sides of the fork battle it out until a clear winner emerges, then resume normal operations. If the forking does not settle quickly (takes over a couple weeks), there may a come a time when you'll have to pick a side.

In this case, inform yourself on both sides and choose accordingly.

You are most likely trying to import a compressed private key, which Armory does not support. If what you want to achieve is to actually the balance of an Electrum wallet to an Armory wallet, you are better off just sending the coins from Electrum to your Armory address, because this is exactly what sweeping does in Armory: it scans the keys and creates a transaction that sweeps all fund into an Armory wallet.

Yes

It can't find the first block in your blockchain data.

Post your log files.

You can get Core to check its own chain over. As for Armory, you have to rebuild the DB from scratch.

Armory does not work with pruned nodes.

Start bitcoinqt with -disablewallet and use the second GUI tab

Is D: a USB drive?

The chaincode is wallet specific. Public member means it is treated as publicly exposed data in the wallet. It is never encrypted and carried around in WO wallets. To put this in a realistic scenario, an attacker with your WO wallet and a single private key on the derivation chain can reveal the entire private chain.

If you are updating from 0.94, you will need to delete your Armory database as it is not compatible with 0.95+. The installer just replace the binaries. Uninstalling does not wipe the user data (db/wallets/settings), so you will have to wipe the db data manually.


No difference with 0.95. 0.96 default settings are backwards compatible with up to 0.92. If you use the new scripts types (deviate from the defaults), you will need a 0.96+ signer.


This stuff will always be supported.

https://github.com/goatpig/BitcoinArmory/blob/master/cppForSwig/EncryptionUtils.cpp#L825

Code is self explanatory. Public key N+1 is derived from (public key N) x Chaincode. The chaincode is a public member. If you want an ELI5, search this forum, there are a few written.

Post armorylog.txt

cookie auth replaces rpclogin/password

You need server=1 to enable the RPC though.

Corrupt blockchain issue. You need to redownload the chain.

Delete your Armory database (C:\Users\Donnyman\AppData\Roaming/Armory/databases) and try again.

Worst case scenario, the AV actually nuked blockchain data and you need to redownload it, since it happened early, in the 200k.