Bitcoin Forum

Bitcoin => Armory => Topic started by: goatpig on October 21, 2016, 08:27:47 PM



Title: Armory 0.95 is out
Post by: goatpig on October 21, 2016, 08:27:47 PM
No changes since the last testing release (0.94.99.1). I've decided to sticky the latest stable release thread from now. Enjoy

Binaries:

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

Changelog:

https://github.com/goatpig/BitcoinArmory/blob/v0.95.0/changelog.txt

- Forgot to bump the version and add the date in the changelog, will do for 0.95.1
- On windows, the automated DB will spawn a command line dialog. This wasn't the intention originally, but it goes a long way conveying the change in architecture. I've decided to leave it as is until 0.95.1.

*************************************

Botched auto bitcoind management on Windows,
you'll have to turn it off until I get a fix out.

**************************************


Title: Re: Armory 0.95 is out
Post by: Carlton Banks on October 22, 2016, 10:30:28 AM
@users of Qubes OS:

0.95 is currently not working with Whonix, investigating a fix to that right now.


Debian 8 template is running 0.95 ok. Those that add parameters to their /usr/share/applications/armory.desktop file may need to invoke python directly (i.e. "Exec=python /usr/lib/armory/ArmoryQt.py <arguments>" instead of running the /usr/bin/armory script file. Don't forget to run /usr/lib/qubes/qubes-trigger-sync-app-menus after editing your .desktop files.


Title: Re: Armory 0.95 is out
Post by: m.fridge on October 23, 2016, 04:09:53 PM
Hi,

thanks for finalizing the new release! I am keen to check it out :)

I get the following compilation error in Swig:
Code:
CppBlockUtils_wrap.cxx:3991:77: error: ‘type_name’ is not a member of ‘swig::traits<long long unsigned int>’

Regards,
Michael


Title: Re: Armory 0.95 is out
Post by: goatpig on October 23, 2016, 04:28:02 PM
Hi,

thanks for finalizing the new release! I am keen to check it out :)

I get the following compilation error in Swig:
Code:
CppBlockUtils_wrap.cxx:3991:77: error: ‘type_name’ is not a member of ‘swig::traits<long long unsigned int>’

Regards,
Michael

What OS and compiler are you using?


Title: Re: Armory 0.95 is out
Post by: visdude on October 28, 2016, 04:00:30 AM

Armory 0.95 is not working for me. Due to some changes in 0.95 (e.g. Client and Database split), I assume that my arg in my ArmoryQt shortcut target which is set to point to alternate database directories for both Bitcoin Core and Armory is no longer valid (it was working just fine with 0.94.1). What do I have to do to get 0.95 working without changing my current alternate Bitcoin Core and Armory database locations/directories.

This is my current Armory shortcut target arg that worked quite well with 0.94.1:

"C:\Program Files (x86)\Armory\ArmoryQt.exe" --satoshi-datadir="D:\Bitcoin" --datadir="D:\Armory"

Also, on the btcarmory site under "Notable Changes", it says:

"Client no longer requires a local Bitcoin node to operate as P2P has moved to ArmoryDB"

...while under "Full changelog/Added", it also states:

"ArmoryDB requires the presence of a bitcoin node on localhost:8333 and access to raw blockchain data like before".

I'm confused. Do I still or do I not have to manually fire up and sync Bitcoin core 0.13.1 before running Armory 0.95 as I did before with Armory 0.94.1? I'm running W7 x64 BTW.

Sorry for my cluelessness as I am very coding-illiterate.



Title: Re: Armory 0.95 is out
Post by: achow101 on October 28, 2016, 04:23:37 AM

Armory 0.95 is not working for me. Due to some changes in 0.95 (e.g. Client and Database split), I assume that my arg in my ArmoryQt shortcut target which is set to point to alternate database directories for both Bitcoin Core and Armory is no longer valid (it was working just fine with 0.94.1). What do I have to do to get 0.95 working without changing my current alternate Bitcoin Core and Armory database locations/directories.

This is my current Armory shortcut target arg that worked quite well with 0.94.1:

"C:\Program Files (x86)\Armory\ArmoryQt.exe" --satoshi-datadir="D:\Bitcoin" --datadir="D:\Armory"
That should be fine. What is probably broken is the fact that goatpig forgot to include guardian.exe which is what spawns the bitcoind when Armory is set to auto manage it.

Also, on the btcarmory site under "Notable Changes", it says:

"Client no longer requires a local Bitcoin node to operate as P2P has moved to ArmoryDB"

...while under "Full changelog/Added", it also states:

"ArmoryDB requires the presence of a bitcoin node on localhost:8333 and access to raw blockchain data like before".

I'm confused. Do I still or do I not have to manually fire up and sync Bitcoin core 0.13.1 before running Armory 0.95 as I did before with Armory 0.94.1? I'm running W7 x64 BTW.

Sorry for my cluelessness as I am very coding-illiterate.
There are two parts, the DB (ArmoryDB) and the client (ArmoryQt). ArmoryDB requires a local Bitcoind. ArmoryQt can connect to any instance of ArmoryDB, both remote and local. That does not require a local bitcoind. ArmoryQt will automatically spawn an instance of ArmoryDB of it does not detect one locally and a remote one is not specified. Thus, if you are just running ArmoryQt without doing anything to ArmoryDB, then you will still need to run Bitcoin Core locally.

tl;dr yes you still need Bitcoin Core locally.


Title: Re: Armory 0.95 is out
Post by: visdude on October 28, 2016, 11:23:36 AM

Armory 0.95 is not working for me. Due to some changes in 0.95 (e.g. Client and Database split), I assume that my arg in my ArmoryQt shortcut target which is set to point to alternate database directories for both Bitcoin Core and Armory is no longer valid (it was working just fine with 0.94.1). What do I have to do to get 0.95 working without changing my current alternate Bitcoin Core and Armory database locations/directories.

This is my current Armory shortcut target arg that worked quite well with 0.94.1:

"C:\Program Files (x86)\Armory\ArmoryQt.exe" --satoshi-datadir="D:\Bitcoin" --datadir="D:\Armory"
That should be fine. What is probably broken is the fact that goatpig forgot to include guardian.exe which is what spawns the bitcoind when Armory is set to auto manage it.

Also, on the btcarmory site under "Notable Changes", it says:

"Client no longer requires a local Bitcoin node to operate as P2P has moved to ArmoryDB"

...while under "Full changelog/Added", it also states:

"ArmoryDB requires the presence of a bitcoin node on localhost:8333 and access to raw blockchain data like before".

I'm confused. Do I still or do I not have to manually fire up and sync Bitcoin core 0.13.1 before running Armory 0.95 as I did before with Armory 0.94.1? I'm running W7 x64 BTW.

Sorry for my cluelessness as I am very coding-illiterate.
There are two parts, the DB (ArmoryDB) and the client (ArmoryQt). ArmoryDB requires a local Bitcoind. ArmoryQt can connect to any instance of ArmoryDB, both remote and local. That does not require a local bitcoind. ArmoryQt will automatically spawn an instance of ArmoryDB of it does not detect one locally and a remote one is not specified. Thus, if you are just running ArmoryQt without doing anything to ArmoryDB, then you will still need to run Bitcoin Core locally.

tl;dr yes you still need Bitcoin Core locally.

Thank you for the timely reply and explanation. It's helping me understand a bit more though it is still a challenge for me to comprehend the intricacies of coding. I'm just a plain ol' user.

When I run ArmoryQt with the shortcut arg (specifying Bitcoin and Armory alternative/non-standard database directory paths) after starting and syncing Bitcoin Core 0.13.1 (not managed by ArmoryQt), the client opens with the ArmoryDB CLI dialog and does nothing else after the third line:

http://s10.postimg.org/za752gjgp/Armory_DB_cl_dialog.png

...and of course, ArmoryQt consequently gets stuck at this point without any progress...and offline:

http://s16.postimg.org/7g1sqxdid/Armory_Qt_stuck.png

Though I don't think it's related to my particular issue, I'm curious as to why there is a "slash" (/) instead of a "backslash" (\) between "Roaming" and "Armory" on the first line of the CLI dialog (directory path).

From what I can surmise, perhaps the ArmoryQt shortcut arg (directory locations) is not being passed on when it automatically spawns an instance of ArmoryDB, thereby not finding the specified database directories. It's most likely a far-fetched assumption on my part but if it is so, can you suggest a workaround?

Just out of curiosity, was there a reason/purpose of the binary split since it was working just fine up to 0.94.1?




Title: Re: Armory 0.95 is out
Post by: achow101 on October 28, 2016, 12:23:41 PM
Thank you for the timely reply and explanation. It's helping me understand a bit more though it is still a challenge for me to comprehend the intricacies of coding. I'm just a plain ol' user.

When I run ArmoryQt with the shortcut arg (specifying Bitcoin and Armory alternative/non-standard database directory paths) after starting and syncing Bitcoin Core 0.13.1 (not managed by ArmoryQt), the client opens with the ArmoryDB CLI dialog and does nothing else after the third line:

...and of course, ArmoryQt consequently gets stuck at this point without any progress...and offline:
Can you post the log files?

Though I don't think it's related to my particular issue, I'm curious as to why there is a "slash" (/) instead of a "backslash" (\) between "Roaming" and "Armory" on the first line of the CLI dialog (directory path).
That shouldn't matter. The backslash and forward slash are treated the same.

From what I can surmise, perhaps the ArmoryQt shortcut arg (directory locations) is not being passed on when it automatically spawns an instance of ArmoryDB, thereby not finding the specified database directories. It's most likely a far-fetched assumption on my part but if it is so, can you suggest a workaround?
I doubt it.

Just out of curiosity, was there a reason/purpose of the binary split since it was working just fine up to 0.94.1?
The main reason is to make the litenode feature work. Litenode is where you run the client remotely and have it connect to an ArmoryDB instance on another machine. I think the idea is to shift Armory towards an Electrum-like architecture where you have clients and servers.


Title: Re: Armory 0.95 is out
Post by: goatpig on October 28, 2016, 01:19:54 PM
From what I can surmise, perhaps the ArmoryQt shortcut arg (directory locations) is not being passed on when it automatically spawns an instance of ArmoryDB, thereby not finding the specified database directories. It's most likely a far-fetched assumption on my part but if it is so, can you suggest a workaround?

The same pathing command line arguments that work on the client work on the DB. You can see the full list of DB cli arg here:

https://github.com/goatpig/BitcoinArmory/blob/master/cppForSwig/BlockUtils.cpp#L812

and these are the default paths:

https://github.com/goatpig/BitcoinArmory/blob/master/cppForSwig/BlockUtils.cpp#L704

