Armory 0.96 is out

[goatpig]

If there's change, you should CPFP. Otherwise clear unconfirmed and push again.

[1714679271]

1714679271

[1714679271]

1714679271

[1714679271]

1714679271

[1714679271]

1714679271

[1714679271]

1714679271

[1714679271]

1714679271

[bitbitcoincoin]

If there's change, you should CPFP. Otherwise clear unconfirmed and push again.

It showed as the only transaction, no returning change.

I cleared unconfirmed and am trying again but now getting the "tx timeout" error, guessing I need to rebuild and rescan now?

[goatpig]

No, use the testing build for 0.96.1

[bitbitcoincoin]

No, use the testing build for 0.96.1

Just loaded it, clicked send with a higher fee this time and nothing happened after the passphrase window closed. Armory behaving as if I never tried to send any BTC, never had this happen before and it's kinda scary...

[goatpig]

post armorylog.txt

[bitbitcoincoin]

quite a lot to it, going through it looks like this is where Im getting an error when I try to send after updating to the beta edition

2017-06-07 10:21:52 (INFO) -- ArmoryQt.py:3099 - Sending Tx, 7fc06e76fa56988078b52575391fb98472fbdcd6796567399df6728d739f9d36
2017-06-07 10:21:58 (ERROR) -- Traceback (most recent call last):
  File "ui\QtExecuteSignal.pyc", line 31, in methodSlot
  File "ArmoryQt.py", line 5036, in handleCppNotification
  File "ArmoryQt.py", line 3114, in zcBroadcastError
  File "CppBlockUtils.pyc", line 3012, in broadcastThroughRPC
DbErrorMsg: <CppBlockUtils.DbErrorMsg; proxy of <Swig Object of type 'DbErrorMsg *' at 0x000000000375CF30> >

Let me know if you need more info, I can post all of today but it's a ton of text.

[goatpig]

Turn on your node RPC.

[bitbitcoincoin]

Turn on your node RPC.

After some research apparently this is bitcoind?  I remembered I had a error message pop up during the beta install which may have caused bitcoind to not run properly.

Anyways I just did what I did when I had a similar issue last week, reinstalled the non beta edition and now everything is working fine. Coins are now showing as confirmed on both ends, thanks for the help.

[goatpig]

After some research apparently this is bitcoind?  I remembered I had a error message pop up during the beta install which may have caused bitcoind to not run properly.

No, that's automating the node.

RPC is the other interface your node provides the is used in Armory to gather fee estimates and error status on transactions broadcast failure (if you use the latest testing version). This would give you an idea what's going on with your transaction.

[naska21]

Hi, Armory 0.96.0.1 stuck on  block 466853. The database is loading but after its building armory status always states Connected (466853 blocks)   What should I do?

P.S. Did rebuild database. Now the status is Connected 470 510 blocks/ The blocks number corresponds to current one. Will see  if it changes with blocks found

P.P.S It follows the current block!

[bjernvig]

Binaries:

https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96

changelog

https://github.com/goatpig/BitcoinArmory/blob/master/changelog.txt

Notable changes:

1) SegWit
2) RBF & CPFP
3) Translations
4) Compressed public keys
5) Reworked coin control and address tree UI
6) Fleshed out fee and privacy features

Better description on the webpage: https://btcarmory.com/0.96.0-release/

Notes:

Only putting out Windows x64 and Linux x64 builds atm. Offline bundles, RPi and OSX builds for 0.96.1, once I get rid of the twisted/openssl dependency. Eta 1-2 weeks.

Thanks:

achow101 for the support and translation PR, droark for the OSX support and the testers for helping tiddy things up.

Enjoy =)

Happy to see Armory still moving forward, efforts are much appreciated here!
Has anyone successfully restored from a fragmented two of three paper backup with 0.96?
0.96 is the release that got me past the "offline" phase in which you can't "do" anything such as restore backups... so pleased with that!
I'm trying to restore from a 2 of 3 fragmented paper backup, wallet version 1.35c with a SecurePrint code.
I type in my two fragments, but the "Restore from fragments" button remains disabled bottom right.
Am I doing something wrong, or is this a bug with a workaround perhaps?
Getting a little nervous as now running low on options for accessing my funds... A Windows update destroyed the PC holding my bitcoins!

Thanks for any help :-)

Hi I am having the same paper backup issue on my Windows 10 computer. I have also downloading the Armory 0.96.2 test version from githut and the"restore wallet" is then not disabled anymore, but nothing happens when clicking the button. Has this restore wallet issue been fixed in another build that I could maybe use?

Thanks for all your support on this one

[goatpig]

It's most likely fixed in the code but not built for yet. Post your armorylog.txt for the good measure. Use pastebin.

[bjernvig]

It's most likely fixed in the code but not built for yet. Post your armorylog.txt for the good measure. Use pastebin.

I have put the content of the log file here:
https://pastebin.com/ubxdjVWu

As you can see I have clicked the "Restore wallet" button a couple of times:-)

Thanks for the quick response by the way

[goatpig]

This is fixed in code already.

[bjernvig]

Great!

Do you have an estimated date for when the release with the issue fixed will be made available?

[goatpig]

Early next week

[Alexoz]

Hey guys, I'm stuck here https://github.com/goatpig/BitcoinArmory/blob/master/osxbuild/OSX_build_notes.md "7. Compile Armory.

cd osxbuild
python build-app.py > /dev/null

No such file or directory

[gangtraet]

That seems weird.  Have you checked that the file is there?  Have you spelled it correctly on the command line (perhaps using TAB completion).

[goatpig]

Did you git submodule?

[naska21]

Hi, noticed some issue with 0.96.0.1. After closing the list of available addresses the main window results in Not Responding state when trying to close it . Checked it several times.