Topic: Armory 0.96.4 release - page 2. (Read 728 times)

All right, I was expecting armory to read bitcoin.conf from my home directory but it reads it only from the Bitcoin Home Dir. Now I have everything working great.

Thanks for your help!

You can't do that, it tries to read it from your bitcoin.conf on its own. You'd have to hardcode your log/pass in code and build it yourself.

RPC is configured with rpcuser and rpcpassword and working (at least with bitcoin-cli and lightningd). I see that ArmoryDB is running with "--cookie" but I can't use this as bitcoind is running with its own user with very limited permissions and the cookie file can't be read by other users.

Where can I tell armory the right rpcuser and rpcpassword?

You have to setup the RPC. Also, post armorylog.txt.

I have a couple of issues:

- Fee estimation is not working, the slider is grayed out and I have to set the fee manually.
- When trying to bump the fee of a RBF transaction, an empty small window pops up.

I am running my own bitcoind (0.16.1), armory succesfully syncs and "Connected (X blocks)" is displayed in purple.
Seeing the changelog I am thinking that I have something wrong in my configuration but no clue what can it be.

Win64 version still defaults to incorrect install directory...

If you don't intend to use segwit addresses any time soon, then it's probably not worth changing. It sounds as if the transaction signing functionality in Armory will be getting additional capabilities in the next version too (as there will be a new wallet format).

Thnx,  it clarifies things.  I'm still not using Segwit addresses,  but there's no harm in planning ahead, right?   Hope all goes well if 0.96.4 will be installed a top of 0.96.3 i.e.  without uninstall of previous version.

I think 0.96.4 is needed to fix a tx signing bug when spending segwit outputs:


So having >= 0.96.4 as your offline signing software is necessary if you're using Segwit addresses.

I suspect that has more to do with Qt 4 than anything else. Qt 4 is unsupported at this point and is basically held together with gum as operating systems upgrade. Fingers crossed that this will be the year when Armory jumps from Python 2 and Qt4 to Python 3 and Qt 5. (The two are basically interconnected for Armory's purposes.) Work is ongoing but there aren't enough people helping out, unfortunately.

leave it

Hi, goatpig, I have upgraded my watch-only  wallet to the latest 0.96.4 release. But should I upgrade my cold one (v. 0.96.3) to be on the safe side (or I can leave it as it is)?

minor display bug in Ubuntu 16.04 LTS:

https://imgur.com/Ei51l6i

Need to see your armorylog.txt

RBF gets much further than it used to, but I still can't RBF a transaction from a Watch-only wallet.

I get to the Sending from Wallet: / Enter Recipients: screen, and I can enter my details and click Continue, click Yes on the Insufficient Fee warning, and nothing happens - I'm back at the Wallet/Recipients screen, when I think I should be looking at the Review Offline Transaction screen to save it to my USB flash drive...

If I enter a huge fee to skip the Insufficient Fee warning, the Continue button just doesn't do anything - I can click it all day long.

No

Hi, I am intended to buy Lefger Nano S. Is Armory backward compatible with that wallet? In other words, will Armory's  private+public keys  be equal to those of Ledger   if I put into Armory the seed from Lefger Nano S?

Bunch of stuff going on in the dev branch.

A lot of these changes are a result of a partnership I hold with an upcoming exchange. The most significant parts are:

1) Optimizing the DB to operate a c10k capable supernode (basically a chain explorer service).

2) In that same vain, swapping the server interface from FCGI to websockets.

3) Since I don't like the CA model SSL hinges upon, I'm having droark implement BIP151 for the client/server encryption layer. This is done in consultation with Core, and we're hoping the code will be accepted into Core when they're ready to work on this layer.

From the user perspective, these changes mostly result in better stability. BIP151 and websockets will improve privacy and quality of life for the few users who use remote DBs. For the stuff that's more immediately relevant to individual users there's:

1) new wallet format

2) BIP32 support

3) bech32 support

For .1-2, I also intent to swap out cryptopp in full for Jonas Schnelli's libbtc, which operates as a wrapper around the Core crypto libraries in Armory's use case.

There will be some work needed to accomodate the new wallet features in the GUI. I'd also like to use this opportunity to introduce an advanced filter feature for ledgers (some sort of pseudo regex), so that people can customize their ledgers without me having to hardcode a filter GUI for each scenario.

I would also like to leverage the new wallet code and its flexibility with meta data to introduce a new privacy feature, in which you can create and manage a list of vendors and voluntarily flag your payments to that vendor, to improve coin selection privacy.

As an example, assume you use BitPay vendors. You would add BitPay as a vendor to your wallet, and flag the addresses of theirs that you use while construction payment tx. This would allow the coin selection to prioritize change addresses you used with BitPay in the past, and warn you when you have to introduce an unrelated UTXO to meet your payment. I've noticed through my own usage that I often end up moving coins to the same handful of services, and the code is lacking the meta data that would otherwise minimize my coins exposure to these services.

There are other big items on the list, like hardware wallet support, blocks over p2p, common export formats like BIP39, py3/qt5, but these will most likely be for 0.98.

I also have a couple contacts at Lightning Labs and am looking to interface Armory with their daemon so that people can at least create, close and revoke LN channels in the future, with the understanding that most of the heavy lifting will be offloaded to their code. This would be either 0.98 or 0.99, and obviously optional.

Very happy with how well 0.96.4 is working, can't fault it after testing it out for a few days.

Any news on 0.97? (features, not ETA )

Downlaod armory_0.96.4_src.tar. The other ones are automatically generated by Github and do not have all of the necessary components.