The DB will append /database to you datadir if no dbdir is specified.

If you have issues letting the client automate the DB spawning, I suggest you start the DB manually with the arguments you want and see how it operates. You will need to run ArmoryDB.exe in the command prompt.

Quote
Just out of curiosity, was there a reason/purpose of the binary split since it was working just fine up to 0.94.1?

Plenty of reason to split the server from the client. One is remote capability, another is multiple clients to one server, another is process isolation (after all, the client does everything wallets, the db does everything blockchain, and they dont intersect in these duties), another is to enable Armory to operate as a web stack element (one server in the backend, any number of clients over HTTP).

--------------------------

Ima digress here, TL;DR: it's awesome.

DB/client separation makes sense in the long term. 2 features needed in Armory are supernode and blocks over P2P. Blocks over P2P is a versatility and stability feature, supernode is a power user/professional feature. They both require aspects of the client/server separation.

Another benefit is splitting the code base, which will come in the future.

Overall this feature is inscribed in my vision for Armory. I want Armory to cater to high end users and professionals. Client/server separation is a must have in this case. Maybe this example will make my case better than a list of requirements:

When the likes of Microsoft and Dell add Bitcoin payment support, they're not integrating with Bitcoin, they are simply interfacing with a payment processor like Coinbase or BitPay.

It makes me die a little inside every time an IT giant approaches the Bitcoin space like your local florist integrates with Paypal. I would like there to be an industry standard, robust and full featured open source solution targeted at their needs, a kind of no brainer go to stack, and this is where I am trying to take Armory.

As for individual users, I fancy them all enthusiasts, and I believe their needs largely intersect with professional use cases. To give you another example, the reality towards with 0.95 is working, is that in the future you could have a server at home that runs your own Core and ArmoryDB instances, and with a JavaScript template, get your Armory GUI straight to your mobile phone, and offline sign with a Trezor on the spot, all the while fully verifying the blockchain with code you run and no privacy leak.

Imagine your friends and family are interested in Bitcoin. You could provide them with the full bitcoin experience with no privacy leak nor the need to rely on a 3rd party service. With supernode, you could even offer them a blockchain explorer service, again with no risk of privacy leaks.

Imagine in the future you are running a node to support your Lightning hub. You won't need a second node just to run Armory, point the DB to your existing one.

Imagine you want to setup a multisig scheme and split keys among several devices, some of which are online. You would be able to bounce the transaction stub between online devices, finalize and broadcast from any of these, all running against the same remote server. And then there's all the use cases I can't think of yet.

Put another way, it's the future! Flying cars and self drying clothes. Now, drink the koolaid!


Title: Re: Armory 0.95 is out
Post by: visdude on October 28, 2016, 11:41:37 PM
Thank you for the timely reply and explanation. It's helping me understand a bit more though it is still a challenge for me to comprehend the intricacies of coding. I'm just a plain ol' user.

When I run ArmoryQt with the shortcut arg (specifying Bitcoin and Armory alternative/non-standard database directory paths) after starting and syncing Bitcoin Core 0.13.1 (not managed by ArmoryQt), the client opens with the ArmoryDB CLI dialog and does nothing else after the third line:

...and of course, ArmoryQt consequently gets stuck at this point without any progress...and offline:
Can you post the log files?

