Topic: Armory 0.96 is out (Read 13770 times)

Because that hasn't been the official download location for a long time now... the original bitcoin armory "company" essentially folded (https://bitcointalksearch.org/topic/the-end-of-the-road-for-armory-1351792)... goatpig took over development.

The NEW website is: https://btcarmory.com/
The very latest code is available on goatpig's GitHub: https://github.com/goatpig/BitcoinArmory/releases

You should read the "sticky" posts stuck to the top of the board like this one: https://bitcointalksearch.org/topic/0964-rc1-2227856

Unfortunately, for whatever reason, the original Bitcoin Armory people have left their website up and running... which seems to confuse the hell out of everyone... even more so than Armory itself and it's requirement to have a full Bitcoin Core node running behind it!

With all due respect sir,

I downloaded armory_0.96_win64.exe  from  https://www.bitcoinarmory.com/download/ .

Why isn't that the latest version?

Where else am I supposed to get it?

Thanks

j/k

Grab the latest version from the stickies, you're using dated stuff. Also delete your databases folder. If you're still having trouble, make a thread and post your logs.

No.

This message is to goatpig.
Recently I installed armory 0.96 on a windows 10 machine.
Unfortunately every time I open it I get the error message  " armory_failed_to_spawn_the_db/ "
And Armory is offline.
Would you be kind enough to tell me how to fix the problem?

Thanking you in advance,

Gangat

I fixed all of the known RBF issues just an hour ago. The fixes are in the testing branch if you'd like to try them out, otherwise I'll put out a new RC once I have the BTG signer done.


That won't trigger rescans anymore, as the DB keeps track of all addresses it sees now. You can flag the DB for a rescan from the help menu. Any rescan or rebuild action won't carry over the ZC state, so you'll lose the entries in the ledger.


I'll look into that.

Well, my tx didn't need bumping in the end.  But Armory (0.96.3) seems can't detect its own txs; I think I'm going to run out of outputs soon



Re-importing the wallet didn't help; I was hoping there was a way to invoke rescanning?  And trying to do a Wallet Consistency check gave a backtrace and an empty
Perform Wallet Consistency Check with both buttons greyed out:
(ERROR) ArmoryUtils.py:3192 - Error in pybkgdthread: 'unicode' object has no attribute 'walletPath'
Traceback (most recent call last):
  File "/usr/lib/armory/armoryengine/ArmoryUtils.py", line 3190, in run
    self.output = self.func()
  File "/usr/lib/armory/armoryengine/ArmoryUtils.py", line 3127, in funcPartial
    return thefunc(*args, **kwargs)
  File "/usr/lib/armory/armoryengine/PyBtcWalletRecovery.py", line 1848, in ParseWallet
    Progress=Progress)
  File "/usr/lib/armory/armoryengine/ArmoryUtils.py", line 3218, in wrappedFunc
    return func(*args, **kwargs)
  File "/usr/lib/armory/armoryengine/PyBtcWalletRecovery.py", line 1695, in FixWallet
    frt = fixer.ProcessWallet(wltPath, wlt, Passphrase, mode, Progress=Progress)
  File "/usr/lib/armory/armoryengine/ArmoryUtils.py", line 3218, in wrappedFunc
    return func(*args, **kwargs)
  File "/usr/lib/armory/armoryengine/PyBtcWalletRecovery.py", line 400, in ProcessWallet
    WalletPath = Wallet.walletPath
AttributeError: 'unicode' object has no attribute 'walletPath'


Thanks!
Rusty.

You have a Unicode character (Ö) somewhere in your path. Armory can't handle Unicode. You'll have to make the entire path ASCII-only.

Hi,

 I just installed the wallet but can't launch it:

It is a common problem: Do you want to display a progress box, if you don't know how long the operation is going to take?  Some programs delay popping up the dialog until a few seconds have passed.  It can still pop up a fraction of a second before it closes, but now it is a lot less likely.

Or you could put a 1-sec delay on closing it.  But please don't require an extra click

To allow for the use of segwit and compressed key in p2sh scripts, I developed a whole new wallet code. This stuff is in C++ and operates as companion code to the python stuff. The goal was to no disrupt the existing, time tested code, while providing new features for those willing to run new code.

This flashing dialog is for the operation the mirrors the python wallet containers into their new, C++ implemented counterparts. These wallets are WO only, as they only need the data necessary to register the scripts with the DB and construct unsigned transactions. And no, there's nothing to click on, it is just there for report progress on the mirroring, and closes on its own. I figured I'd rather let people see something progress than silently mirror wallets, which can take up to a couple minutes on large wallets.

You will see that dialog every run because you use an imported address, and the mirroring code goes through every import each run, since there is no deterministic way to verify the mirrored wallet is still in sync with the python counterpart.

I'm not sure where to take that part of the GUI atm (if letting the dialog flash is ok, or requiring user interaction to close it is gonna piss off people real quick).


Yep, I borked that when I fixed comments resolution in the main ledger.


And apparently I borked that too... fml.

Thanks for the reports, will go over that stuff .4

0.96.3 gcc 5.7 ubuntu deb.  Three issues I've found (was on 0.93.3).

- I get a flashed-up-then-gone dialog on startup.  Finally caught it on video, it's "Mirroring Wallets".  Is this something I should be able to click on?

- Bump fee via right-click fails (see error below).  This is my imported vanity addr 1RustyR...

- You told a previous user to use the RBF control dialog, hitting that gives this error (and no effect):
Hope that helps track something!  Meanwhile I'll wait for my 2sat/byte TX

Thanks!
Rusty.

is there any general reason why both 0.95.1 and 0.96 *.deb in VM would both show Connected status bottom right but be stuck at 470751?  everything else appears ok.

getblockcount shows correct height.

I suppose so. Thanks.

I do plan on pushing out an offline package for 0.96.1 if it's what you are referring to.

Thank you for this thorough tutorial. It helped a lot.

I tried installing "armory_0.96-gcc5.4_amd64.deb" as an offline wallet but it required downloading a couple of files. Obviously, I am not about to compromise my offline machine by exposing it to the interweb just to download said files. Will the next release be self-contained (i.e. not requiring to go online to download some files in order to complete its installation)?

goatpig: Installed latest test build #4 and all worked great and balance all confirmed. Test transaction pending and should be good. Thanks for your assistance!

It's still there, but posting the individual files is better, as the export option, while more accessible to the user, compounds both client and db logs together which makes it a bit harder on those who read through it. More often than not, only one of the logs is actually relevant to a given issue.