This feature is long dead and I'll remove all BCH signer code in the next release to boot. Therefor, I'm going to unsticky this thread.

Try the noasm .deb

Update to 0.96.5, delete the DB and start over.

The issue is more PyQt than Mac tbh. Some modules depend on OpenSSL (QtNetwork is the chief culprit), and PyQt includes everything Qt has to offer by default. Using Qt at the C++ level, you could probably avoid that kind of overzealous linkage.

Qt

You should skip these two, they complicate your setup. Let Core handle that pathing for you. Once you're setup properly, they will default to these :


**************************************
Bitcoin Core setup:


This will allow Bitcoin core to use this path for its settings. You need to customize the Core settings for your system:


Start bitcoin-qt from the shortcut and let it download the blockchain.

*******************************
Armory setup:


Same as with Core, this tells Armory where to look for its settings and wallet data. Now for the Armory specific settings:


Once Core is done downloading the chain, start ArmoryQt with the shortcut and you should be good.[/code]

Armory wasn't invoked with any of your command line arguments. I don't know why you're putting spaces everywhere, that will definitely break paths.


This stuff is just insanity. Give me the path for your Armory Data and Bitcoin Core data, I'll tell you how to setup.

ASCII is basically the western alphabet encoding. If you are using "exotic" characters such as Arabic, Chinese, Hebrew and the like, they cannot be encoded with the ASCII standard, you'd have to use UTF to represent them.

The folders you referred to are for the binary installation. The "install" I am talking about is the where on your system the Armory wallet and settings are saved. This is a different folder from the one that holds the binaries.

On Windows, it defaults to:


Where *username* is the name you have given to your user account during the Windows install. If this name uses non ASCII characters, Armory will fail to run.

You need to first confirm this is the issue, then set your Armory user folder to an ASCII only path. For that, you need to create a shortcut of ArmoryQt.exe and add "--datadir=*custompath*" in the target box, where *custompath* is whatever folder you choose.

You can search the web for "ASCII table" for the list of acceptable characters for the custom path.

Do not install Armory in a folder that has non ASCII characters.

Armory is warning that it has to unrelated UTXOs together to meet the value of your desired payment. This erodes your privacy because if you move forward with this transaction, all these UTXOs will now be related.

There is no risk of coin loss, just privacy loss. Financial privacy is significant however, don't damage if you don't need to.

What you can to go around the issue is manually select UTXOs you know are fine to mix/use for that particular payment.

Then he went full Kubernets. Never go full Kubernets!

To be fair, the only stuff Armory doesn't link to statically beside the C lib is Qt.

Update to 0.96.5 and try again.

They try to support it. None of our devs are involved though.


What version of Armory are you using?

Armory doesn't support BIP44 atm, that's in for the next version. So you'd have to input the public keys manually, Armory won't be able to generate these for you from your seed. If you want so sign those coins out of multisig script with Armory, you will have to import the underlying private keys too.

After that, you have to pick your MS script type. I suggest you pick the P2WPSH.

At any rate, addresses in your case are not useful, you need the straight up public keys. You cannot create a multisig script from addresses, as you cannot yield public keys from addresses.

In /home/jacob/.armory/, create a file named armorydb.conf. In there add this one line and save:


Try again and let me know.

Doesn't look like you told Armory where to look for your custom Bitcoin data folder.

In Files > Settings, second second section from the top, set your custom folder and try again. Make sure there are no zombie instances of ArmoryDB first.

Changes are taking place in the dev branch. A lot has changed and there's still a lot I want to add in there. The work is split with helping another project. Most of the progess with that project is shared with Armory and the code ends up in the Armory repo eventually.

The main bottleneck atm is moving from SWIG to another C++ to Python framework to allow for a shift to Py3 & Qt5. Also need to go over GUI for the new wallets. Mostly, the GUI needs to represent BIP32 wallet branches.

I dont know what that is =/

Definitely try the noasm builds.