Here they are (wallet/user info obscured with x's).

From armorycpplog:

Log file opened at 1477695827: D:\ArmoryData\Armory\armorycpplog.txt
-ERROR - 1477695831: (..\SwigClient.cpp:61) unexpected type


From armorylog:

2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1128 - C++ block utilities loaded successfully
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1238 -
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1239 -
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1240 -
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1241 - ************************************************************
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1242 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe --satoshi-datadir=D:\BitcoinData\Bitcoin --datadir=D:\ArmoryData\Armory
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1243 - ************************************************************
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1244 - Loading Armory Engine:
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1245 -    Armory Version        : 0.95
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1246 -    Armory Build:         : 374672b751
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1247 -    PyBtcWallet  Version  : 1.35
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1248 - Detected Operating system: Windows
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1249 -    OS Variant            : 7-6.1.7601-SP1-Multiprocessor Free
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1250 -    User home-directory   : C:\Users\xxxxxxxx\AppData\Roaming
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1251 -    Satoshi BTC directory : D:\BitcoinData\Bitcoin
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1252 -    Armory home dir       : D:\ArmoryData\Armory
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1253 - Detected System Specs    :
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1254 -    Total Available RAM   : 15.94 GB
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1255 -    CPU ID string         : Intel64 Family 6 Model 60 Stepping 3, GenuineIntel
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1256 -    Number of CPU cores   : 4 cores
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1257 -    System is 64-bit      : True
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1258 -    Preferred Encoding    : cp1252
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1259 -    Machine Arch          : amd64
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1260 -    Available HDD (ARM)   : 108 GB
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1261 -    Available HDD (BTC)   : 108 GB
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1262 -
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1263 - Network Name: Main Network
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1264 - Satoshi Port: 8333
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1265 - Do wlt check: True
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1266 - Named options/arguments to armoryengine.py:
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     thread_count    : -1
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     rescan          : False
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     ignoreAllZC     : False
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     rescanBalance   : False
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     disableModules  : False
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     port            : None
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     interport       : 8223
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     skipStatsReport : False
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     forceWalletCheck: False
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     regtest         : False
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     rebuild         : False
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     nettimeout      : 2
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     datadir         : D:\ArmoryData\Armory
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     clearMempool    : False
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     offline         : False
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     coverageOutputDir: None
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     armoryDBDir     : DEFAULT
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     armorydb_port   : 9001
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     satoshiPort     : DEFAULT
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     useTorSettings  : False
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     netlog          : False
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     keypool         : 100
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     coverageInclude : None
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     forceOnline     : False
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     skipAnnounceCheck: False
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     redownload      : False
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     armorydb_ip     : 127.0.0.1
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     multisigFile    : DEFAULT
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     ram_usage       : -1
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     testAnnounceCode: False
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     mtdebug         : False
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     logDisable      : False
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     settingsPath    : D:\ArmoryData\Armory\ArmorySettings.txt
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     db_type         : DB_FULL
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     doDebug         : False
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     enableDetSign   : True
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     disableConfPermis: False
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     testnet         : False
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     rpcport         : DEFAULT
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     satoshiHome     : D:\BitcoinData\Bitcoin
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     satoshiRpcport  : DEFAULT
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     logFile         : D:\ArmoryData\Armory\ArmoryQt.exe.log.txt
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1268 -     verbosity       : None
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1269 - Other arguments:
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1272 - ************************************************************
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:1675 - C++ block utilities loaded successfully
2016-10-28 16:03 (INFO) -- BDM.pyc:367 - Using the asynchronous/multi-threaded BlockDataManager.
2016-10-28 16:03 (INFO) -- BDM.pyc:368 - Blockchain operations will happen in the background. 
2016-10-28 16:03 (INFO) -- BDM.pyc:369 - Devs: check TheBDM.getState() before asking for data.
2016-10-28 16:03 (INFO) -- BDM.pyc:370 - Registering addresses during rescans will queue them for
2016-10-28 16:03 (INFO) -- BDM.pyc:371 - inclusion after the current scan is completed.
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:3588 - Using settings file: D:\ArmoryData\Armory\ArmorySettings.txt
2016-10-28 16:03 (INFO) -- ArmoryQt.py:2485 - loadWalletsAndSettings
2016-10-28 16:03 (INFO) -- ArmoryQt.py:2539 - Loading wallets...
2016-10-28 16:03 (INFO) -- ArmoryQt.py:2598 - Number of wallets read in: 3
2016-10-28 16:03 (INFO) -- ArmoryQt.py:2603 -    Wallet (xxxxxxxxx):   "xxxxxxxx (Watch)                     "   (No Encryption)
2016-10-28 16:03 (INFO) -- ArmoryQt.py:2603 -    Wallet (xxxxxxxxx):   "xxxxxxxx (Watch)                   "   (No Encryption)
2016-10-28 16:03 (INFO) -- ArmoryQt.py:2603 -    Wallet (xxxxxxxxx):   "xxxxxxxx (Watch)                    "   (No Encryption)
2016-10-28 16:03 (INFO) -- ArmoryQt.py:2608 - Loading Multisig Lockboxes
2016-10-28 16:03 (INFO) -- ArmoryQt.py:2153 - Setting up networking...
2016-10-28 16:03 (INFO) -- ArmoryQt.py:1412 - setupUriRegistration
2016-10-28 16:03 (INFO) -- ArmoryQt.py:1480 - Armory already registered for current user.  Done!
2016-10-28 16:03 (INFO) -- ArmoryQt.py:546 - Usermode: Expert
2016-10-28 16:03 (INFO) -- ArmoryQt.py:1708 - Changing usermode:
2016-10-28 16:03 (INFO) -- ArmoryQt.py:1709 -    From: Expert
2016-10-28 16:03 (INFO) -- ArmoryQt.py:1717 -      To: Expert
2016-10-28 16:03 (INFO) -- ArmoryQt.py:2217 - startBitcoindIfNecessary
2016-10-28 16:03 (INFO) -- ArmoryQt.py:2257 - setSatoshiPaths
2016-10-28 16:03 (INFO) -- SDM.pyc:382 - Reading bitcoin.conf file
2016-10-28 16:03 (INFO) -- SDM.pyc:395 - Setting permissions on bitcoin.conf
2016-10-28 16:03 (INFO) -- SDM.pyc:404 - Setting permissions on bitcoin.conf
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:642 - Executing popen: [u'icacls', u'D:\\BitcoinData\\Bitcoin\\bitcoin.conf', u'/inheritance:r', u'/grant:r', u'xxxxxxxx:F']
2016-10-28 16:03 (INFO) -- SDM.pyc:410 - icacls returned:
2016-10-28 16:03 (INFO) -- SDM.pyc:755 - Creating proxy in SDM: host=127.0.0.1, port=8332
2016-10-28 16:03 (INFO) -- ArmoryQt.py:2257 - setSatoshiPaths
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:642 - Executing popen: ['./ArmoryDB.exe', '--db-type="DB_FULL"', '--spawnId="BNvn2WehsxpeokfqjebEwukaYuXRdkgkyLHp9pSrgnS5"', u'--satoshi-datadir="D:\\BitcoinData\\Bitcoin\\blocks"', u'--dbdir="D:\\ArmoryData\\Armory\\databases"']
2016-10-28 16:03 (INFO) -- ArmoryQt.py:2307 - Setting netmode: 1
2016-10-28 16:03 (INFO) -- ArmoryQt.py:2307 - Setting netmode: 0
2016-10-28 16:03 (INFO) -- ArmoryQt.py:2289 - loadBlockchainIfNecessary
2016-10-28 16:03 (INFO) -- ArmoryQt.py:5645 - Dashboard switched to "Scanning" mode
2016-10-28 16:03 (INFO) -- ArmoryQt.py:5645 - Dashboard switched to "Scanning" mode
2016-10-28 16:03 (INFO) -- ArmoryUtils.pyc:3753 - Another Armory instance just tried to open.
2016-10-28 16:19 (INFO) -- ArmoryQt.py:6366 - BDM state is scanning -- force shutdown BDM
2016-10-28 16:19 (INFO) -- SDM.pyc:587 - Called stopBitcoind
2016-10-28 16:19 (INFO) -- SDM.pyc:593 - ...but bitcoind is not running, to be able to stop
2016-10-28 16:19 (INFO) -- ArmoryQt.py:6386 - Attempting to close the main window!



Title: Re: Armory 0.95 is out
Post by: visdude on October 29, 2016, 12:10:48 AM

Plenty of reason to split the server from the client. One is remote capability, another is multiple clients to one server, another is process isolation (after all, the client does everything wallets, the db does everything blockchain, and they dont intersect in these duties), another is to enable Armory to operate as a web stack element (one server in the backend, any number of clients over HTTP).

--------------------------

Ima digress here, TL;DR: it's awesome.

DB/client separation makes sense in the long term. 2 features needed in Armory are supernode and blocks over P2P. Blocks over P2P is a versatility and stability feature, supernode is a power user/professional feature. They both require aspects of the client/server separation.

Another benefit is splitting the code base, which will come in the future.

Overall this feature is inscribed in my vision for Armory. I want Armory to cater to high end users and professionals. Client/server separation is a must have in this case. Maybe this example will make my case better than a list of requirements:

When the likes of Microsoft and Dell add Bitcoin payment support, they're not integrating with Bitcoin, they are simply interfacing with a payment processor like Coinbase or BitPay.

It makes me die a little inside every time an IT giant approaches the Bitcoin space like your local florist integrates with Paypal. I would like there to be an industry standard, robust and full featured open source solution targeted at their needs, a kind of no brainer go to stack, and this is where I am trying to take Armory.

As for individual users, I fancy them all enthusiasts, and I believe their needs largely intersect with professional use cases. To give you another example, the reality towards with 0.95 is working, is that in the future you could have a server at home that runs your own Core and ArmoryDB instances, and with a JavaScript template, get your Armory GUI straight to your mobile phone, and offline sign with a Trezor on the spot, all the while fully verifying the blockchain with code you run and no privacy leak.

Imagine your friends and family are interested in Bitcoin. You could provide them with the full bitcoin experience with no privacy leak nor the need to rely on a 3rd party service. With supernode, you could even offer them a blockchain explorer service, again with no risk of privacy leaks.

Imagine in the future you are running a node to support your Lightning hub. You won't need a second node just to run Armory, point the DB to your existing one.

Imagine you want to setup a multisig scheme and split keys among several devices, some of which are online. You would be able to bounce the transaction stub between online devices, finalize and broadcast from any of these, all running against the same remote server. And then there's all the use cases I can't think of yet.

Put another way, it's the future! Flying cars and self drying clothes. Now, drink the koolaid!


Thanks for elaborating on your vision of Armory. Very cool stuff...especially the hardware wallet>mobile device app>private remote node/server scenario. Awesomeness indeed! Imbibing the koolaid.



Title: Re: Armory 0.95 is out
Post by: goatpig on October 29, 2016, 12:55:35 AM
Run the DB manually.


Title: Re: Armory 0.95 is out
Post by: visdude on October 29, 2016, 03:57:21 AM
Run the DB manually.

How do I do that? Running stuff in a CLI terminal gives me the heebie-jeebies...it horrifies me.

Better yet, can I just copy and paste the arg from the ArmoryQt shortcut (Core and Armory database paths) that worked before the upgrade into an ArmoryDB shortcut and run it this way?

BTW, did you get a chance to see the logs I posted above for achow101? Anything unusual in them that would indicate why it crashes on me?



Title: Re: Armory 0.95 is out
Post by: goatpig on October 29, 2016, 09:47:44 AM
Better yet, can I just copy and paste the arg from the ArmoryQt shortcut (Core and Armory database paths) that worked before the upgrade into an ArmoryDB shortcut and run it this way?

Yes

Quote
BTW, did you get a chance to see the logs I posted above for achow101? Anything unusual in them that would indicate why it crashes on me?

Yes. This is why I instructed you to start the DB manually.


Title: Re: Armory 0.95 is out
Post by: visdude on October 29, 2016, 08:37:57 PM
Better yet, can I just copy and paste the arg from the ArmoryQt shortcut (Core and Armory database paths) that worked before the upgrade into an ArmoryDB shortcut and run it this way?

Yes

Quote
BTW, did you get a chance to see the logs I posted above for achow101? Anything unusual in them that would indicate why it crashes on me?

Yes. This is why I instructed you to start the DB manually.

Crashed.

https://s21.postimg.org/a7s6bwc5j/Armory_DB_message.png

dblog:

Log file opened at 1477771772: D:\ArmoryData\Armory/dbLog.txt
-INFO  - 1477771772: (..\main.cpp:22) Running on 4 threads
-INFO  - 1477771772: (..\main.cpp:23) Ram usage level: 4
-INFO  - 1477771772: (..\BlockUtils.cpp:1325) blkfile dir: D:\BitcoinData\Bitcoin/blocks
-INFO  - 1477771772: (..\BlockUtils.cpp:1326) lmdb dir: D:\ArmoryData\Armory/databases
-INFO  - 1477771772: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 1477771773: (..\BlockUtils.cpp:1508) Executing: doInitialSyncOnLoad
-INFO  - 1477771773: (..\BitcoinP2P.cpp:783) Connected to Bitcoin node
-INFO  - 1477771773: (..\DatabaseBuilder.cpp:162) Reading headers from db
-ERROR - 1477771773: (..\StoredBlockObj.cpp:538) buffer is too small: 0 bytes. expected: 106
-ERROR - 1477771773: (..\BDM_mainthread.cpp:255) BDM thread failed: buffer is too small: 0 bytes. expected: 106



Title: Re: Armory 0.95 is out
Post by: goatpig on October 29, 2016, 08:51:34 PM
Clean up your database folder or use another --dbdir.


Title: Re: Armory 0.95 is out
Post by: goatpig on October 29, 2016, 08:52:38 PM
Pushed the fixes for 0.95.1 in dev. People who've had issues, please build and try. Looking to release tomorrow or Monday.


Title: Re: Armory 0.95 is out
Post by: visdude on October 29, 2016, 09:45:56 PM
Clean up your database folder or use another --dbdir.

1. You mean rebuild the Armory database from scratch?
2. --dbdir has the same effect as --datadir, right?



Title: Re: Armory 0.95 is out
Post by: visdude on October 30, 2016, 03:28:44 AM
Clean up your database folder or use another --dbdir.

ArmoryDB insists on still creating "dblog.txt" file in the default "Armory" folder location (C:\Users\username\AppData\Roaming\Armory) in spite of the arg that specifies the alternate directory. It was crashing on me the way it did because it needs the presence of an Armory folder at the default location to be able to create dblog.txt in it. Otherwise, it refuses to proceed.

Perhaps it can be fixed in 0.95.1 if it's not too late so it will be consistent (along with the rest of the files) when opting to move the Armory database folder to a different location.

Thanks for the assistance.




Title: Re: Armory 0.95 is out
Post by: goatpig on October 30, 2016, 10:43:43 AM
1. You mean rebuild the Armory database from scratch?
2. --dbdir has the same effect as --datadir, right?

1) Yes

2) No. The datadir is where your wallets, logs and setting files are, as well as where the /databases folder defaults to. --dbdir forces the the db folder to the path of your choosing.

ArmoryDB insists on still creating "dblog.txt" file in the default "Armory" folder location (C:\Users\username\AppData\Roaming\Armory) in spite of the arg that specifies the alternate directory. It was crashing on me the way it did because it needs the presence of an Armory folder at the default location to be able to create dblog.txt in it. Otherwise, it refuses to proceed.

Perhaps it can be fixed in 0.95.1 if it's not too late so it will be consistent (along with the rest of the files) when opting to move the Armory database folder to a different location.

Thanks for the assistance.

Log files do not go in the dbdir. If you want to use a custom datadir and a custom dbdir, use both command line arguments together. You do not need to provide the DB with the same datadir as the client, i.e. it doesn't need the wallets, settings and other log files to operate.

However, the db needs a valid datadir (it won't create it for you). There isn't much I can change here. The issue you were experiencing with the log file is simply the first failure in line when the db lacks a valid datadir. Side stepping that one will only bump you to the next failure.

If you do not want to point the DB to the same datadir as the client, you can start the db directly with --datadir="/newpath" and it will set the db by default to /newpath/databases. If you let the client spawn the DB for you, the client will always push its own datadir to the DB, in which case you may want to use a custom dbdir.


Title: Re: Armory 0.95 is out
Post by: visdude on October 30, 2016, 02:57:17 PM
1. You mean rebuild the Armory database from scratch?
2. --dbdir has the same effect as --datadir, right?

1) Yes

2) No. The datadir is where your wallets, logs and setting files are, as well as where the /databases folder defaults to. --dbdir forces the the db folder to the path of your choosing.

ArmoryDB insists on still creating "dblog.txt" file in the default "Armory" folder location (C:\Users\username\AppData\Roaming\Armory) in spite of the arg that specifies the alternate directory. It was crashing on me the way it did because it needs the presence of an Armory folder at the default location to be able to create dblog.txt in it. Otherwise, it refuses to proceed.

Perhaps it can be fixed in 0.95.1 if it's not too late so it will be consistent (along with the rest of the files) when opting to move the Armory database folder to a different location.

Thanks for the assistance.

Log files do not go in the dbdir. If you want to use a custom datadir and a custom dbdir, use both command line arguments together. You do not need to provide the DB with the same datadir as the client, i.e. it doesn't need the wallets, settings and other log files to operate.

However, the db needs a valid datadir (it won't create it for you). There isn't much I can change here. The issue you were experiencing with the log file is simply the first failure in line when the db lacks a valid datadir. Side stepping that one will only bump you to the next failure.

If you do not want to point the DB to the same datadir as the client, you can start the db directly with --datadir="/newpath" and it will set the db by default to /newpath/databases. If you let the client spawn the DB for you, the client will always push its own datadir to the DB, in which case you may want to use a custom dbdir.


datadir, --datadir, dbdir, --dbdir, custom datadir, custom dbdir, DB, client, etc. I'm even more confused.

Anyway, here's what I got and what I have experienced:

My ArmoryQt shorcut arg: "C:\Program Files (x86)\Armory\ArmoryQt.exe" --satoshi-datadir="D:\BitcoinData\Bitcoin" --datadir="D:\ArmoryData\Armory". The contents of the "Armory" folder on this alternate path are the "databases" folder, armorycpplog.txt, armorylog.txt, ArmorySettings.txt and my watchonly wallet files.

With the above setup, ArmoryQt runs just fine and properly spawns ArmoryDB but with a caveat: an "Armory" folder must still exist at the default location (i.e. C:\Users\username\AppData\Roaming\Armory) because it insists on having the "dblog.txt" file reside there in spite of the arg that specifies the alternate directory/location. Otherwise, it hangs as before.

I can live with it. I have a functional Armory after all but it would be nice to have it create and look for the "dblog.txt" file in the alternate "Armory" folder location as defined in the shortcut arg above; where it should reside together with the rest of the log files. Is there anything I can change in or add to my shortcut arg to achieve this? If not, no biggie. It's not pretty but I can live with it.



Title: Re: Armory 0.95 is out
Post by: goatpig on October 30, 2016, 03:13:57 PM
With the above setup, ArmoryQt runs just fine and properly spawns ArmoryDB but with a caveat: an "Armory" folder must still exist at the default location (i.e. C:\Users\username\AppData\Roaming\Armory) because it insists on having the "dblog.txt" file reside there. Otherwise, it hangs as before.

That's quite a different situation here from what I had understood. Are you saying the DB won't put its log file in the explicit datadir? That's a bug, not a design choice. I'll try to reproduce on my end and fix it for the point release.


Title: Re: Armory 0.95 is out
Post by: Carlton Banks on October 30, 2016, 04:37:58 PM
Pushed the fixes for 0.95.1 in dev. People who've had issues, please build and try. Looking to release tomorrow or Monday.

Whonix is fixed for me. Coin control is improved, but not fixed.

First pick from a multi input address respects the users choice (which is fixed compared to previous behaviour). Changing one's mind after hitting accepts reveals the bug, and it seems similar to before: all the inputs from the address of the intended selected input appear to get selected, but quickly scrolling down the list shows that not quite all the inputs in fact are selected. It seems that random inputs (only at the same address as any inputs picked originally by the user) are left unselected, but whether that does really conform to some pattern I can't say.


Title: Re: Armory 0.95 is out
Post by: visdude on October 30, 2016, 07:53:19 PM
With the above setup, ArmoryQt runs just fine and properly spawns ArmoryDB but with a caveat: an "Armory" folder must still exist at the default location (i.e. C:\Users\username\AppData\Roaming\Armory) because it insists on having the "dblog.txt" file reside there. Otherwise, it hangs as before.

That's quite a different situation here from what I had understood. Are you saying the DB won't put its log file in the explicit datadir? That's a bug, not a design choice. I'll try to reproduce on my end and fix it for the point release.

Correct. The DB won't put its log file (dblog.txt) in the explicit datadir (which I usually refer to as the alternate location/directory/path) as specified in the arg. Furthermore, if it cannot detect an "Armory" folder still at the default location to put the dblog.txt file into, that's when it hangs. It requires it.



Title: Re: Armory 0.95 is out
Post by: goatpig on October 30, 2016, 07:58:39 PM
First pick from a multi input address respects the users choice (which is fixed compared to previous behaviour). Changing one's mind after hitting accepts reveals the bug, and it seems similar to before: all the inputs from the address of the intended selected input appear to get selected, but quickly scrolling down the list shows that not quite all the inputs in fact are selected. It seems that random inputs (only at the same address as any inputs picked originally by the user) are left unselected, but whether that does really conform to some pattern I can't say.

Correct. The DB won't put its log file (dblog.txt) in the explicit datadir (which I usually refer to as the alternate location/directory/path) as specified in the arg. Furthermore, if it cannot detect an "Armory" folder still at the default location to put the dblog.txt file into, that's when it hangs. It requires it.

Both these should be fixed in dev, please test and report.


Title: Re: Armory 0.95 is out
Post by: visdude on October 30, 2016, 08:08:19 PM

Both these should be fixed in dev, please test and report.

Sorry, I'm not familiar with the procedure. Do you mean test for the bug in the next release and report accordingly? Please elaborate.



Title: Re: Armory 0.95 is out
Post by: goatpig on October 30, 2016, 08:14:32 PM
Sorry, I'm not familiar with the procedure. Do you mean test for the bug in the next release and report accordingly? Please elaborate.

I mean pull the code from dev, build from source and test for the bug again. If you can't build from source, you're left with crossing your fingers and waiting for the next build.


Title: Re: Armory 0.95 is out
Post by: visdude on October 30, 2016, 08:27:58 PM
Sorry, I'm not familiar with the procedure. Do you mean test for the bug in the next release and report accordingly? Please elaborate.

I mean pull the code from dev, build from source and test for the bug again. If you can't build from source, you're left with crossing your fingers and waiting for the next build.

It would have to be the latter (crossing fingers) as I don't know how to pull code from dev let alone build from source.



Title: Re: Armory 0.95 is out
Post by: goatpig on October 30, 2016, 08:31:09 PM
https://github.com/goatpig/BitcoinArmory/blob/dev/windowsbuild/Windows_build_notes.md

There are some minimal instructions here if you'd like to spend the day battling it =D


Title: Re: Armory 0.95 is out
Post by: visdude on October 31, 2016, 01:02:47 AM
https://github.com/goatpig/BitcoinArmory/blob/dev/windowsbuild/Windows_build_notes.md

There are some minimal instructions here if you'd like to spend the day battling it =D

I'm very interested to learn once I can devote some time to it. Currently, I'm hardly getting by just trying to re-familiarize myself with a Linux install I tinkered around with late last year (a futile attempt to learn) so I can figure out how to generate wallet addresses for that new over-hyped/overpriced crypto that just launched whose initial price dropped about 70% already. I'm hoping to fire up my old boxes and mine some hoping to catch the tail end of the dump.  ;D



Title: Re: Armory 0.95 is out
Post by: Carlton Banks on October 31, 2016, 02:09:04 AM
First pick from a multi input address respects the users choice (which is fixed compared to previous behaviour). Changing one's mind after hitting accepts reveals the bug, and it seems similar to before: all the inputs from the address of the intended selected input appear to get selected, but quickly scrolling down the list shows that not quite all the inputs in fact are selected. It seems that random inputs (only at the same address as any inputs picked originally by the user) are left unselected, but whether that does really conform to some pattern I can't say.

Both these should be fixed in dev, please test and report.

You've got the coin control fixed, given it a fair amount of testing now. Wallet filter in the main tx window is broken for me.

A few minor things; dbLog.txt didn't get created while I was testing the Db building with Whonix/Qubes. That drew my attention to the progress bars: headers stage is too indecisive/imprecise in it's estimates, and the Tx hash resolution stage has a kind of crazy strobe effect as well as supremely eccentric estimates (started at 10 seconds, stayed there for 10 seconds, stayed at 1 second for a minute etc). One last minor: uncommented tx's used to inherit the label of the address they're associated with instead of just being fully blank.


Title: Re: Armory 0.95 is out
Post by: goatpig on October 31, 2016, 09:30:43 PM
Great, I just realized my response was never posted, thanks to the DDoS episode.

Quote
A few minor things; dbLog.txt didn't get created while I was testing the Db building with Whonix/Qubes.

The first line the db outputs in the terminal is the db log path. Double check against that and let me know.

Quote
That drew my attention to the progress bars: headers stage is too indecisive/imprecise in it's estimates, and the Tx hash resolution stage has a kind of crazy strobe effect as well as supremely eccentric estimates (started at 10 seconds, stayed there for 10 seconds, stayed at 1 second for a minute etc).

The progress bars were designed in 0.92 when the DB was much slower. I did not change anything to the underlying ETA code, just plugged it into the existing code. I will have overhaul that stuff at some point. Not a priority right now though.

Quote
One last minor: uncommented tx's used to inherit the label of the address they're associated with instead of just being fully blank.

That and the other minor features that were not replicated in this version will be fixed in 0.95.2.

For now, I have one user reporting a crash. I am waiting on his input in order to fix that one, then I'll release 0.95.1


Title: Re: Armory 0.95 is out
Post by: Carlton Banks on November 01, 2016, 12:14:57 PM
The first line the db outputs in the terminal is the db log path. Double check against that and let me know.

Yes, that happens reliably. My description was inadequate: I tested the Db build using Whonix, and dbLog.txt was'n't created that test-run, but was created the next time I ran Armory. Because using the Linux tail command with dbLog.txt is the best way to view the Db build progress, I'm double certain that it wasn't created during that 1st test run, despite that being otherwise successful.

The progress bars were designed in 0.92 when the DB was much slower. I did not change anything to the underlying ETA code, just plugged it into the existing code. I will have overhaul that stuff at some point. Not a priority right now though.

Yep, I was expecting wacky behaviour, seeing as you warned us about that.

That and the other minor features that were not replicated in this version will be fixed in 0.95.2.

For now, I have one user reporting a crash. I am waiting on his input in order to fix that one, then I'll release 0.95.1

Looking forward to it all. Hail goatpig, etc.


Title: Re: Armory 0.95 is out
Post by: OtisG on November 01, 2016, 11:11:22 PM
Howdy,
I need help please.

I installed the new BitCoin Core v0.13.1 with no problems at all. 
Runs great.

The problem is the new Armory 0.95.

I installed the Armory 0.95 update (long time Armory user), but the "Initialize Bitcoin Engine" is just spinning.
It never gets to "Build Databases" or "Scan Transaction History"
I've let it run 8hrs to no effect, so definitely not working correctly.
I see that it has successfully spawned BitcoinD under task manager.
This is running under Windows 7 x64 bit.

Any thoughts?

Thanks in advance!
OtisG



Title: Re: Armory 0.95 is out
Post by: achow101 on November 01, 2016, 11:21:22 PM
Howdy,
I need help please.

I installed the new BitCoin Core v0.13.1 with no problems at all. 
Runs great.

The problem is the new Armory 0.95.

I installed the Armory 0.95 update (long time Armory user), but the "Initialize Bitcoin Engine" is just spinning.
It never gets to "Build Databases" or "Scan Transaction History"
I've let it run 8hrs to no effect, so definitely not working correctly.
I see that it has successfully spawned BitcoinD under task manager.
This is running under Windows 7 x64 bit.

Any thoughts?

Thanks in advance!
OtisG


Armory 0.95 build for Windows was messed up. You can downgrade to 0.94.1, grab the guardian.exe file from 0.94.1 and put it in the installation folder for Armory, or run Bitcoin Core without Armory management. To run without Armory management, start Armory and go to File > Settings and uncheck "Let armory manage bitcoin core". Then start Bitcoin Core and restart Armory.


Title: Re: Armory 0.95 is out
Post by: OtisG on November 01, 2016, 11:56:44 PM
Howdy,
I need help please.

I installed the new BitCoin Core v0.13.1 with no problems at all. 
Runs great.

The problem is the new Armory 0.95.

I installed the Armory 0.95 update (long time Armory user), but the "Initialize Bitcoin Engine" is just spinning.
It never gets to "Build Databases" or "Scan Transaction History"
I've let it run 8hrs to no effect, so definitely not working correctly.
I see that it has successfully spawned BitcoinD under task manager.
This is running under Windows 7 x64 bit.

Any thoughts?

Thanks in advance!
OtisG


Armory 0.95 build for Windows was messed up. You can downgrade to 0.94.1, grab the guardian.exe file from 0.94.1 and put it in the installation folder for Armory, or run Bitcoin Core without Armory management. To run without Armory management, start Armory and go to File > Settings and uncheck "Let armory manage bitcoin core". Then start Bitcoin Core and restart Armory.

Thanks for your quick reply!

I unchecked the management options.  Launching Armory without Bitcoin Core management launches ArmoryDB which then crashes 5 seconds later.
Instead of that option, I've downgraded Armory back to 0.93.3 where I was before.

Are the Windows 7 related issues expected to be resolved in 0.95.1?  I sure hope so.  I have cold storage coin, so this is very important for me.

OtisG


Title: Re: Armory 0.95 is out
Post by: achow101 on November 01, 2016, 11:59:21 PM
Thanks for your quick reply!

I unchecked the management options.  Launching Armory without Bitcoin Core management launches ArmoryDB which then crashes 5 seconds later.
Instead of that option, I've downgraded Armory back to 0.93.3 where I was before.
You should use 0.94.1 instead.

Can you provide the log file?

Are the Windows 7 related issues expected to be resolved in 0.95.1?  I sure hope so.  I have cold storage coin, so this is very important for me.

OtisG
It should be fixed. However, if this is a new issue, we need to know so that it can be fixed ASAP.


Title: Re: Armory 0.95 is out
Post by: OtisG on November 02, 2016, 12:08:18 AM
Sure - are you referring to uploading Armoryqt.exe.log ?



Title: Re: Armory 0.95 is out
Post by: achow101 on November 02, 2016, 12:11:25 AM
Sure - are you referring to uploading Armoryqt.exe.log ?
The file from File > Export Log File.


Title: Re: Armory 0.95 is out
Post by: OtisG on November 02, 2016, 12:27:57 AM
Sure - are you referring to uploading Armoryqt.exe.log ?
The file from File > Export Log File.

Got the file. What's the best way to get it to you.  I don't see a file upload option among the icons under the reply option.
OtisG


Title: Re: Armory 0.95 is out
Post by: achow101 on November 02, 2016, 12:31:34 AM
Sure - are you referring to uploading Armoryqt.exe.log ?
The file from File > Export Log File.

Got the file. What's the best way to get it to you.  I don't see a file upload option among the icons under the reply option.
OtisG
Open the file in a text editor. Copy the contents to http://pastebin.com/. If it is too large, get as much as you can from the bottom. Then post the link to the paste here.


Title: Re: Armory 0.95 is out
Post by: visdude on November 02, 2016, 06:01:11 AM
Howdy,
I need help please.

I installed the new BitCoin Core v0.13.1 with no problems at all.  
Runs great.

The problem is the new Armory 0.95.

I installed the Armory 0.95 update (long time Armory user), but the "Initialize Bitcoin Engine" is just spinning.
It never gets to "Build Databases" or "Scan Transaction History"
I've let it run 8hrs to no effect, so definitely not working correctly.
I see that it has successfully spawned BitcoinD under task manager.
This is running under Windows 7 x64 bit.

Any thoughts?

Thanks in advance!
OtisG



I have W7 x64 as well and also ran into a hitch when I upgraded to 0.13.1/0.95. The following steps somehow worked for me (YMMV):

1. Rename old Armory data folder (serves as backup).

2. Uninstall the previous version and install Armory 0.95 from scratch.

3. Start Armory 0.95 in Offline Mode and "Skip" creating a wallet. Change settings accordingly [File/Settings...] and save it. Close Armory.

4. Copy watchonly wallet files from the old Armory data folder to the new one.

5. Start Bitcoin-Qt and let it sync.

6. Start Armory 0.95 and let it build a new DB.

As long as you don't intend to move your Armory data folder to a new location (refer to an issue I presented earlier on this thread), 0.95 should be peachy for you from here on.





Title: Re: Armory 0.95 is out
Post by: OtisG on November 03, 2016, 01:49:46 AM
Visdude, thanks for the suggestions.  I did those steps, but to no avail.  Same endless spinning wheel.

Achow, thanks for your help, but I think i'll just wait on 0.95.1.  
If it doesn't work, I'll move on to a different wallet.
I just don't have time for endless debugging.



Title: Re: Armory 0.95 is out
Post by: OtisG on November 03, 2016, 08:51:59 PM
The good news is I successfully upgraded from 93.3 to 94.1.
It failed at first, then I read a blurb to rename the ...\armory\databases directory first for any upgrade from 93.3
Then the upgrade worked.

AND, it saved me 85GB of SSD space  :o after I moved the renamed directory to an archive drive.

I then tried updating to 95.0 from 94.1, but I get the same spinning initializing wheel.
Back down to 94.1 for now.
I'll wait for 95.1 to see if that resolves the upgrade problem from 94.1.


Title: Re: Armory 0.95 is out
Post by: droark on November 03, 2016, 09:29:25 PM
I then tried updating to 95.0 from 94.1, but I get the same spinning initializing wheel.

IIRC, you need to clear the DB again when upgrading to 0.95, like you did when upgrading to 0.94. Try that if 0.95.1 (which should be out very soon) doesn't fix your woes.


Title: Re: Armory 0.95 is out
Post by: gangtraet on November 03, 2016, 09:30:46 PM
Just did the same upgrade.  You have to remove the database directory again.  It stays small (but not quite as small as in 0.94.1, although still tiny compared to the bad old days).


Title: Re: Armory 0.95 is out
Post by: OtisG on November 04, 2016, 11:41:31 AM
I just installed 0.95.1 AND IT WORKS, woohoo! 
Back in business.

Thanks Armory Developers!


Title: Re: Armory 0.95 is out
Post by: PeZ on November 06, 2016, 12:18:53 AM
I tried doing a clean install of 0.95.1 and follow the post above, but no luck. Still stuck on build databases and doesn't build the database.

It only works if I start bitcoin-qt and Armory separately.


Title: Re: Armory 0.95 is out
Post by: jammers on November 06, 2016, 03:16:18 PM
hi there,

reddit pointed me to the updated armory, so glad it's still going! I've been trying to upgrade from .93 and bitcoin .11 to the latest version .95.1 and the latest core 13.1

I've had a problem whereby it's trying to scan the blockchain (I know it's up to date), and saying 1 second on scanning transactions and not going further. I tried to rescan and rebuild databases, and nothing happens when I reboot (although I did get the pop up welcome message).

I'm going to try and reinstall completely to see if that fixes it, but if I'm doing something obviously wrong, please let me know.

Thanks

Jamie


Title: Re: Armory 0.95 is out
Post by: achow101 on November 06, 2016, 03:33:15 PM
I tried doing a clean install of 0.95.1 and follow the post above, but no luck. Still stuck on build databases and doesn't build the database.

It only works if I start bitcoin-qt and Armory separately.
Do you see the progress bar move at all or does it stay stuck at something like 1%?

hi there,

reddit pointed me to the updated armory, so glad it's still going! I've been trying to upgrade from .93 and bitcoin .11 to the latest version .95.1 and the latest core 13.1

I've had a problem whereby it's trying to scan the blockchain (I know it's up to date), and saying 1 second on scanning transactions and not going further. I tried to rescan and rebuild databases, and nothing happens when I reboot (although I did get the pop up welcome message).

I'm going to try and reinstall completely to see if that fixes it, but if I'm doing something obviously wrong, please let me know.

Thanks

Jamie
First, you need to delete the entire folder named "databases" inside of armory's datadir. Then try again.

If you do not see any of the progress bars moving and stuck at 1%, that usually means that the ArmoryDB isn't running or crashed. Stop Armory and make sure that there are no processes named ArmoryDB running. Then try again.



Title: Re: Armory 0.95 is out
Post by: Carlton Banks on November 06, 2016, 04:22:57 PM
I've had a problem whereby it's trying to scan the blockchain (I know it's up to date), and saying 1 second on scanning transactions and not going further. I tried to rescan and rebuild databases, and nothing happens when I reboot (although I did get the pop up welcome message).

This might be just a problem with the progress bars only, I've experienced something similar.

Does the process (building Db/tx scan) fill all the progress bars convincingly until it gets to the transaction scan stage? If yes, I would leave it to continue despite how unconvincing the cosmetics are, they're literally just that, cosmetic. The best way to follow the progress reliably is to view the dbLog.txt file continuously (tail -f <path/filename> if you're using Linux).


Title: Re: Armory 0.95 is out
Post by: PeZ on November 06, 2016, 10:58:27 PM
I tried doing a clean install of 0.95.1 and follow the post above, but no luck. Still stuck on build databases and doesn't build the database.

It only works if I start bitcoin-qt and Armory separately.
Do you see the progress bar move at all or does it stay stuck at something like 1%?
http://i.imgur.com/Pmo08Uq.jpg
Bitcoind is running in the background, but ArmoryDB isn't.

I change the setting in Armory to not have bitcoind running. I start bitcoin-qt, let it sync, then run Armory. ArmoryDB command window immediately pops up and connects to bitcoin-qt. It manages the Armory database then it becomes fully functional.


Title: Re: Armory 0.95 is out
Post by: DLS123 on November 07, 2016, 12:23:08 AM
Getting error "DB version Mismatch use another dbdir"  Any help is appreciated.


Title: Re: Armory 0.95 is out
Post by: achow101 on November 07, 2016, 12:27:44 AM
Getting error "DB version Mismatch use another dbdir"  Any help is appreciated.
Go to the armory data directory (os dependent) and delete the "databases" folder. Then start Armory.


Title: Re: Armory 0.95 is out
Post by: jammers on November 07, 2016, 09:25:28 PM

hi there,

reddit pointed me to the updated armory, so glad it's still going! I've been trying to upgrade from .93 and bitcoin .11 to the latest version .95.1 and the latest core 13.1

I've had a problem whereby it's trying to scan the blockchain (I know it's up to date), and saying 1 second on scanning transactions and not going further. I tried to rescan and rebuild databases, and nothing happens when I reboot (although I did get the pop up welcome message).

I'm going to try and reinstall completely to see if that fixes it, but if I'm doing something obviously wrong, please let me know.

Thanks

Jamie
First, you need to delete the entire folder named "databases" inside of armory's datadir. Then try again.

If you do not see any of the progress bars moving and stuck at 1%, that usually means that the ArmoryDB isn't running or crashed. Stop Armory and make sure that there are no processes named ArmoryDB running. Then try again.


[/quote]

So I have the same problem as PeZ.

However, I'll try to log into C:\Users\xxx\AppData\Roaming\Armory and delete the databases folder.

Then when I boot up Armory, it does the wallet consistency check, Initialising Bitcoin Engine bar is full green, and scan transaction history says 0% and 1 second.

I do see the databases folder being created, but there aren't any files in it. I'll leave it here for a couple of minutes and see if it starts to boot



Title: Re: Armory 0.95 is out
Post by: achow101 on November 07, 2016, 09:33:57 PM
So I have the same problem as PeZ.

However, I'll try to log into C:\Users\xxx\AppData\Roaming\Armory and delete the databases folder.

Then when I boot up Armory, it does the wallet consistency check, Initialising Bitcoin Engine bar is full green, and scan transaction history says 0% and 1 second.

I do see the databases folder being created, but there aren't any files in it. I'll leave it here for a couple of minutes and see if it starts to boot
Stop Armory and open up task manager. Make sure that any process with the name "ArmoryDB" is killed. Then try again.


Title: Re: Armory 0.95 is out
Post by: jammers on November 07, 2016, 10:17:31 PM
checked again and there's no movement.

I did check for processes, can't see any for ArmoryDB


Title: Re: Armory 0.95 is out
Post by: achow101 on November 07, 2016, 10:38:26 PM
checked again and there's no movement.

I did check for processes, can't see any for ArmoryDB
Log files please


Title: Re: Armory 0.95 is out
Post by: DLS123 on November 08, 2016, 12:29:11 AM
Getting error "DB version Mismatch use another dbdir"  Any help is appreciated.
Go to the armory data directory (os dependent) and delete the "databases" folder. Then start Armory.

Thanks so much. Have one more quick question.  If I do a "receive" and enter in a comment, when that address gets a deposit the comment doesn't show up in the comments section.  Anyone have any ideas?

Thanks


Title: Re: Armory 0.95 is out
Post by: achow101 on November 08, 2016, 12:30:29 AM
Thanks so much. Have one more quick question.  If I do a "receive" and enter in a comment, when that address gets a deposit the comment doesn't show up in the comments section.  Anyone have any ideas?

Thanks
It's a known bug.


Title: Re: Armory 0.95 is out
Post by: RGBKey on November 12, 2016, 05:13:07 AM
So right now the way to get armory to run is to disable it running core in the options, have core running then start armory?


Title: Re: Armory 0.95 is out
Post by: goatpig on November 12, 2016, 02:06:45 PM
So right now the way to get armory to run is to disable it running core in the options, have core running then start armory?

Fixed in 0.95.1


Title: Re: Armory 0.95 is out
Post by: RGBKey on November 12, 2016, 06:26:04 PM
So right now the way to get armory to run is to disable it running core in the options, have core running then start armory?

Fixed in 0.95.1
I just freshly installed armory and I've been having trouble with it still. When I don't run bitcoin core outside of armory (if I keep the option checked) it gets stuck on Initializing Bitcoin Engine.


Title: Re: Armory 0.95 is out
Post by: jammers on November 13, 2016, 07:38:57 PM
Howdy,
I need help please.

I installed the new BitCoin Core v0.13.1 with no problems at all. 
Runs great.

The problem is the new Armory 0.95.

I installed the Armory 0.95 update (long time Armory user), but the "Initialize Bitcoin Engine" is just spinning.
It never gets to "Build Databases" or "Scan Transaction History"
I've let it run 8hrs to no effect, so definitely not working correctly.
I see that it has successfully spawned BitcoinD under task manager.
This is running under Windows 7 x64 bit.

Any thoughts?

Thanks in advance!
OtisG


Armory 0.95 build for Windows was messed up. You can downgrade to 0.94.1, grab the guardian.exe file from 0.94.1 and put it in the installation folder for Armory, or run Bitcoin Core without Armory management. To run without Armory management, start Armory and go to File > Settings and uncheck "Let armory manage bitcoin core". Then start Bitcoin Core and restart Armory.


I'm trying this now as well. I heard that Armory development is back up and running, so am trying to get things up and running using .95.1 and .13.1.

I'd had a lot of problems in the early posts of this thread (initialising bitcoin engine, 1 second), but disabling auto management of core, loading that up and syncing and then loading up Armory made armoryDB show, and start creating the databases.

I did have an issue before, when restoring an old paper backup where it was showing a balance, but not addresses. So now I can get armory going and see if it'll load my addresses from my paper backup, and get using Armory again.

I'll update when I can get into it, or report any issues in the meantime.


Title: Re: Armory 0.95 is out
Post by: PeZ on November 13, 2016, 10:10:27 PM
So right now the way to get armory to run is to disable it running core in the options, have core running then start armory?

Fixed in 0.95.1
Ever since ArmoryDB was separated out of Armory, I have been forced to run Core and Armory separately.


Title: Re: Armory 0.95 is out
Post by: goatpig on November 13, 2016, 10:45:38 PM
Ever since ArmoryDB was separated out of Armory, I have been forced to run Core and Armory separately.

That's the preferred mode in any case. You may be experiencing path mismatches with auto bitcoind. That mode will change a lot under the hood next release, and I will also improve on the pathing customization. For now, bear with this.


Title: Re: Armory 0.95 is out
Post by: jammers on November 18, 2016, 12:41:16 PM
ok, so good and bad news. Firstly, I didn't have to redownload the blockchain (yay), and then it's spent the time scanning the wallets (paper backup), and then putting some of the addresses I had used into the wallet. Now I know I saw somewhere there was the ability for me to set how many addresses to generate (i read somewhere 50 or 100).

But I see another issue with the paper backup import. Any of the addresses I had before that have a zero balance now, but had transactions there aren't being shown. I know I have a digital backup somewhere, but that's definitely an issue I want to report. Is there a way I can get it to generate a couple of hundred wallets and see if it picks up the ones that have been used before? I don't mind testing this a few times if it can help, but I know a good few people have probably laminated paper backups

Thanks

Jamie

P.S. The booting speed now is pretty quick, wayyyyy faster than before, and I'm on a lower spec machine than I was in the past.


Title: Re: Armory 0.95 is out
Post by: goatpig on November 18, 2016, 02:46:09 PM
You should import your wallets offline first, then start online so as to let Armory scan the new addresses in a bulk. The missing history indicates the addresses either need to be scanned, or your blockchain copy is missing some blocks (what'st he top block displaying in the bottom right of Armory?)


Title: Re: Armory 0.95 is out
Post by: jammers on November 18, 2016, 04:07:18 PM
Ok, so I'll remove the wallets, re-import them when offline, and then try restoring the paper backup again

The bottom right does say it's synced to the latest block

And it's not about the missing history as such, it's more that it's showing a load of addresses, but ones which I know had transactions on them weren't picked up


Title: Re: Armory 0.95 is out
Post by: goatpig on November 18, 2016, 04:09:44 PM
Ok, so I'll remove the wallets, re-import them when offline, and then try restoring the paper backup again

You don't need to do that, you can just do a Help -> Rescan databases


Title: Re: Armory 0.95 is out
Post by: jammers on November 18, 2016, 05:12:16 PM
ok, i'll do that now while i'm out


Title: Re: Armory 0.95 is out
Post by: jammers on November 18, 2016, 05:36:42 PM
just a quick question @goatpig should I have core open or closed when I do the rescan?


Title: Re: Armory 0.95 is out
Post by: achow101 on November 18, 2016, 06:44:31 PM
just a quick question @goatpig should I have core open or closed when I do the rescan?
Open. Core should always be running when you run Armory.


Title: Re: Armory 0.95 is out
Post by: padrino on January 05, 2017, 04:37:07 AM
Trying to run 0.95.1 on OSX 10.10 with the provided binary, on startup it's failing with "ImportError: cannot import name sha1", I assumed the bundle had all needed modules, or are some pulled from the system? I haven't run down the reason the import is failing but thought I would paste in case it was a known issue.


Title: Re: Armory 0.95 is out
Post by: droark on January 05, 2017, 08:16:09 AM
Trying to run 0.95.1 on OSX 10.10 with the provided binary, on startup it's failing with "ImportError: cannot import name sha1", I assumed the bundle had all needed modules, or are some pulled from the system? I haven't run down the reason the import is failing but thought I would paste in case it was a known issue.

You'll need to run "brew install openssl" (https://github.com/goatpig/BitcoinArmory/blob/dev/README_OSX.md).


Title: Re: Armory 0.95 is out
Post by: TraderTimm on February 15, 2017, 12:49:18 AM
Running the newest release on Ubuntu/Trusty (don't mock, 0.93 worked fine).

Got "dbdir error - fortunately I backed up my old installation to another directory.

Wiped everything from the old install .armory directory - installed using software manager for amd64 deb linux package.

I see a new .armory hidden directory created.

Start Armory, loads quickly. I didn't have it set to start anything (bitcoind) on its own, so I closed it.

Re-started Armory with bitcoind running, and my watching-wallet in the .armory directory -- it sees it, does a wallet consistency check, says its all fine.

Then the dreaded DB error pops up and wants me to close Armory.

Bitcoin-qt 0.13.1 and Bitcoind work just fine, sync with no issues and I have the latest blockheight.

Is there somewhere else its looking for the Armory database? The only hidden folder I was aware of is in my user directory under .armory/databases -- and even when I wipe that out completely it still chokes with a DB error.

Just bummed because I was using a prior version with no problems.


Title: Re: Armory 0.95 is out
Post by: achow101 on February 15, 2017, 01:02:35 AM
Running the newest release on Ubuntu/Trusty (don't mock, 0.93 worked fine).

Got "dbdir error - fortunately I backed up my old installation to another directory.

Wiped everything from the old install .armory directory - installed using software manager for amd64 deb linux package.

I see a new .armory hidden directory created.

Start Armory, loads quickly. I didn't have it set to start anything (bitcoind) on its own, so I closed it.

Re-started Armory with bitcoind running, and my watching-wallet in the .armory directory -- it sees it, does a wallet consistency check, says its all fine.

Then the dreaded DB error pops up and wants me to close Armory.

Bitcoin-qt 0.13.1 and Bitcoind work just fine, sync with no issues and I have the latest blockheight.

Is there somewhere else its looking for the Armory database? The only hidden folder I was aware of is in my user directory under .armory/databases -- and even when I wipe that out completely it still chokes with a DB error.

Just bummed because I was using a prior version with no problems.


Log files please.


Title: Re: Armory 0.95 is out
Post by: TraderTimm on February 15, 2017, 03:25:03 PM
Log files please.

That won't be easy given how I have this system set up. I'll just roll back to the working prior version and wait until there's a fix that handles the problem. I was surprised that the database 0.93 is manipulating is 72GB in size -- and that's just for Armory, not the blockchain storage size, obviously.

I'll just use the slow-poke version for a while I guess.

Thanks.


Title: Re: Armory 0.95 is out
Post by: TraderTimm on February 28, 2017, 04:01:21 PM
Just an update - was going to roll back to 0.93 when I decided on a whim to start up 0.95 again.

And... it worked!

I had wiped the database directory entirely, started and synced bitcoind prior to launching Armory. My guess is one of my prior actions had fixed something, but I didn't bother to reboot the linux box since that is not usually needed. I guess I had to power-cycle it, because that did the trick.

Anyway, its much faster, so thanks very much for that!


Title: Re: Armory 0.95 is out
Post by: goatpig on February 28, 2017, 04:59:39 PM
Just an update - was going to roll back to 0.93 when I decided on a whim to start up 0.95 again.

And... it worked!

I had wiped the database directory entirely, started and synced bitcoind prior to launching Armory. My guess is one of my prior actions had fixed something, but I didn't bother to reboot the linux box since that is not usually needed. I guess I had to power-cycle it, because that did the trick.

Anyway, its much faster, so thanks very much for that!


Please consider participating in the 0.96 testing phase =)


Title: Re: Armory 0.95 is out
Post by: TraderTimm on March 01, 2017, 04:23:27 PM
Please consider participating in the 0.96 testing phase =)

I'm avidly following your progress :) Thanks for all you've done to continue Armory, its one of the best out there.


Title: Re: Armory 0.95 is out
Post by: TraderTimm on March 11, 2017, 04:50:32 PM
One small thing I've noticed -- In the main program window, my watching wallet balance is correct (Under the "Available Wallets" Section of the GUI), but the lower right totals of "Maximum Funds, Spendable Funds, Unconfirmed" is zero.

When I click on my watching-wallet to get the "Wallet Properties" window, my Max/Spendable is the current balance, with Unconfirmed being zero.

Its just a bit disconcerting that the main display doesn't update with the balances -- and yes, I'm fully synced with the blockchain when I tried this.

Edit -- Naturally just AFTER I post this, the totals updated in the main window.... I guess there's just a bit of a delay somehow? Worth mentioning anyway...



Title: Re: Armory 0.95 is out
Post by: Carlton Banks on March 11, 2017, 05:14:50 PM
This is goatpig's admirable pragmatism at work; there were still bugs like this in 0.95.x, but delaying the release to squash them wasn't really worth the trade-off of not getting the releases out. He's one man, doing the job of several, and at this early stage for the new code in Armory (which AFAIA was a significant re-write), it made more sense to let non-critical bugs slide. Alot of these have been dealt with for 0.96 so far, and certainly some aspect of unconfirmed balances was fixed in the last few days (I know not the details of that though)


Title: Re: Armory 0.95 is out
Post by: goatpig on March 11, 2017, 05:43:42 PM
but delaying the release to squash them wasn't really worth the trade-off of not getting the releases out

This ought to be the first time someone argues I release too fast!

TraderTimm: that stuff is fixed in 0.96


Title: Re: Armory 0.95 is out
Post by: TraderTimm on March 12, 2017, 03:35:45 PM
but delaying the release to squash them wasn't really worth the trade-off of not getting the releases out

This ought to be the first time someone argues I release too fast!

TraderTimm: that stuff is fixed in 0.96

I have to say that 0.95 is light-years faster than I could have ever believed. I only had to build the databases once, and afterward it updates VERY quickly. Thank you very much for your time and effort on this project. I sincerely appreciate your skill and talent.


Title: Re: Armory 0.95 is out
Post by: Flanagan on March 20, 2017, 02:27:37 PM
VERIFYING
armory_0.95.1_amd64.deb ?

Now that I got Lubuntu installed in another 64 system, I downloaded the package from https://btcarmory.com/0.95.1-release/

Don't see any information on verification at the site.
What release signature ?
What release signing key?

EDIT: Ok sorry, just saw the information at the site. Will try and report here my process of verification.

STEPS TO VERIFY I've done:

1) Import Armory Signing Key:
gpg --recv-keys --keyserver keyserver.ubuntu.com 4922589A
gpg: key 8C5211764922589A: public key "goatpig (Offline signing key for Armory releases) <moothecowlord@gmail.com>" imported
gpg: no ultimately trusted keys found
gpg: Total number processed: 1
gpg:               imported: 1

2) Download release signing key from: https://btcarmory.com/0.95.1-release/

3) shasum -c sha256sum.asc armory_0.95.1_amd64.deb

armory_0.95.1_amd64.deb: OK    <-- OK
shasum: armory_0.95.1_osx.tar.gz:
armory_0.95.1_osx.tar.gz: FAILED open or read
shasum: armory_0.95.1_win64.exe: No such file or directory
armory_0.95.1_win64.exe: FAILED open or read
shasum: WARNING: 20 lines are improperly formatted
shasum: WARNING: 2 listed files could not be read
shasum: armory_0.95.1_amd64.deb: no properly formatted SHA1 checksum lines found

3.1)
Compare the hash of the sha256sum.asc file with the one in the application package:
a) Inside the sha256sum.asc file:  
4d692a60afc114f4ccb230d11006c69af12ee37a0b7964b03caff90b6619b75c  armory_0.95.1_amd64.deb

b) sha256sum armory_0.95.1_amd64.deb
4d692a60afc114f4ccb230d11006c69af12ee37a0b7964b03caff90b6619b75c  armory_0.95.1_amd64.deb   <---inside the application package

They coincide so <-- OK


4)  gpg --verify
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

4d692a60afc114f4ccb230d11006c69af12ee37a0b7964b03caff90b6619b75c  armory_0.95.1_amd64.deb
9ec3803b914660c5fbecfd5b2d6e907f64d16f920cd648678137d307399beb8d  armory_0.95.1_osx.tar.gz
ccb495aa3a695e43ac04b4741dd8f8463d5349192a0f5db895dbd2e834e5844a  armory_0.95.1_win64.exe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJYGjjiAAoJEIxSEXZJIliaQ2EP/RwLphwj0z0o00VP/PGHzKYK
UmTHibof3ZavFF1orAdgWDayHoQCsZBcPy8fQcGWZ3zomhAqCC1lN496SHkkWQWH
TAYvMOsRlvMaaNIcoJ+jxyJzjmWd5+FjOEd/Uy9Au6DQFCqIEHTbjth/hyyUouaM
IxqudEiGAye2V5sIP8XWIWz6l8vq9OPKd4x3/F3NvlBY6jpAc81VxGFnfAZgIpW6
+in302WwIg61zG5AeVfju6BKJCREMvJvSvrdcrnK0UZDFm2jnl0IU1Q8omJFZXpG
EL06QBgO0+4aJ0rOu/RIIBzXJQgfj9Eul3ih0M6KbrImIAU3DlDKV3RTaNG9evCX
H5TtTKgux8Yuyljks5qu2WB7Cj8LtjbzPHMf4QT2SfavFpejJJFEAWyx2GdLTd5y
jZ95dwbPby59gyfwK3FNurgRduW+hjTGjTtZAk7CopkbrbLW4NzdjtHfKKzHmqid
yTI2PMCCjOLnAvTxEGKngmACQSvzDT9NN9ImWhf/E0IRKE7JtPPAp4U8xdC0NZDk
yIUP5A4D8d7FDpv8arK8v5PV4WyiCHLjyPRmt5kOc9AAUVr/7oPZO0FI4+VyY24X
ooOtuVmt66hTPyymmd0QUeulgl0PVqsJoyENjvx8H1Q8Wdo2rHseg06r2Q174Ckr
STBuW7eIR89uaLEsgjzC
=NJYO
-----END PGP SIGNATURE-----
gpg: Signature made mié 02 nov 2016 20:05:06 CET
gpg:                using RSA key 8C5211764922589A
gpg: Good signature from "goatpig (Offline signing key for Armory releases) <moothecowlord@gmail.com>" [unknown] <-- OK
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 745D 707F BA53 968B DF63  AA8D 8C52 1176 4922 589A


Title: Re: Armory 0.95 is out
Post by: goatpig on March 20, 2017, 02:57:34 PM
Just do

Code:
sha256sum armory_0.95.1_amd64.deb

This give you the hash for the package. Compare that with the hash in the signed file. If they match, check the signature on the hash file. If the sig is good, you got the right files.


Title: Re: Armory 0.95 is out
Post by: Flanagan on March 20, 2017, 03:15:50 PM
Thanks,
Updating my previous post with this command and results !


Title: Re: Armory 0.95 is out
Post by: goatpig on March 20, 2017, 03:20:42 PM
Quote
gpg: Good signature from "goatpig (Offline signing key for Armory releases) <moothecowlord@gmail.com>" [unknown] <--Take it as OK ! ?

Yes, good sig means the key (mine in this case) properly signed the data inside the "----- PGP SIGNED MESSAGE-----" encapsulation.


Title: Re: Armory 0.95 is out
Post by: Petete on April 13, 2017, 03:46:12 PM
Well, Flanagan's steps to verify differ in what's being said on the website as he uses pgp key 8C5211764922589A instead of  98832223. I guess both belong to goatpig?


Title: Re: Armory 0.95 is out
Post by: Petete on April 14, 2017, 07:41:45 AM
I have problems upgrading from 0.93.3 to 0.95.1 on Ubuntu 14.04.

What I do is:
- delete "databases" and "bittorrentcache" folders in .armory
- remove 0.93.3, install and start 0.95.1
- wait for the database being build (seems to work fine)
- see armory hanging at "Scanning transaction history" (showing no progress for hours)
- ArmoryDB will consume all available memory at this point
- close Armory, kill ArmoryDB process
- restart Armory
- it will finish to main screen, but this years transactions are missing, showing a wrong total sum of funds

This is on my backup computer. On my main computer, also with Ubuntu 14.04 and same wallets, ArmoryDB will also hang at "Scanning transaction history" but not consume all available memory. Also there are error messages when Armory is started from console. I can close Armory there with it shutting down ArmoryDB automatically. When I restart Armory, it completes and shows correct total funds.

I could just copy over everything from the main computer to backup computer, but havent't done so as I wanted to report the issue first.


Title: Re: Armory 0.95 is out
Post by: RoadStress on April 14, 2017, 03:19:03 PM
I thought this is a normal behavior. When you change or create new database Armory needs to scan all your wallets again against the new databases. That is a very resourceful task (hint: now you will understand why on-chain scaling is not efficient and why we need that part of transaction to be off-chain) and I think it needs all the RAM memory for faster processing. I would like to know if there is a cap on the amount of ram that it needs in order to speed things up, but you sound like you have very little ram available on your back-up machine. I think you will need to leave your computer online overnight or when until it finishes. I will take a while.

Maybe someone can teach us how or what can we copy from Armory from another computer that has all wallets synced.


Title: Re: Armory 0.95 is out
Post by: TraderTimm on April 14, 2017, 03:58:11 PM
Goatpig - Serious question that I hoped you might be able to briefly address.

This project - "Large Bitcoin Collider" - https://lbc.cryptoguru.org/stats - is searching keyspace and trying to find funds. While the statistics say their success is going to be very small, I was wondering if there were any features in Armory that might make their "rattle every doorknob until we find money" strategy that much more difficult.

Just curious what you think.

Thanks in advance...


Title: Re: Armory 0.95 is out
Post by: goatpig on April 14, 2017, 05:06:06 PM
I have problems upgrading from 0.93.3 to 0.95.1 on Ubuntu 14.04.

Make your own thread, post armorylog.txt and dbLog.txt

Quote
Maybe someone can teach us how or what can we copy from Armory from another computer that has all wallets synced.

A DB is bound to its blockchain data. If you copy the blockchain data over, you can copy the DB over as well. More often than not, the issue is your pathing though.

Quote
This project - "Large Bitcoin Collider" - https://lbc.cryptoguru.org/stats - is searching keyspace and trying to find funds. While the statistics say their success is going to be very small, I was wondering if there were any features in Armory that might make their "rattle every doorknob until we find money" strategy that much more difficult.

Basically a useless venture, but sure, I'll indulge:

1) Scanning the entire key space is idiotic. Waste of energy.

2) What kind of scripts are they even scanning for? 0.96 has quite a unique script type construct for compressed keys. It doesn't matter if they by some miracle within a miracle manage to reproduce your private key if they don't know what script hash to look for.

3) This protection (provided by the script hash) is incumbent on avoiding address reuse. As long as you fund a script hash and that script is exotic enough, chances are these type of pointless attacks won't even know what script to look for. If you reuse addresses (a signature reveals the public key), you are loosing the extra protection afforded by the script hash.

This is the main reason for avoiding address reuse btw.

4) Speaking of exotic scripts, you could construct a script that requires the resolution of an extra hash, or use 2-of-3 or 3-of-4 multisig for long term cold storage, if you are afraid there is an odd chance these clowns found one of your keys. Something like nested P2WSH 3-of-3 multisig with an empty IF branch would put your coins behind 2 hashes and 3 private keys.

5) If you are so inclined, you can create a wallet seed with custom entropy through the deck of cards GUI. That's assuming you don't trust the quality of the PRNG on your machine (that's advisable with Windows, since the code is closed source).


Title: Re: Armory 0.95 is out
Post by: Petete on April 14, 2017, 08:22:26 PM
I thought this is a normal behavior. When you change or create new database Armory needs to scan all your wallets again against the new databases. That is a very resourceful task (hint: now you will understand why on-chain scaling is not efficient and why we need that part of transaction to be off-chain) and I think it needs all the RAM memory for faster processing. I would like to know if there is a cap on the amount of ram that it needs in order to speed things up, but you sound like you have very little ram available on your back-up machine. I think you will need to leave your computer online overnight or when until it finishes. I will take a while.

Maybe someone can teach us how or what can we copy from Armory from another computer that has all wallets synced.

Both main and backup computer have 16GB of RAM. Scanning from scratch taking some time is normal, but it just feels odd to me that ArmoryDB will consume 14GB on one computer and hang while it never consumes more than 4GB or less (I think) on the main one.  And a bit unsettling to see it finish with wrong total sum when ArmoryDB is being killed. I've been trying this for some days now btw, having waited for more than a day for the task to complete and also saw other non-reproducable erratic behaviour.

Anyways, should've done some more research than just searching forum and reading through this thread, apologies! Looking at dbLog.txt there seems to be a problem with some blocks. You can not use bitcoind >0.13.1 with 0.95.1 right? Will make an own thread if I'm still curious, Thank You!


Title: Re: Armory 0.95 is out
Post by: achow101 on April 14, 2017, 09:31:32 PM
Anyways, should've done some more research than just searching forum and reading through this thread, apologies! Looking at dbLog.txt there seems to be a problem with some blocks. You can not use bitcoind >0.13.1 with 0.95.1 right? Will make an own thread if I'm still curious, Thank You!
You can't use greater than 0.14.0 with 0.95.1. You should make your own thread about this and post the armorylog.txt and dbLog.txt files.


Title: Re: Armory 0.95 is out
Post by: galaxiekyl on June 01, 2017, 02:18:17 AM
hi

armory can work on win x86 ?


Title: Re: Armory 0.95 is out
Post by: goatpig on June 03, 2017, 04:09:13 PM
hi

armory can work on win x86 ?

Has not been built for x86 in like 3 years. If you can get it to build, it could work on the side, or connected to a remote database. The DB itself can't run on x86 as it will run out of addressable memory.


Title: Re: Armory 0.95 is out
Post by: walletrecoveryservices on June 09, 2017, 04:37:56 AM
Hi
I've used Armory for years. Lovely software :)  Since I have upgraded to 0.96.0 (on Windows), one of my wallets behaves weirdly. To be specific: when I click the 'Receive Bitcoins' button, it does exactly nothing. When I have other wallets open, and I click that button, it correctly shows the relevant popup window. (the 'New Receiving Address' window)
Can you advise? Is this a known bug? Is there a work around?
Cheers Dave


Title: Re: Armory 0.95 is out
Post by: achow101 on June 09, 2017, 05:21:17 AM
Hi
I've used Armory for years. Lovely software :)  Since I have upgraded to 0.96.0 (on Windows), one of my wallets behaves weirdly. To be specific: when I click the 'Receive Bitcoins' button, it does exactly nothing. When I have other wallets open, and I click that button, it correctly shows the relevant popup window. (the 'New Receiving Address' window)
Can you advise? Is this a known bug? Is there a work around?
Cheers Dave
First, post in the right thread (hint: this one isn't it. check the stickies). Also post the Armory log files. You will probably also want to use the 0.96.1 testing build 2 as that has many bug fixes for 0.96.


Title: Re: Armory 0.95 is out
Post by: dellech on July 29, 2017, 10:38:48 PM
Hi,

thanks for finalizing the new release! I am keen to check it out :)

I get the following compilation error in Swig:
Code:
CppBlockUtils_wrap.cxx:3991:77: error: ‘type_name’ is not a member of ‘swig::traits<long long unsigned int>’

Regards,
Michael

What OS and compiler are you using?

Hi

I encountered the same error and found a workaround. Successfully compiled Armory 0.96.1 for usage as my offline signer wallet.

I need a 32bit linux version (OpenSUSE Tumbleweed, GCC 7.2) because my cold wallet is on an old Pentium M laptop, so 64bit OS is not an option.
After the compilation error I tried to compile Armory on a Bananpi M1 with armbian. Same error here and I found the following workaround which also helped for the 32bit compile:

in the file BitcoinArmory/cppForSwig/CppBlockUtils.i on line 44 I added the "|| 1" at the end.
Code:
#if defined(_WIN32) || defined(__WIN32__) || defined(__CYGWIN__) || defined(__CLANG__) || 1
%typedef unsigned long long uint64_t;
#else
#if defined(__GNUC__) // Linux
%typedef long unsigned int uint64_t;
#else
%typedef unsigned long long uint64_t;
#endif
#endif

It seems that the definition for the case __GNUC__ is only valid for 64bit Intel/AMD targets. my addition simply forces the typedef unsigned long long  instead of long unsigned int.  That does the trick for x86_32 and arm7.

Offline wallet creation and signing work like a charm - I tried 2 small transactions signed with the resulting executables and everything went ok.

I do not know enough C++, python and swig to suggest the real solution, but my workaround might give a hint.


Cheers and many thanks for your work, Goatpig!


Title: Re: Armory 0.95 is out
Post by: nimbosa on July 31, 2017, 11:29:11 AM
minor issue: reported here https://github.com/goatpig/BitcoinArmory/issues/275

using latest release armory_0.96.1_amd64.deb (https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.1) (Armory 0.96.1 for Ubuntu/Debian 64-bit):

$ sudo apt install -y ./armory_0.96.1_amd64.deb
.
..
...
Setting up armory (0.96.1-1) ...
   Setting up menu items.
    EXEC: xdg-icon-resource install --novendor --context apps --size 64 /usr/local/share/armory/img/armory_icon_64x64.png armoryicon
xdg-icon-resource: file '/usr/local/share/armory/img/armory_icon_64x64.png' does not exist
    EXEC: xdg-icon-resource install --novendor --context apps --size 64 /usr/local/share/armory/img/armory_icon_64x64.png armoryofflineicon
xdg-icon-resource: file '/usr/local/share/armory/img/armory_icon_64x64.png' does not exist
    EXEC: xdg-icon-resource install --novendor --context apps --size 64 /usr/local/share/armory/img/armory_icon_green_64x64.png armorytestneticon
xdg-icon-resource: file '/usr/local/share/armory/img/armory_icon_green_64x64.png' does not exist
    EXEC: xdg-desktop-menu  install --novendor /usr/share/applications/armory.desktop
    EXEC: xdg-desktop-menu  install --novendor /usr/share/applications/armorytestnet.desktop
    EXEC: xdg-desktop-menu  install --novendor /usr/share/applications/armoryoffline.desktop
...
..
.
$