Bitcoin Forum

Bitcoin => Armory => Topic started by: goatpig on December 24, 2018, 08:59:21 AM



Title: Armory 0.96.5
Post by: goatpig on December 24, 2018, 08:59:21 AM
Another point release with some bug fixes and the ability to spend to bech32 addresses. Most likely the last update before 0.97, sometimes for Q2 2019.

Changelog
Quote
== Added ==
   - You can now set the database path from the Settings menu.
   - You can now spend to bech32 addresses.
   - Added support for satoshi-port CLI argument in ArmoryDB.
   - Break backwards compatibility for unsigned transactions carrying bech32 outputs.
     Older versions cannot make sense of bech32 addresses, therefor they shouldn't
     be able to sign the tx at all.

== Fixes ==
   - Improved bitcoind path detection.
   - Properly carry thread-count and ram-usage command line arguments from client to automated db process.
   - Custom paths set in the GUI will now properly overrule custom paths from armoryqt.conf.
   - Fixed spending from lockboxes.
   - Fixed deleting lockboxes.
   - Fixed Simulfund promisory note creation and signing.
   - Fixed preview dialog for unconfirmed transactions.
   - Fixed previewing unsigned transactions in offline mode.
   - Properly detect output script type when filtering UTXOs.
   - Use relevant config files with testnet/regtest modes.
   - Properly display bech32 address strings in transaction system tray notification.
   - Fix signing transactions with OP_RETURN outputs.
   - Fix passing satoshi-port argument through ArmoryQt to auto-managed ArmoryDB.

   - Fixed SecurePrint decryption on Windows.
   - Recent updates to the MSVC compiler resulted in invalid decryption of AES-CBC packets. This issue only
     affects the decryption of SecurePrint encrypted backups. Encryption still operates as expected, no
     SecurePrint backups created with the incriminated builds are faulty. Wallets are not concerned, as they
     use AES-CFB.
     
     The solution was to turn off all optimizations in MSVC when buidling CryptoPP. This may impact DB boostrapping
     performance.

     This issue affects all Windows builds of 0.96.4.

== Misc ==
- Use blockstream.info instead of blockchain.info as the external block explorer link.


Binaries
https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.5

Happy holidays!


Title: Re: Armory 0.96.5
Post by: bitpop on December 28, 2018, 11:28:48 PM
Merry Christmas 🎄🎅🎁


Title: Re: Armory 0.96.5
Post by: Cassiel on January 25, 2019, 11:58:30 AM
Thanks goatpig.

Quick bug report, it still defaults to the wrong path on install (32bit, rather than 64bit). Been a bug for a number of releases now, very annoying if you don't remember to change it!


Title: Re: Armory 0.96.5
Post by: goatpig on January 25, 2019, 07:05:23 PM
Thanks goatpig.

Quick bug report, it still defaults to the wrong path on install (32bit, rather than 64bit). Been a bug for a number of releases now, very annoying if you don't remember to change it!


It's somewhere in the NSIS settings, I never remember to update that =(


Title: Re: Armory 0.96.5
Post by: johnlu on April 01, 2019, 09:13:36 PM
Most likely the last update before 0.97, sometimes for Q2 2019.

What will be new features in 0.97?


Title: Re: Armory 0.96.5
Post by: droark on April 02, 2019, 12:04:15 AM
While I can't speak for goatpig, I believe the following will be present in 0.97. Some of this is nerd stuff. Don't worry if this makes no sense to you. ;)

- Upgraded wallets (finally!) with full SegWit support and some other features. (Of course, people who wish to stick to their old wallets may do so. They just won't get access to the new features.)
- FCGI is being replaced with WebSockets, which is much more stable.
- Proper supernode support. People who wish to connect to Armory remotely will be able to do so via WebSockets. If it helps, think of it as being a bit like one of those block explorers, only you can send transactions and quickly resolve transactions that you throw at it. (You will need a powerful server for this, mind you.)
- Support for BIP 150 and 151. (Granted, Jonas is deprecating them in favor of a new standard.) This can be used in conjunction with WebSockets to establish a secure connection without relying on TLS.
- Moving from an ancient version of Crypto++ to libsecp256k1 (via libbtc) for crypto functionality.
- Better build system, partially in prep for a move to Python 3 and Qt 5 (required for many reasons).
- Replace SWIG with cppyy.
- More unit tests, to ensure that nothing breaks.
- Better documentation.
- Some code cleanup to get rid of a ton of compiler warnings.

There's probably more that I forgot. This is the gist of what's in there right now, or should be in there very soon.

Regarding Python 3 and Qt 5, this is a much-delayed thing we've been meaning to do for ages, especially since Qt 4 has been unsupported for ages and probably won't even run on the next version of macOS (out in ~6 months or so). We have somebody helping in their free time but I won't complain if others want to jump in and make things happen more quickly. :)

As for the timeframe, Q2 is still the target, but we'll see. Things keep coming up.


Title: Re: Armory 0.96.5
Post by: naska21 on April 29, 2019, 06:24:44 AM
snip

Thank you, goatpig, for  updating Armory. Regarding this I have question whether it has an option to transfer offline transaction from/to cold wallet via QR code? If not, will  such option  contain in future releases?


Title: Re: Armory 0.96.5
Post by: goatpig on April 29, 2019, 03:07:11 PM
snip

Thank you, goatpig, for  updating Armory. Regarding this I have question whether it has an option to transfer offline transaction from/to cold wallet via QR code? If not, will  such option  contain in future releases?

No this feature is not available in Armory. It has been requested before, and I think it's a good feature to have. I believe having hardware wallet support comes first however, but depending on how easy it is to implement, I can add it in the next major release.


Title: Re: Armory 0.96.5
Post by: walkingaround on June 24, 2019, 06:14:18 PM
Hi! Good to see that there's always new improvements to Armory. I have a question: does Ver. 0.96.5 work together with Bitcoin Core 0.18.0? I can't get it running on Windows 10 pro 64 bit. Since some days ago, I used Ver. 0.96.0 with many different Bitcoin core versions and all worked fine, but 0.96.5 doesn't work with 0.18.0 - I tried already all recommended pathing settings etc., but I can't get it running.

Am I doing something wrong, or does Armory 0.96.5 require lower versions of Bitcoin core?

Thank you, regards  :)



Title: Re: Armory 0.96.5
Post by: Carlton Banks on June 24, 2019, 07:53:58 PM
does Ver. 0.96.5 work together with Bitcoin Core 0.18.0?

I tested them together on Linux a few months ago, all seemed ok (pretty quick superficial test though). I'm not using 0.18 with Armory now though (0.18 eats your CPU if you use it together with Tor :/ )

"Post your logs" is what someone will eventually say :)


Title: Re: Armory 0.96.5
Post by: PhoenixFire on June 24, 2019, 08:58:17 PM
Hi! Good to see that there's always new improvements to Armory. I have a question: does Ver. 0.96.5 work together with Bitcoin Core 0.18.0? I can't get it running on Windows 10 pro 64 bit. Since some days ago, I used Ver. 0.96.0 with many different Bitcoin core versions and all worked fine, but 0.96.5 doesn't work with 0.18.0 - I tried already all recommended pathing settings etc., but I can't get it running.

Am I doing something wrong, or does Armory 0.96.5 require lower versions of Bitcoin core?

Thank you, regards  :)
0.18.0 and 0.96.5 function fine on my Win 10 testing VM.
Have you tried clearing the Armory database after upgrading from 0.96?
If yes, make a thread :)


Title: Re: Armory 0.96.5
Post by: HCP on June 25, 2019, 12:57:07 AM
Hi! Good to see that there's always new improvements to Armory. I have a question: does Ver. 0.96.5 work together with Bitcoin Core 0.18.0? I can't get it running on Windows 10 pro 64 bit.

Am I doing something wrong, or does Armory 0.96.5 require lower versions of Bitcoin core?
I'm currently using Windows 10 PRO x64 + Bitcoin Core 0.18.0 + Armory 0.96.5 and it all works fine.

Can you please clarify exactly what you mean by "can't get it running". Does Armory start? Does it attempt to build the database? Is is just showing as "offline"? Is it not correctly updating the number of blocks? ???

Also, if you haven't already tried... a very simple thing to try is simply rebooting the PC, it's possible there are "ghost" ArmoryDB processes running in the background preventing Armory from running properly.


But, in all honesty, your best bet is to do as Carlton Banks already suggested and post your logs. Both the armorylog.txt and dbLog.txt.


Title: Re: Armory 0.96.5
Post by: walkingaround on June 25, 2019, 10:26:38 AM
Hello to all, thanks for the many answers. In principle, I only wanted to know if 0.96.5/0.18.0 can work or I should give up. As  you commented, I can expect normal functioning with those versions, that's good news.

On the other side, I can't succeed in getting Armory running, so that I post my logs and say many thanks in advance for your help.

Armory starts, rebuilds the data base and stucks. It is either offline or shows a status "online" but zero blocks. It shows "node status" with no change and "organizing blockchain" for ages, but nothing else happens.

I already rebooted many times since I am tryiing to get Armory running.

I tried already letting Armory run bitcoin core in background and also without that (i.e. bitcoin core running separately).

Drive J is a Samsung T3 (fast enough).

I changed bitcoin core's config:
listen=1
addnode=127.0.0.1
server=1

That's all, thank you for any hint.   :) :)

Code:
Armorylog:

2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1284 - ************************************************************
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1285 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe --dbdir=J:\Users\User3\AppData\Roaming\Armory\databases --satoshi-datadir=J:\bitcoin
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1286 - ************************************************************
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1287 - Loading Armory Engine:
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1288 -    Armory Version        : 0.96.5
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1289 -    Armory Build:         : 8730390989
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1290 -    PyBtcWallet  Version  : 1.35
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1291 - Detected Operating system: Windows
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1292 -    OS Variant            : 10-10.0.17763--Multiprocessor Free
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1293 -    User home-directory   : C:\Users\User3\AppData\Roaming
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1294 -    Satoshi BTC directory : J:\bitcoin
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1295 -    Armory home dir       : C:\Users\User3\AppData\Roaming\Armory\
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1296 - Detected System Specs    :
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1297 -    Total Available RAM   : 15.96 GB
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1298 -    CPU ID string         : AMD64 Family 21 Model 2 Stepping 0, AuthenticAMD
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1299 -    Number of CPU cores   : 8 cores
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1300 -    System is 64-bit      : True
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1301 -    Preferred Encoding    : cp1252
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1302 -    Machine Arch          : amd64
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1303 -    Available HDD (ARM)   : 958 GB
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1304 -    Available HDD (BTC)   : 209 GB
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1305 -
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1306 - Network Name: Main Network
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1307 - Satoshi Port: 8333
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1308 - Do wlt check: True
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1309 - Named options/arguments to armoryengine.py:
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     force_segwit    : False
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     nettimeout      : 2
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     rescan          : False
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     force_fcgi      : False
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     ignoreAllZC     : False
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     rescanBalance   : False
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     disableModules  : False
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     port            : None
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     interport       : 8223
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     coverageOutputDir: None
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     forceWalletCheck: False
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     regtest         : False
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     rebuild         : False
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     thread_count    : -1
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     datadir         : DEFAULT
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     clearMempool    : False
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     offline         : False
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     armoryDBDir     : J:\Users\User3\AppData\Roaming\Armory\databases
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     armorydb_port   : 9001
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     satoshiPort     : DEFAULT
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     disableConfPermis: False
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     useTorSettings  : False
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     netlog          : False
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     keypool         : 100
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     coverageInclude : None
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     forceOnline     : False
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     disableWalletCheck: False
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     redownload      : False
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     rpcBindAddr     : 127.0.0.1
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     armorydb_ip     : 127.0.0.1
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     multisigFile    : DEFAULT
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     ram_usage       : -1
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     ignoreZC        : False
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     logDisable      : False
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     settingsPath    : C:\Users\User3\AppData\Roaming\Armory\ArmorySettings.txt
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     language        : en
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     db_type         : DB_FULL
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     doDebug         : False
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     enableDetSign   : True
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     mtdebug         : False
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     testnet         : False
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     rpcport         : DEFAULT
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     satoshiHome     : J:\bitcoin
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     satoshiRpcport  : DEFAULT
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     logFile         : C:\Users\User3\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1311 -     verbosity       : None
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1312 - Other arguments:
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1315 - ************************************************************
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:1720 - C++ block utilities loaded successfully
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:3578 - Using settings file: C:\Users\User3\AppData\Roaming\Armory\ArmorySettings.txt
2019-06-25 11:23:48 (ERROR) -- ArmoryUtils.pyc:3735 - Unsupported language  specified. Defaulting to English (en)
2019-06-25 11:23:48 (INFO) -- ArmoryUtils.pyc:3738 - Using Language: en
2019-06-25 11:23:48 (INFO) -- BDM.pyc:353 - Using the asynchronous/multi-threaded BlockDataManager.
2019-06-25 11:23:48 (INFO) -- BDM.pyc:354 - Blockchain operations will happen in the background. 
2019-06-25 11:23:48 (INFO) -- BDM.pyc:355 - Devs: check TheBDM.getState() before asking for data.
2019-06-25 11:23:48 (INFO) -- BDM.pyc:356 - Registering addresses during rescans will queue them for
2019-06-25 11:23:48 (INFO) -- BDM.pyc:357 - inclusion after the current scan is completed.
2019-06-25 11:23:51 (INFO) -- ArmoryUtils.pyc:3578 - Using settings file: C:\Users\User3\AppData\Roaming\Armory\ArmorySettings.txt
2019-06-25 11:23:51 (INFO) -- ArmoryQt.py:2060 - loadWalletsAndSettings
2019-06-25 11:23:51 (INFO) -- ArmoryQt.py:2120 - Loading wallets...
2019-06-25 11:23:52 (INFO) -- ArmoryQt.py:2185 - Number of wallets read in: 9
2019-06-25 11:23:52 (INFO) -- ArmoryQt.py:2190 -    Wallet (26Jaq9434):   "Online Wallet                   "   (Encrypted)
2019-06-25 11:23:52 (INFO) -- ArmoryQt.py:2190 -    Wallet (2yxvwUv5M):   "08 offline green (Wat"   (No Encryption)
2019-06-25 11:23:52 (INFO) -- ArmoryQt.py:2190 -    Wallet (2URaJxaPh):   "07 offline green (Wat"   (No Encryption)
2019-06-25 11:23:52 (INFO) -- ArmoryQt.py:2195 - Loading Multisig Lockboxes
2019-06-25 11:23:52 (INFO) -- ArmoryQt.py:1763 - acquiring process mutex...
2019-06-25 11:23:53 (INFO) -- ArmoryQt.py:1395 - setupUriRegistration
2019-06-25 11:23:53 (INFO) -- ArmoryQt.py:1513 - URL-register action: AskUser
2019-06-25 11:23:54 (INFO) -- ArmoryQt.py:566 - Usermode: Expert
2019-06-25 11:23:54 (INFO) -- ArmoryQt.py:1698 - Changing usermode:
2019-06-25 11:23:54 (INFO) -- ArmoryQt.py:1699 -    From: Expert
2019-06-25 11:23:54 (INFO) -- ArmoryQt.py:1707 -      To: Expert
2019-06-25 11:23:54 (INFO) -- ArmoryQt.py:1836 - startBitcoindIfNecessary
2019-06-25 11:23:54 (INFO) -- ArmoryQt.py:1872 - setSatoshiPaths
2019-06-25 11:23:54 (INFO) -- ArmoryQt.py:1891 - Setting satoshi datadir = j:\bitcoin
2019-06-25 11:23:54 (INFO) -- SDM.pyc:171 - Found bitcoind in the following places:
2019-06-25 11:23:54 (INFO) -- SDM.pyc:173 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2019-06-25 11:23:54 (INFO) -- SDM.pyc:173 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2019-06-25 11:23:54 (INFO) -- SDM.pyc:175 - Using: C:\Program Files\Bitcoin\daemon\bitcoind.exe
2019-06-25 11:23:54 (INFO) -- SDM.pyc:340 - Called startBitcoind
2019-06-25 11:23:54 (WARNING) -- SDM.pyc:445 - Spawning bitcoind with command: C:\Program Files\Bitcoin\daemon\bitcoind.exe -datadir=j:\bitcoin
2019-06-25 11:23:54 (INFO) -- ArmoryUtils.pyc:689 - Executing popen: [u'C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', '-datadir=j:\\bitcoin']
2019-06-25 11:23:55 (INFO) -- SDM.pyc:451 - PID of bitcoind: 4252
2019-06-25 11:23:55 (INFO) -- SDM.pyc:452 - PID of armory:   2664
2019-06-25 11:23:55 (INFO) -- ArmoryUtils.pyc:689 - Executing popen: ['C:\\Program Files (x86)\\Armory\\guardian.exe', '2664', '4252']
2019-06-25 11:23:58 (INFO) -- ArmoryQt.py:1923 - Setting netmode: 1
2019-06-25 11:23:58 (INFO) -- ArmoryQt.py:1905 - loadBlockchainIfNecessary
2019-06-25 11:23:58 (ERROR) -- ArmoryQt.py:1198 - 27 attempts to load blockchain failed.  Remove mempool.bin.
2019-06-25 11:23:58 (ERROR) -- ArmoryQt.py:1203 - File mempool.bin does not exist. Nothing deleted.
2019-06-25 11:23:58 (INFO) -- ArmoryQt.py:1923 - Setting netmode: 1
2019-06-25 11:23:58 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2019-06-25 11:23:58 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2019-06-25 11:24:00 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2019-06-25 11:24:04 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2019-06-25 11:24:07 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2019-06-25 11:24:11 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode

=============

dblog:

Log file opened at 11:21:50.000: C:\Users\User3\AppData\Roaming\Armory\dbLog.txt
-INFO  - 11:21:50.000: (e:\users\goat\code\armory3\cppforswig\main.cpp:32) Running on 8 threads
-INFO  - 11:21:50.000: (e:\users\goat\code\armory3\cppforswig\main.cpp:33) Ram usage level: 50
-INFO  - 11:21:50.093: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:915) blkfile dir: J:\bitcoin\blocks
-INFO  - 11:21:50.093: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:916) lmdb dir: J:\Users\User3\AppData\Roaming\Armory\databases
-INFO  - 11:21:50.093: (e:\users\goat\code\armory3\cppforswig\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 11:21:51.734: (e:\users\goat\code\armory3\cppforswig\bdm_server.h:263) Listening on port 59111
-INFO  - 11:21:51.734: (e:\users\goat\code\armory3\cppforswig\bitcoinp2p.cpp:947) Connected to Bitcoin node
-INFO  - 11:21:51.062: (e:\users\goat\code\armory3\cppforswig\noderpc.cpp:57) RPC connection established
-INFO  - 11:21:51.062: (e:\users\goat\code\armory3\cppforswig\blockdatamanagerconfig.cpp:919) waiting on node sync: 99.9998%
-INFO  - 11:21:51.078: (e:\users\goat\code\armory3\cppforswig\noderpc.cpp:425) Node is ready
-INFO  - 11:21:51.078: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:1108) Executing: doInitialSyncOnLoad
-INFO  - 11:21:51.218: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:199) Reading headers from db
-WARN  - 11:21:51.218: (e:\users\goat\code\armory3\cppforswig\lmdb_wrapper.cpp:1241) No headers in DB yet!
-INFO  - 11:21:51.218: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:238) Found 1 headers in db
-INFO  - 11:21:51.218: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:71) updating HEADERS db
-INFO  - 11:21:52.797: (e:\users\goat\code\armory3\cppforswig\bdm_server.cpp:1121) registered bdv: ae3e5bb38b7e83f01b1b
-INFO  - 11:21:55.281: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4
-INFO  - 11:21:55.328: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #6
-INFO  - 11:21:56.703: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #7
-INFO  - 11:21:59.359: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #12
-INFO  - 11:21:59.453: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #13
-INFO  - 11:22:00.843: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #14
-INFO  - 11:22:00.125: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #15
-INFO  - 11:22:03.531: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #20
-INFO  - 11:22:03.578: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #21
-INFO  - 11:22:04.297: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #22
-INFO  - 11:22:04.437: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #23
-INFO  - 11:22:07.453: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #29
-INFO  - 11:22:08.515: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #30
-INFO  - 11:22:09.703: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #31
-INFO  - 11:22:11.390: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #37
-INFO  - 11:22:13.156: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #39
-INFO  - 11:22:15.375: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #45
-INFO  - 11:22:17.453: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #47
-INFO  - 11:22:19.187: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #53
-INFO  - 11:22:22.109: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #54
-INFO  - 11:22:22.234: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #55
-INFO  - 11:22:23.984: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #61
-INFO  - 11:22:26.140: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #62
-INFO  - 11:22:26.203: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #63
-INFO  - 11:22:27.922: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #69
-INFO  - 11:22:30.984: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #70
-INFO  - 11:22:30.047: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #71
-INFO  - 11:22:31.781: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #77
-INFO  - 11:22:34.062: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #78
-INFO  - 11:22:34.172: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #79
-INFO  - 11:22:35.765: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #85
-INFO  - 11:22:38.047: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #86
-INFO  - 11:22:38.125: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #87
-INFO  - 11:22:38.515: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #93
-INFO  - 11:22:42.890: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #94
-INFO  - 11:22:42.000: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #95
-INFO  - 11:22:42.343: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #101
-INFO  - 11:22:46.015: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #102
-INFO  - 11:22:46.093: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #103
-INFO  - 11:22:46.187: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #109
-INFO  - 11:22:50.765: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #117
-INFO  - 11:22:53.312: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #125
-INFO  - 11:22:57.843: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #133
-INFO  - 11:23:00.328: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #141
-INFO  - 11:23:04.968: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #149
-INFO  - 11:23:07.547: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #157
-INFO  - 11:23:11.031: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #165
-INFO  - 11:23:14.484: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #173
-INFO  - 11:23:18.937: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #181
-INFO  - 11:23:21.453: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #189
-INFO  - 11:23:25.922: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #197
-INFO  - 11:23:28.343: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #205
-INFO  - 11:23:32.000: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #213
-ERROR - 11:23:33.297: (e:\users\goat\code\armory3\cppforswig\bitcoinp2p.cpp:1037) caught StopBlockingLoop in processDataStackThread
-INFO  - 11:23:33.297: (e:\users\goat\code\armory3\cppforswig\bitcoinp2p.cpp:969) Disconnected from Bitcoin node
-INFO  - 11:23:35.609: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #221
-INFO  - 11:23:39.078: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #229
-INFO  - 11:23:42.422: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #237
-INFO  - 11:23:46.922: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #245
-INFO  - 11:23:49.468: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #253
-INFO  - 11:23:53.906: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #261
-INFO  - 11:23:56.343: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #269
-INFO  - 11:23:58.875: (e:\users\goat\code\armory3\cppforswig\bdm_server.cpp:1121) registered bdv: 7a11e6b86a45ff77a2ed
-INFO  - 11:24:00.093: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #277
-INFO  - 11:24:04.750: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #285
-INFO  - 11:24:07.609: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #293
-INFO  - 11:24:11.672: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #301
-INFO  - 11:24:14.953: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #309
-INFO  - 11:24:18.656: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #317
-INFO  - 11:24:21.406: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #325
-INFO  - 11:24:24.593: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #333
-INFO  - 11:24:28.297: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #341
-INFO  - 11:24:31.609: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #349
-INFO  - 11:24:35.047: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #357
-INFO  - 11:24:38.515: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #365
-INFO  - 11:24:42.500: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #373
-INFO  - 11:24:46.156: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #381
-INFO  - 11:24:50.156: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #389
-INFO  - 11:24:54.968: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #397
-INFO  - 11:24:57.515: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #405
-ERROR - 11:25:00.093: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:366) block deser except:
-ERROR - 11:25:00.093: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:367) block fileID: 412
-INFO  - 11:25:00.093: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:493) Found next block after skipping 909384bytes
-INFO  - 11:25:01.328: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #413
-INFO  - 11:25:05.750: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #421
-INFO  - 11:25:09.750: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #429
-INFO  - 11:25:12.250: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #437
-INFO  - 11:25:16.093: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #445
-INFO  - 11:25:20.672: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #453
-INFO  - 11:25:23.125: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #461
-INFO  - 11:25:27.953: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #469
-INFO  - 11:25:30.625: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #477
-INFO  - 11:25:34.390: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #485
-INFO  - 11:25:38.093: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #493
-INFO  - 11:25:42.781: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #501
-INFO  - 11:25:44.890: (e:\users\goat\code\armory3\cppforswig\bitcoinp2p.cpp:947) Connected to Bitcoin node
-INFO  - 11:25:45.453: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #509
-INFO  - 11:25:49.812: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #517
-INFO  - 11:25:52.453: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #525
-INFO  - 11:25:56.172: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #533
-INFO  - 11:26:00.812: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #541
-INFO  - 11:26:03.422: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #549
-INFO  - 11:26:07.140: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #557
-INFO  - 11:26:11.718: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #565
-INFO  - 11:26:14.047: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #573
-INFO  - 11:26:18.750: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #581
-INFO  - 11:26:21.406: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #589
-INFO  - 11:26:25.984: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #597
-INFO  - 11:26:28.593: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #605
-INFO  - 11:26:32.281: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #613
-INFO  - 11:26:36.703: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #621
-INFO  - 11:26:39.359: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #629
-INFO  - 11:26:43.109: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #637
-INFO  - 11:26:47.703: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #645
-INFO  - 11:26:50.390: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #653
-INFO  - 11:26:54.875: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #661
-INFO  - 11:26:58.656: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #669
-INFO  - 11:27:01.343: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #677
-INFO  - 11:27:05.187: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #685
-INFO  - 11:27:09.015: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #693
-INFO  - 11:27:13.734: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #701
-INFO  - 11:27:16.562: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #709
-INFO  - 11:27:20.234: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #717
-INFO  - 11:27:24.890: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #725
-INFO  - 11:27:27.312: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #733
-INFO  - 11:27:31.968: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #741
-INFO  - 11:27:34.218: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #749
-INFO  - 11:27:38.953: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #757
-INFO  - 11:27:42.859: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #765
-INFO  - 11:27:46.656: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #773
-INFO  - 11:27:49.453: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #781
-INFO  - 11:27:53.203: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #789
-INFO  - 11:27:57.718: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #797
-INFO  - 11:28:00.187: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #805
-INFO  - 11:28:04.672: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #813
-INFO  - 11:28:07.281: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #821
-INFO  - 11:28:10.578: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #829
-INFO  - 11:28:14.937: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #837
-INFO  - 11:28:17.406: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #845
-INFO  - 11:28:21.000: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #853
-INFO  - 11:28:25.656: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #861
-INFO  - 11:28:28.390: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #869
-INFO  - 11:28:32.093: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #877
-INFO  - 11:28:36.828: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #885
-INFO  - 11:28:39.203: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #893
-INFO  - 11:28:43.797: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #901
-INFO  - 11:28:46.375: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #909
-INFO  - 11:28:50.031: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #917
-INFO  - 11:28:53.515: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #925
-INFO  - 11:28:57.093: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #933
-INFO  - 11:29:01.656: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #941
-INFO  - 11:29:04.156: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #949
-INFO  - 11:29:07.531: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #957
-INFO  - 11:29:11.859: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #965
-INFO  - 11:29:14.390: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #973
-INFO  - 11:29:18.062: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #981
-INFO  - 11:29:22.765: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #989
-INFO  - 11:29:25.375: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #997
-INFO  - 11:29:29.093: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1005
-INFO  - 11:29:33.703: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1013
-INFO  - 11:29:36.218: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1021
-INFO  - 11:29:40.890: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1029
-INFO  - 11:29:43.250: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1037
-INFO  - 11:29:47.078: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1045
-INFO  - 11:29:50.547: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1053
-INFO  - 11:29:54.281: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1061
-INFO  - 11:29:58.843: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1069
-INFO  - 11:30:01.468: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1077
-INFO  - 11:30:05.859: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1085
-INFO  - 11:30:08.609: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1093
-INFO  - 11:30:12.468: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1101
-INFO  - 11:30:16.484: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1109
-INFO  - 11:30:20.937: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1117
-INFO  - 11:30:24.875: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1125
-INFO  - 11:30:27.484: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1133
-INFO  - 11:30:31.109: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1141
-INFO  - 11:30:34.922: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1149
-INFO  - 11:30:37.890: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1157
-INFO  - 11:30:40.781: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1165
-INFO  - 11:30:43.828: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1173
-INFO  - 11:30:46.781: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1181
-INFO  - 11:30:48.609: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1189
-INFO  - 11:30:51.359: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1197
-INFO  - 11:30:54.359: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1205
-INFO  - 11:30:58.703: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1213
-INFO  - 11:31:01.359: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1221
-INFO  - 11:31:04.609: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1229
-INFO  - 11:31:08.125: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1237
-INFO  - 11:31:11.437: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1245
-INFO  - 11:31:15.859: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1253
-INFO  - 11:31:18.343: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1261
-INFO  - 11:31:22.859: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1269
-INFO  - 11:31:25.718: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1277
-INFO  - 11:31:28.922: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1285
-INFO  - 11:31:31.562: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1293
-INFO  - 11:31:34.515: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1301
-INFO  - 11:31:38.640: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1309
-INFO  - 11:31:41.797: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1317
-INFO  - 11:31:44.062: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1325
-INFO  - 11:31:47.578: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1333
-INFO  - 11:31:51.031: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1341
-INFO  - 11:31:54.484: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1349
-INFO  - 11:31:58.000: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1357
-INFO  - 11:32:01.437: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1365
-INFO  - 11:32:05.140: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1373
-INFO  - 11:32:09.750: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1381
-INFO  - 11:32:12.406: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1389
-INFO  - 11:32:16.718: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1397
-INFO  - 11:32:19.250: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1405
-INFO  - 11:32:23.906: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1413
-INFO  - 11:32:26.390: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1421
-INFO  - 11:32:30.015: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1429
-INFO  - 11:32:33.437: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1437
-INFO  - 11:32:37.031: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1445
-INFO  - 11:32:40.484: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1453
-INFO  - 11:32:44.062: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1461
-INFO  - 11:32:47.562: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1469
-INFO  - 11:32:51.203: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1477
-INFO  - 11:32:55.922: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1485
-INFO  - 11:32:59.781: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1493
-INFO  - 11:33:03.640: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1501
-INFO  - 11:33:06.328: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1509
-INFO  - 11:33:10.218: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1517
-INFO  - 11:33:13.375: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1525
-INFO  - 11:33:17.984: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1533
-INFO  - 11:33:20.609: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1541
-INFO  - 11:33:24.203: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1549
-INFO  - 11:33:28.859: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1557
-INFO  - 11:33:31.609: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1565
-INFO  - 11:33:36.687: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1573
-INFO  - 11:33:39.562: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1581
-INFO  - 11:33:43.281: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1589
-INFO  - 11:33:47.453: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1597
-INFO  - 11:33:51.406: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1605
-INFO  - 11:33:55.015: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1613
-INFO  - 11:33:59.968: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1621
-INFO  - 11:34:03.687: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1629
-INFO  - 11:34:06.281: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1637
-INFO  - 11:34:10.890: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1645
-INFO  - 11:34:14.797: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1653
-INFO  - 11:34:17.297: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1661
-INFO  - 11:34:21.906: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1669
-INFO  - 11:34:24.578: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1677
-INFO  - 11:34:28.234: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1685
-INFO  - 11:34:32.843: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1693
-INFO  - 11:34:53.718: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #1695
-INFO  - 11:35:02.078: (e:\users\goat\code\armory3\cppforswig\blockchain.cpp:248) Organizing chain





Title: Re: Armory 0.96.5
Post by: HCP on June 27, 2019, 09:04:24 PM
I honestly can't see anything really obviously wrong with those logs?!? :(

I would suggest that you attempt to use the "Rebuild and Rescan Databases" option from the help menu and see if that fixes it. Other than that, possibly running ArmoryDB manually from the command line (without ArmoryQT running) to see if it is behaving correctly.


"organizing blockchain" for ages, but nothing else happens.
Note that the "organising blockchain" can take quite a while to finish on first sync... how long did you leave it running?


Title: Re: Armory 0.96.5
Post by: walkingaround on June 28, 2019, 07:37:48 AM
Thank you, HCP.

I have already tried to rebuild and rescan databases many times with no success.

I waited on "organizing blockchain" for more than 12 hours. It was, however, not a first sync; I have been using Armory 96.0 for over two years with no problems. The trouble began as I changed to ver. 96.5.

I suspect that my bitcoin core blockchain is corrupted. Curiously, bitcoin core reported to be fully synchronized, but in an attempt to reindex chainstate bitcoin core reported a fatal error and does not start anymore.

Now, I am reindexing the whole bitcoin blockchain; this will take some long time.

I think that the origin of the failure is that an Armory process working in the background was killed as I shut down the computer and corrupted thereby the bitcoin blockchain files. I will write again if I get Armory running after rebuilding Bitcoin Core.

Thanks again!
 


Title: Re: Armory 0.96.5
Post by: walkingaround on June 29, 2019, 07:29:37 AM
I'm using a new bitcoin blockchain downloaded by torrent, and finally I got Armory running, after many days trying without success. Next, I will reindex the whole blockchain again for security.

In some other postings I have seen that many other people had similar problems.

To all of them, consider the possibility that bitcoin core's blockchain is corrupted. In my case, it was not easy to identify the problem because bitcoin core reported always to be fully synchronized; but Armory detected anyhow problems in the blockchain and didn't work.

Another possibility could be that my PC is infected by malware not detected by my security software. I'm checking it.

Many thanks again!

 8)


Title: Re: Armory 0.96.5
Post by: SubMex on July 22, 2019, 03:41:17 PM
@walkingaround

Yes, its like you said: if there is any problem with the blockchain database, Armory hangs.
I had the same problem in the past, and after reloading the whole blockchain, Armory works fine.

Maybe Armory should tell this to the user, if there is a problem with the blockchain database?  :)


Title: Re: Armory 0.96.5
Post by: goatpig on July 22, 2019, 04:20:26 PM
It gets reported in the log files.


Title: Re: Armory 0.96.5
Post by: VelhoDoRio on July 25, 2019, 03:57:37 AM
Any possibility of Armory being released as an appimage?


Title: Re: Armory 0.96.5
Post by: arasharashi on August 08, 2019, 10:09:35 AM
I have putted address of my ARMORY wallet in my mining pool site & they have sent some bitcoins to it but my ARMORY wallet is not showing any thing and my wallet's balance is zero. what should I do?


Title: Re: Armory 0.96.5
Post by: goatpig on August 08, 2019, 02:24:07 PM
Any possibility of Armory being released as an appimage?

I dont know what that is =/


Title: Re: Armory 0.96.5
Post by: HCP on August 08, 2019, 09:06:42 PM
I have putted address of my ARMORY wallet in my mining pool site & they have sent some bitcoins to it but my ARMORY wallet is not showing any thing and my wallet's balance is zero. what should I do?
Do you have Bitcoin Core installed and fully synced? Armory requires Bitcoin Core to be able to function properly... if you don't have Bitcoin Core installed, you will need to install it (and fully sync the blockchain) before Armory will be able to show your balance...

Suggest you create your own thread rather than posting in this one.


Title: Re: Armory 0.96.5
Post by: johnlu on August 15, 2019, 06:32:22 PM
Hi, I know this an open source project. But there's some time with no new release. Do you have any idea of how long it would take to release 0.97?

Thanks for your all your efforts guys :-)


Title: Re: Armory 0.96.5
Post by: Carlton Banks on August 15, 2019, 07:19:20 PM
@johnlu

there's a significant re-write of the code going on for 0.97, that sort of thing can take alot of time. It's better that it does (take some time), as it's a good opportunity to re-structure the codebase with a long term perspective in mind


not sure on the exact latest progress though, check github I guess


Title: Re: Armory 0.96.5
Post by: johnlu on August 16, 2019, 08:50:54 AM
Thanks Carlton!!


Title: Re: Armory 0.96.5
Post by: goatpig on August 16, 2019, 01:40:31 PM
Changes are taking place in the dev branch. A lot has changed and there's still a lot I want to add in there. The work is split with helping another project. Most of the progess with that project is shared with Armory and the code ends up in the Armory repo eventually.

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


Title: Re: Armory 0.96.5
Post by: droark on August 17, 2019, 03:51:32 PM
The main bottleneck atm is moving from SWIG to another C++ to Python framework to allow for a shift to Py3 & Qt5.

As an update on that end, there have been three main holdups.

- The cppyy (https://cppyy.readthedocs.io/en/latest/) project is the main linchpin here. It's pretty slick, and Wim's a very smart guy. Alas, like any project, it has holes. We find 'em, we report 'em, we usually get a fix within a day or two. I want to say that this portion is close to being done.
- There's something in WebSocket that isn't working right with the GUI. I was trying to track it down when...
- ...due to Apple's stupidity (https://communities.vmware.com/thread/614825), my VMs became unusable for a few weeks. They're kinda usable now but, until Apple issues a proper fix (and who knows if they will or if they'll try to force an upgrade to macOS 10.15), I may have to force a downgrade of my Mac. Thanks for nothing, Tim.

The switch from Py2 to Py3 remains to be done. We have somebody who has offered to help. I don't know if he's still interested, although I assume he is (contingent on his schedule). I'm pretty busy myself but will do what I can to help. This really needs to get done ASAP for a variety of reasons.


Title: Re: Armory 0.96.5
Post by: VelhoDoRio on September 02, 2019, 02:58:29 AM
Any possibility of Armory being released as an appimage?

I dont know what that is =/

https://appimage.org/

Electrum and Electrum-LTC are already using it.
https://electrum.org/#download

The downside is that is more slow.
But there is no need to install it or install system libraries.

I always build Armory from the git repository.
But for the offline machine, the signer, I have to do a few extras steps.

I have to clone the repo to a usb stick that has vfat file system.
Take the usb stick to the offline machine and clone it again.
And then build it there.

Having an appimage to use on the offline machine just for signing could be handy!


Title: Re: Armory 0.96.5
Post by: Carlton Banks on September 02, 2019, 11:06:13 AM
Having an appimage to use on the offline machine just for signing could be handy!

not really, as the offline machine must have the appimage package installed too, which compromises the security model


computer science solved this problem 40-50 years ago: the static binary (bitcoin itself is a static binary, all needed libraries by bitcoind/bitcoin-qt are packaged into the executable file)


appimage is trying to reinvent the wheel, and they actually managed to fail. they solved the problem of needing to install non-standard extra packages/libs by.... requiring an extra non-standard package/library. great idea. no, really. ::)


Title: Re: Armory 0.96.5
Post by: goatpig on September 03, 2019, 04:41:54 AM
Quote
computer science solved this problem 40-50 years ago: the static binary (bitcoin itself is a static binary, all needed libraries by bitcoind/bitcoin-qt are packaged into the executable file)

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


Title: Re: Armory 0.96.5
Post by: Carlton Banks on September 03, 2019, 08:13:01 AM
Quote
computer science solved this problem 40-50 years ago: the static binary (bitcoin itself is a static binary, all needed libraries by bitcoind/bitcoin-qt are packaged into the executable file)

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

right. those libraries are so commonly used that it's not hard to work out a way of getting them to play nice with whatever Linux distro is shipping the most eccentric version of, which if we're honest is always Debian stable, lol. The common Debian joke is that you only need to remove 1 letter from "stable" and 2 from "unstable" to get the words "stale" and "usable"


Title: Re: Armory 0.96.5
Post by: Donhobluesky on October 08, 2019, 07:57:04 PM
This version will not run on my MacOS 10.14.6


Title: Re: Armory 0.96.5
Post by: Carlton Banks on October 08, 2019, 08:24:29 PM
getting Armory running on a Mac is not the easiest task. there are a few people on Bitcointalk who know the details, of which there are more than a few


Title: Re: Armory 0.96.5
Post by: droark on October 10, 2019, 02:54:48 PM
This version will not run on my MacOS 10.14.6

1)What is the exact problem that you're having?

2)I need to make a separate post, but just so that everybody knows, Armory won't run on 10.15 due to some changes Apple made. Please don't upgrade to it just yet.


Title: Re: Armory 0.96.5
Post by: infosecwriter on May 13, 2020, 01:24:43 AM
Ubuntu 20.04 has issues installing.

Missing dependencies python-qt4, python-twisted, python-psutil

---
electing previously unselected package armory.
(Reading database ... 245601 files and directories currently installed.)
Preparing to unpack armory_0.96-gcc5.4_amd64.deb ...
Unpacking armory (0.96-1) ...
dpkg: dependency problems prevent configuration of armory:
 armory depends on python-qt4; however:
  Package python-qt4 is not installed.
 armory depends on python-twisted; however:
  Package python-twisted is not installed.
 armory depends on python-psutil; however:
  Package python-psutil is not installed.

dpkg: error processing package armory (--install):
 dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.31-0ubuntu9) ...
Errors were encountered while processing:
 armory


Title: Re: Armory 0.96.5
Post by: goatpig on May 13, 2020, 11:23:34 AM
Ubuntu 20 got rid of py2 I believe.


Title: Re: Armory 0.96.5
Post by: arulbero on May 16, 2020, 12:28:08 PM
Ubuntu 20.04 has issues installing.

Missing dependencies python-qt4, python-twisted, python-psutil

Ubuntu 20 got rid of py2 I believe.

Quote
computer science solved this problem 40-50 years ago: the static binary (bitcoin itself is a static binary, all needed libraries by bitcoind/bitcoin-qt are packaged into the executable file)

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

Is it possible to have a release of Armory (executable file) that works on ubuntu 20.04?

With all needed libraries statically linked?


Title: Re: Armory 0.96.5
Post by: goatpig on May 16, 2020, 11:12:15 PM
Python isn't exactly a library, though it the interpreter can be loaded as one, but I digress. Yes, it's possible to freeze Armory on linux. But considering the cost to do so, you're better off running an older version (in a VM), or installing py2 on you Ubuntu 20 system. There will be a release sometimes this summer with a bunch of new stuff and a port to py3/qt5 which will fix a lot of compatibility stuff with modern OS.


Title: Re: Armory 0.96.5
Post by: arulbero on May 17, 2020, 06:21:16 PM
Python isn't exactly a library, though it the interpreter can be loaded as one, but I digress. Yes, it's possible to freeze Armory on linux. But considering the cost to do so, you're better off running an older version (in a VM), or installing py2 on you Ubuntu 20 system.

The installation of python2 is very simple: sudo apt-get install python2, but Pyqt4 is not available as package for 20.04. VM is the last resort.


There will be a release sometimes this summer with a bunch of new stuff and a port to py3/qt5 which will fix a lot of compatibility stuff with modern OS.

Very good news!!


Title: Re: Armory 0.96.5
Post by: goatpig on May 18, 2020, 08:03:49 AM
The installation of python2 is very simple: sudo apt-get install python2, but Pyqt4 is not available as package for 20.04. VM is the last resort.

There typically are archive servers with older packages that let you grab no longer supported libs like this. You could also install it from pip, though I believe a Ubuntu 19 VM is the better solution.


Title: Re: Armory 0.96.5
Post by: Aurik on May 30, 2020, 03:01:31 PM
Armory 0.97: Is this project still being worked on? In this topics first post the eta is Q2 '19.
Can you give some update and background infos about it?


Title: Re: Armory 0.96.5
Post by: Ethorsen on May 30, 2020, 04:05:34 PM
I also wish we can see an update to Armory sooner or later.  I've been sticking with this wallet since I started dealing BTC in early 2013.   It would be nice to continue using it on the long term.


Title: Re: Armory 0.96.5
Post by: goatpig on May 30, 2020, 04:26:27 PM
Quote
Can you give some update and background infos about it?

Sometimes this summer. New wallet code is done, migration to LWS + socket encryption is done. Main blocker atm is the migration from p2/qt4 to py3/qt5. Then I need some extra work for the BIP32 wallet GUI. I do have a day job though.


Title: Re: Armory 0.96.5
Post by: Masterswarm on August 19, 2020, 05:59:56 PM
I have an old machine which is still running 0.92!  It runs on my dad's computer so I quite literally haven't toucehd it in years.  Still has a fraction of a BTC on it too!


Title: Re: Armory 0.96.5
Post by: giszmo on August 31, 2020, 12:24:08 AM
What happened to the website? https://btcarmory.com/ down? Git repo has no updates in years?

I'm expanding https://WalletScrutiny.com to Linux wallets and in terms of binary distribution this would be a "defunct" wallet?


Title: Re: Armory 0.96.5
Post by: goatpig on August 31, 2020, 06:20:54 AM
What happened to the website? https://btcarmory.com/ down? Git repo has no updates in years?

I'm expanding https://WalletScrutiny.com to Linux wallets and in terms of binary distribution this would be a "defunct" wallet?

Owned by the former maintainers. I use my repo (goatpig/BitcoinArmory on github). It has a gh-pages branch for btcarmory.com in there. You can look at development in the dev branch. Master only receives signed tags for releases.


Title: Re: Armory 0.96.5
Post by: btcArmory user on December 20, 2020, 08:10:47 PM
I am reindexing bitcoin core from command line on Windows 10.0. Bitcoin Core 0.20.1
The counters are incrementing on lines 2 - 4, but they are static on line 1 of the overview tab.
Number of blocks left: Unknown. Syncing Headers (524490, 79.5%)...

The lines containing date and time, progress, and progress increase per hour are all incrementing or changing.

Is the syncing continuing, or do I need to stop this process and try something else?


Title: Re: Armory 0.96.5
Post by: HCP on December 21, 2020, 05:50:28 AM
I think it's caused by the reindex option... What it is currently doing is going through what you currently have stored on disk (this is why you see progress changing as it reindexs the blocks on disk)... once it finishes that process, it'll then start looking for new blocks after 524490 (at which point the "syncing headers" values should change).


Title: Re: Armory 0.96.5
Post by: btcArmory user on January 14, 2021, 12:15:33 AM
The re-indexing process stopped at 53.29%
Sat
May 26 7:39:09  2018

2 years and 32 weeks behind

It still lists the same values at the top: Syncing Headers (524490, 79.5%)

Which way to go on this? Delete db files and rebuild the database in bitcoin core? It took over 3 weeks to get to the stopping point re-indexing headers.


Title: Re: Armory 0.96.5
Post by: HCP on January 14, 2021, 07:37:42 PM
The only things I can think of that would cause this are:

1. Corrupt data on disk... the easiest (but "longest") fix is to simply delete all the bitcoin core block data and start syncing from scratch again.
2. Out of hard disk space... Bitcoin Core will simply stop syncing if it runs out of harddrive space.
3. Some sort of hardware issue causing data corruption.

So, do you actually have enough free space on the disk for the blockchain? ??? It's well over 350+gigs on total storage now...


What do you see at the end of the debug.log file when Bitcoin Core stops syncing? ??? Any obvious errors? It would be helpful if you posted the last couple of hundred of lines from debug.log (use pastebin.com to avoid post length limits)


Title: Re: Armory 0.96.5
Post by: btcArmory user on January 16, 2021, 06:12:30 PM
Hard Disk
used:  187 GB
free:  278 GB

https://pastebin.com/ciVY7EUW



Title: Re: Armory 0.96.5
Post by: btcArmory user on January 16, 2021, 06:41:42 PM
Could the issue be caused by an intermittent failure in the Internet connection? No new blocks are available?


Title: Re: Armory 0.96.5
Post by: HCP on January 16, 2021, 08:46:17 PM
Something odd going on with your Bitcoin Core...

It got as far as getting the new block at 524491, and then just stopped getting new blocks...
Quote
2021-01-09T14:55:25Z UpdateTip: new best=0000000000000000000b6ce14cc39740a42d817ba68382075927555cd707f3e1 height=524491 version=0x20000000 log2_work=88.888701 tx=318642673 date='2018-05-26T14:39:09Z' progress=0.532869 cache=410.4MiB(2884728txo)
2021-01-09T14:55:25Z Imported mempool transactions from disk: 0 succeeded, 0 failed, 0 expired, 0 already there
2021-01-09T15:32:10Z Potential stale tip detected, will try using extra outbound peer (last tip update: 2205 seconds ago)
...
2021-01-12T08:53:05Z Potential stale tip detected, will try using extra outbound peer (last tip update: 237460 seconds ago)

Are you actually connected? What is the networkactive value and how many connections do you see if you do:
Code:
bitcoin-cli getnetworkinfo

Or look at the "Window -> Information" screen in Bitcoin Core GUI? ???


Title: Re: Armory 0.96.5
Post by: btcArmory user on January 16, 2021, 11:16:09 PM
It reached block 524491 previously. I started re-indexing headers about 3 weeks ago. After that, it stopped at a lower percentage, but both values were still displayed in the dialog box.

These two lines were the current status:
The re-indexing process stopped at 53.29%
Sat
May 26 7:39:09  2018

2 years and 32 weeks behind

They were displayed below the block 524491 entry. At the moment, I am updating Windows, having run performance tuning on the system. Windows performance was extremely sluggish.


Title: Re: Armory 0.96.5
Post by: btcArmory user on January 17, 2021, 12:28:49 AM
I currently have 1 active connection to the bitcoin network. That happened after I dropped my personal firewall.
Is there a way to enter IP addresses for bitcoin nodes into the bitcoin.conf file?


Title: Re: Armory 0.96.5
Post by: HCP on January 17, 2021, 12:42:57 AM
I currently have 1 active connection to the bitcoin network. That happened after I dropped my personal firewall.
Is there a way to enter IP addresses for bitcoin nodes into the bitcoin.conf file?
yeah... you can use the addnode command... either with bitcoin-cli, in the console in Bitcoin Core GUI or in the bitcoin.conf file.

As per the examples on the bitcoin github (https://github.com/bitcoin/bitcoin/blob/master/share/examples/bitcoin.conf):
Code:
# Use as many addnode= settings as you like to connect to specific peers
addnode=69.164.218.197
addnode=10.0.0.2:8333


Title: Re: Armory 0.96.5
Post by: btcArmory user on January 17, 2021, 01:01:14 AM
Method not found (code -32601)

Attempted addnode and connect commands in the console


Title: Re: Armory 0.96.5
Post by: HCP on January 17, 2021, 01:13:31 AM
Attempted addnode and connect commands in the console
Ahhh ok, you asked about bitcoin.conf... the previous example was bitcoin.conf option.

In the console, the command syntax is different, it should be:
Code:
addnode IPADDRESS add

for example:
Code:
addnode 127.0.0.1 add


Title: Re: Armory 0.96.5
Post by: btcArmory user on January 17, 2021, 03:13:22 AM
I tried a couple of searches, but didn't come up with a list of IP addresses for bitcoin nodes. Is one of those available? What is the maximum number of concurrent peers that can be established?

getnetworkinfo returns a value of connections = 3

Is this a configuration limit on the number of concurrent peer connections? I do have three at the moment, but wouldn't 16 would be better?


Title: Re: Armory 0.96.5
Post by: btcArmory user on January 17, 2021, 06:35:03 PM
Connections are being added automatically now. 7 is the highest number that I've seen displayed. Thank you for the help!


Title: Re: Armory 0.96.5
Post by: HCP on January 17, 2021, 10:18:08 PM
Connections are being added automatically now. 7 is the highest number that I've seen displayed. Thank you for the help!
Yeah, sometimes it just takes a while for your node to discover (and be discovered by) other peers... Is the sync progress actually increasing now that you have a good number of connections? ???


Title: Re: Armory 0.96.5
Post by: RoadStress on February 21, 2021, 02:50:28 PM
Is there a way to speed up the Scanning part when importing a new wallet? Is the CPU the bottleneck or it's something else?


Title: Re: Armory 0.96.5
Post by: goatpig on February 22, 2021, 12:17:16 AM
Disk IO is the primary bottleneck, then RAM, then CPU cores.


Title: Re: Armory 0.96.5
Post by: btcArmory user on March 07, 2021, 11:48:40 PM
I am running armory 0.96.3.992-beta-8a 7f18a499
qt version 5.9.8
armory offline 0.92.3

I was not running these versions when issues first came up. I attempted to send my BTC. I have a signed transaction that was never broadcast to the network. At that point, bitcoin-qt was out of sync, preventing the transaction from being broadcast, the way it looks. My previous posts have indicated the issues that were encountered getting past that. I have rebuilt the bitcoin database. I have an empty qt wallet and listed, but apparently inactive (grayed-out) wallets for primary and watching wallet on my online system. The balances are (...) on each wallet.
I still have the signed transaction on a usb drive. Where do I go from here? It's probably really easy... I hope.

In armory, 'preparing databases' and 'scanning transaction history' are not active at all - they are grayed out. The wallet consistency check runs successfully in the lower left on armory startup.

I have my armory log file. Is it possible that my Satoshi data dir is pointing to the wrong folder? I must have installed the upgrade into a new folder on the external drive.


Title: Re: Armory 0.96.5
Post by: HCP on March 08, 2021, 02:33:06 AM
I am running armory 0.96.3.992-beta-8a 7f18a499
qt version 5.9.8
armory offline 0.92.3
What is the actual Bitcoin Core version? "Qt" is a library used by Bitcoin Core to display the GUI ;)

Use the: "Help -> About Bitcoin Core" menu option...

If it is anything higher than 0.17... chances are good that it won't play nicely with the older versions of Armory.

You'd need to install the latest 0.96.5 release from: https://btcarmory.com/


Quote
I still have the signed transaction on a usb drive. Where do I go from here? It's probably really easy... I hope.
What are you wanting to achieve at this point? Continuing to use Armory on an ongoing basis or just sending the signed transaction?

Depending on the format of the signed transaction... You might be able to simply copy/paste the contents of the signed transaction file into a transaction broadcast tool like these:
https://coinb.in/#broadcast
https://live.blockcypher.com/btc/pushtx/

Etc... The signed transaction would need to be in raw hex format for this to work.


Title: Re: Armory 0.96.5
Post by: btcArmory user on March 08, 2021, 05:21:14 AM
It was bitcoin core 0.20.1

I downloaded and extracted the indicated version of armory. The executable runs and lists the right version - 0.96.5
Transactions do not appear, and I still have a 0 balance. Shouldn't my BTC have been restored to the wallet? I can't see any difference after the upgrade. The armory log file is also identical to the one before the upgrade.
In terms of where I would like to go from here: ideally, I would see the BTC in the wallet again, and then I would generate another transaction. This time, the transaction would be broadcast to the network.

The signed transaction file is a .SENT.tx and begins with a delimiter and this, like a header TXSIGCOLLECT

It has a mixture of upper and lower case letters; alphanumeric chars. HEX has a mixture of counting numbers and upper case letters, 0 through F -- right?


Title: Re: Armory 0.96.5
Post by: HCP on March 08, 2021, 08:24:35 PM
Yeah, Armory is using a custom unsigned/signed transaction format for the files (possibly Base64 encoded)... Although, theoretically, you should be able to click "Offline Transactions", then "Load File", load the signed transaction and then click "Copy Raw Hex", which would give you the hex you need to verify/broadcast the transaction using one of the transaction broadcast tools (or using Bitcoin Core and the decoderawtransaction and sendrawtransaction commands on the console).

Without actually being able to see the Armory log files, it is difficult to determine why the transactions are not showing... it could be that Bitcoin Core is pruned so that Armory is not able to build it databases properly... it's possible that Armory cannot find your Bitcoin Core data blocks (if you used a "custom datadir" Bitcoin Core)... it's possible that there is corrupt data in the Armory database so it is not working properly.

At this point, I would suggest 2 things:

1. Goto the Armory data directory and delete the armorylog.txt and dbLog.txt files. That will clear out any "old" debug/error messages so we don't have to wade through lines and lines of irrelevant log data.

2. Try using the "Help -> Rebuild and Rescan Databases" option.

Then shutdown Armory and Bitcoin Core. Then start Bitcoin Core and make sure it is fully synced, then start Armory. If, after it has rebuilt the databases, it still isn't showing your transactions, then post up the contents of your armorylog.txt and dbLog.txt files (copy/paste to https://pastebin.com and then click "create new paste", then copy/paste the unique URL that is generated into your post here)


Title: Re: Armory 0.96.5
Post by: Gazz7483 on March 09, 2021, 08:52:37 PM
Hi,

I'm hoping someone can help with a problem I'm having.

I'm running Armory 0.96.5 on a Windows 10 Pro PC.  Bitcoin-qt is up to date and Armory is online but in the corner it says "Connected (0 blocks)".  When I hover the cursor over it, it says RPC disabled.  Could this be something to do with it being connected but not updating the blocks?

Thanks in advance  :)


Title: Re: Armory 0.96.5
Post by: HCP on March 09, 2021, 11:10:21 PM
I'm running Armory 0.96.5 on a Windows 10 Pro PC.  Bitcoin-qt is up to date and Armory is online but in the corner it says "Connected (0 blocks)".  When I hover the cursor over it, it says RPC disabled.  Could this be something to do with it being connected but not updating the blocks?
Correct... Your Bitcoin Core is probably not configured to enable the RPC server. By default, running Bitcoin Core GUI does not switch this on.

- Shutdown Armory and Bitcoin Core
- add the following to your bitcoin.conf file:
Code:
server=1
- Start Bitcoin Core and let it fully sync
- Start Armory

Also, is your Bitcoin Core running in "pruned" mode? ??? Check "Settings -> Options -> Main" and see if the "Prune block storage" option is ticked (or if you have a "prune=" line in your bitcoin.conf file). If you have either of these things, then Armory will not work properly.

If you're still having issues after adding the server=1 line and ensuring that Bitcoin Core is not in pruned mode... you'll need to post your logs (copy/paste the contents of your armorylog.txt and dbLog.txt to https://pastebin.com/ click "create new paste", then copy/paste the uniquely generated URL here)


Title: Re: Armory 0.96.5
Post by: Gazz7483 on March 09, 2021, 11:42:04 PM
Hi HCP,

Thanks so much for the quick reply  :)

I added the server=1 line and it's made a difference - where it says "Connected (0 blocks)", this has now changed from purple to green.

When I installed Bitcoin Core last week, I know I set it to pruned :-[  I'll change this setting now and see if this sorts the problem!

Thanks again,

Gary


Title: Re: Armory 0.96.5
Post by: HCP on March 10, 2021, 12:00:08 AM
I added the server=1 line and it's made a difference - where it says "Connected (0 blocks)", this has now changed from purple to green.
Excellent... one problem solved! ;)


When I installed Bitcoin Core last week, I know I set it to pruned :-[  I'll change this setting now and see if this sorts the problem!
Ok... do note that this will require some 350-400Gigs worth of storage space available on the drive where Bitcoin Core is storing the blocks. If you don't have this storage space available, you'll need to either move the storage to a bigger drive or perhaps use an external drive for block storage (not recommended due to I/O bottlenecks on external drives slowing down syncing)

You are also going to need to redownload and reverify the entire blockchain again :-\ This will likely take a "long time"™


Title: Re: Armory 0.96.5
Post by: btcArmory user on March 10, 2021, 03:04:26 PM
I downloaded this version of the .zip file and extracted it at the root level of an external drive.
armory_0.96.5_win64
When  the extract had completed, there was an Armorystandalone directory in the path. Is that the way is should be?
Maybe I should be using the win64 installer instead of downloading the .zip file?
Armory is offline, according to a message in the lower right of the dashboard.
Added server=1 to bitcoin.conf

The armorylog.txt starts with entries from 2017, so I cleared it out. Syncing bitcoin core so that I can restart armory. I will post the armorylog.txt later on.
This might be an old version of dblog:

https://pastebin.com/xLRHewqk







Title: Re: Armory 0.96.5
Post by: HCP on March 10, 2021, 08:46:14 PM
I downloaded this version of the .zip file and extracted it at the root level of an external drive.
armory_0.96.5_win64
When  the extract had completed, there was an Armorystandalone directory in the path. Is that the way is should be?
Maybe I should be using the win64 installer instead of downloading the .zip file?
It really depends on how you want it setup... if you just want Armory in a "standard" windows location (ie. the "C:\Program Files" directory) along with all your other apps and to have the Windows Start menu icons automatically created etc, then you should use the Windows Installer. If you want to run it from a portable USB drive, then the standalone would be the way to go.

If you want to use a custom install location... then either will work... but the installer is probably easier and, again, it will automatically create the Start menu icons etc.


Title: Re: Armory 0.96.5
Post by: btcArmory user on March 11, 2021, 10:32:32 PM
I have noticed the armory process still running in Windows. I have started to kill that using task manager prior to launching armory. This message has come up a few times after stopping and then restarting bitcoin core.
Cannot obtain a lock on d:\BTC datadir 96-2 - bitcoin core directory. Bitcoin core is probably already running.

Could that be related to the armory process that has been running after exiting armory?

I used the first line command to launch armory when the posted log files were produced. I have tried the second one, too. I can't shake the thought that the executable might be tryiing to access the wrong datadir. The bitcoin core database files are definitely active in d:\btc datadir 96-2\blocks

D:/armory 0_96_5/armory_0.96.5_win64/ArmoryStandalone/armoryqt -- datadir=d:\armory 0.96.3.992\Armory
D:/armory 0_96_5/armory_0.96.5_win64/ArmoryStandalone/armoryqt -- datadir=d:\btc datadir 96-2\Armory

Tried running the 'scan armory databases' from the help menu in armory. Armory is still offline, and is not coming up beyond the scanning transaction history utility in the lower right on startup.

https://pastebin.com/NxzspU0s

https://pastebin.com/exmFXEyR


Title: Re: Armory 0.96.5
Post by: HCP on March 11, 2021, 11:43:11 PM
Firstly, you're using the the commandline arguments incorrectly... there should not be a space between the -- and the command...
Code:
D:/armory 0_96_5/armory_0.96.5_win64/ArmoryStandalone/armoryqt --datadir=d:\armory 0.96.3.992\Armory

Trying to use the "old" Armory data directory may cause issues due to changes in the data structure... not sure if it did change much... but it is possible.


I have noticed the armory process still running in Windows. I have started to kill that using task manager prior to launching armory. This message has come up a few times after stopping and then restarting bitcoin core.
Cannot obtain a lock on d:\BTC datadir 96-2 - bitcoin core directory. Bitcoin core is probably already running.

Could that be related to the armory process that has been running after exiting armory?
Most likely what was happening was that Armory was spawning a hidden "bitcoind" process in the background... as Armory then got "stuck", after you closed the GUI, the background bitcoind process was still running and preventing you from starting Bitcoin Core GUI ("cannot obtain lock" etc).


Personally, if I were you, I would:

1. Download and install the Armory Windows Installer: https://github.com/goatpig/BitcoinArmory/releases/download/v0.96.5/armory_0.96.5_win64.exe
2. Start Armory
3. In Armory "File -> Settings..." menu:
  - UNTICK the box that says "Let Armory run bitcoind/Bitcoin Core in the background"
  - Set the "Bitcoin Home Dir" to be: D:\btc datadir 96-2\
4. Shutdown Armory and then Reboot the computer (this will definitely kill off any "ghost" processes in the background)
5. Start Bitcoin Core GUI manually... make sure it is fully synced before doing the next step
6. Start Armory

If you're still having issues... repost the log files after you have done all of the above.


Title: Re: Armory 0.96.5
Post by: btcArmory user on March 12, 2021, 06:26:25 AM

I have completed all the steps listed. It looks like armory should be back online and scanning databases, but it's not.

https://pastebin.com/35QvGKmt

https://pastebin.com/qsp4Jbrz



Title: Re: Armory 0.96.5
Post by: HCP on March 12, 2021, 11:20:21 AM
It's still attempting to read the Bitcoin block data from the "default" path... did you set the "Bitcoin Home Dir" to: D:\btc datadir 96-2\ ? ???
Code:
2021-03-11 22:10:42 (ERROR) -- BDM.pyc:197 - DB error: C:\Users\enduser\AppData\Roaming/Bitcoin/blocks is not a valid path

Also, is that the same directory that is shown in Bitcoin Core as the "Datadir" when you look at the "Window -> Information" screen within Bitcoin Core GUI?


Title: Re: Armory 0.96.5
Post by: btcArmory user on March 12, 2021, 02:50:35 PM
Quote
It's still attempting to read the Bitcoin block data from the "default" path... did you set the "Bitcoin Home Dir" to: D:\btc datadir 96-2\ ?

Yes, I did that in Armory. I used the GUI. will have to verify the setting for bitcoin core later on.


Title: Re: Armory 0.96.5
Post by: btcArmory user on March 12, 2021, 05:29:39 PM
Confirmed. Both bitcoin core and armory are set for d:\btc datadir 96-2
Neither has the backslash after the name of the directory, btc datadir 96-2

Could that be a factor? It looks as if the system using the default path.


Title: Re: Armory 0.96.5
Post by: HCP on March 12, 2021, 08:44:36 PM
That is very bizarre... did you shutdown and restart Armory after setting that Bitcoin Home Dir location? ???

And just confirming that your Armory settings look exactly like this:
https://talkimg.com/images/2023/11/15/zItDH.png

Box unticked... "Bitcoin Install Dir" is empty... "Bitcoin Home Dir" is set to d:\btc datadir 96-2... and "Armory Database Dir" is empty? ???



Also, is there an armory.conf file in this location: C:\Users\enduser\AppData\Roaming\Armory\


Title: Re: Armory 0.96.5
Post by: btcArmory user on March 13, 2021, 07:29:57 PM
My configuration is exactly like the one you posted. i have repeatedly closed down armory and bitcoin core and restarted the PC. I checked for the armory.conf file in the appdata\roaming\Armlory subdirectory on the C: drive. There is no file by that name, but there is an ArmorySettings with the value for SatoshiDatadir set appropriately.


Title: Re: Armory 0.96.5
Post by: btcArmory user on March 15, 2021, 12:02:30 AM

OK, I am waiting for further direction.


Title: Re: Armory 0.96.5
Post by: HCP on March 15, 2021, 04:36:34 AM
Ok, I have responded to your PM (and provided some alternative contact methods if you are having issues with the PM send limit that "newbie" accounts have here on Bitcointalk)...

Note that I'm travelling on business over the next day or so, so might not be able to respond immediately, but I'll do my best... in the meantime, if you could try posting up the latest versions of your log files, I'll take a look and see if the changes seem to be reflected in the log files.


Title: Re: Armory 0.96.5
Post by: btcArmory user on March 15, 2021, 01:45:57 PM
https://pastebin.com/WkZWvTbw
https://pastebin.com/pg7m0tZP

current logs


Title: Re: Armory 0.96.5
Post by: HCP on March 15, 2021, 07:20:19 PM
Have you not attempted to start Armory for a couple of days? ???

The last timestamp in the log file is from 13th March.
Code:
2021-03-13 11:20:32 (ERROR) -- BDM.pyc:197 - DB error: C:\Users\enduser\AppData\Roaming/Bitcoin/blocks is not a valid path
2021-03-13 11:20:32 (INFO) -- ArmoryQt.py:1923 - Setting netmode: 0
2021-03-13 11:20:32 (INFO) -- ArmoryQt.py:1905 - loadBlockchainIfNecessary
2021-03-13 11:20:32 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2021-03-13 11:20:32 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
It still seems to be attempting to use the "default" Bitcoin Core datadirectory for some reason... I'm not sure why setting the path in the Armory settings is not being recorded correctly.

What directory is your bitcoin-qt.exe file in? Is it in "C:\Program Files\Bitcoin"? or is it somewhere else? ???



Title: Re: Armory 0.96.5
Post by: btcArmory user on March 15, 2021, 11:22:47 PM
I have at least two versions of bitcoin-qt installed. The one that I have been launching is on the d: drive. I'll shut down and then try the one in the path you indicated on the c: drive.

bitcoin-qt on the c: drive launches 0.14.2
the version on the d: drive - d:\bitcoin\bitcoin-qt launches 0.20.1

I  am trying to import a .jpg of the d:\ listing

How does that work on this blog?

There are a number of related directories on the d:\ drive.


Title: Re: Armory 0.96.5
Post by: btcArmory user on March 18, 2021, 10:22:57 PM
Maybe this will help to show where the path is being misdirected. Since the upgrades to bitcoin core 0.20.1 and Armory 0.96.5 this watching wallet installation has been offline and does not scan databases.

https://pastebin.com/5C5zQ3fh

Please let me know if anyone can see a configuration tweak that will get armory running again. Will it be necessary to upgrade bitcoin core from 0.20.1 to 0.21.0?


Title: Re: Armory 0.96.5
Post by: HCP on March 18, 2021, 11:12:26 PM
Aside from the "DB Error" issue with your blocks file not being "valid".... this is also of concern:
Code:
(ERROR) ArmoryQt.py:2180 - ***WARNING: Wallet could not be loaded: C:\Users\enduser\AppData\Roaming\Armory\armory_2ot51ac3y_.wallet (skipping)
Traceback (most recent call last):
  File "ArmoryQt.py", line 2140, in loadWalletsAndSettings
  File "armoryengine\Timer.pyc", line 99, in inner
  File "armoryengine\PyBtcWallet.pyc", line 2156, in readWalletFile
  File "armoryengine\PyBtcWallet.pyc", line 2457, in doWalletFileConsistencyCheck
  File "shutil.pyc", line 133, in copy
  File "shutil.pyc", line 97, in copyfile
IOError: [Errno 13] Permission denied: u'C:\\Users\\enduser\\AppData\\Roaming\\Armory\\armory_2ot51ac3y_.wallet'

Seems like you have some Windows permissions issues... Armory is not able to read the wallet file... are you able to view the properties of that file and see who the "owner" is? Are you running Armory as "administrator"? ???



Title: Re: Armory 0.96.5
Post by: btcArmory user on March 19, 2021, 01:59:54 AM
I am currently syncing up bitcoin core. Would it be typical to start bitcoin core using the bitcoin-qt executable?

I found an armory settings file with no appropriate data directory setting. It's in d:\btc

https://pastebin.com/yJPGf3e4



Title: Re: Armory 0.96.5
Post by: btcArmory user on March 19, 2021, 02:26:52 AM
Quote
are you able to view the properties of that file and see who the "owner" is? Are you running Armory as "administrator"?

The owner is 'enduser' - it's the only login that is being used on this system. I will see if I can run armory as administrator when the time comes. Maybe my armory 0_96_5 installation is still misconfigured? There are no current files in the \appdata\roaming\armory directory. There are only files from 0.96.3. It looks as if the 0_96_5 are all in the d:\armory 0_96_5 directory.

How much simpler and easier would it be to reinstall everything on a new system and restore the wallet for watching only?


Title: Re: Armory 0.96.5
Post by: btcArmory user on March 19, 2021, 05:27:02 AM
Bitcoin core is not running anymore. I can launch the splash page that checks wallet consistency. Then it says done loading
Bitcoin core never opens up and syncs. I tried running Bitcoin Core and Armory as administrator. I don't know what could have happened.


Title: Re: Armory 0.96.5
Post by: btcArmory user on March 19, 2021, 02:40:43 PM
Install bitcoin core 0.21.0 and then reinstall the .exe version of armory 0_96_5? Install the armory to the C:\...\appdata\roaming\armory directory? Last time, I probably installed to the d:\ drive.


Title: Re: Armory 0.96.5
Post by: btcArmory user on March 20, 2021, 12:31:23 PM
Does anyone have an idea as to where to go from here? It looks like everyone else has dropped off this thread.


Title: Re: Armory 0.96.5
Post by: goatpig on March 22, 2021, 03:58:03 PM
Make a thread dedicated to your specific issues please. This isn't really the place.


Title: Re: Armory 0.96.5
Post by: HCP on April 02, 2021, 02:08:46 AM
Does anyone have an idea as to where to go from here? It looks like everyone else has dropped off this thread.
Apologies... I had a rather unexpected "hospital adventure" that literally put me out of action for the better part of 2 weeks :(

As goatpig has suggested, you might want to create your own thread and we can start afresh and see if we can't get Armory and Bitcoin Core up and running on your machine.

A completely fresh start on a fresh system would definitely be the easiest way, but should not be necessary. The trick is to take things one step at a time...

1. Get Bitcoin Core setup and running properly (This includes getting it setup and using any "custom" locations" that you want, which seems to be applicable in your situation)
2. Make sure that Bitcoin Core is fully synced. This is very important. Armory will likely do weird things until Bitcoin Core is fully synced.
3. Get Armory up and running (and setup using any "custom" locations) and talking correctly to Bitcoin Core.


Using Windows 10, Armory 0.96.5 and Bitcoin Core 0.21 it should be relatively easy to get it all going.


Title: Re: Armory 0.96.5
Post by: Aurik on May 16, 2021, 11:01:37 PM
Dear,

is the software (armory) still maintained or updated?
So are there any plans to get 0.97 out? If so, any eta?

Thanks.


Title: Re: Armory 0.96.5
Post by: HCP on May 16, 2021, 11:47:06 PM
is the software (armory) still maintained or updated?
Yes... the website to use is here: https://btcarmory.com/
The github is here: https://github.com/goatpig/BitcoinArmory


So are there any plans to get 0.97 out?
Yes.


If so, any eta?
Im not good with ETAs, don't ask. Soon (TM)
Soon™ :P


Title: Re: Armory 0.96.5
Post by: jnagyjr on June 20, 2021, 12:39:34 AM
is the software (armory) still maintained or updated?
Yes... the website to use is here: https://btcarmory.com/
The github is here: https://github.com/goatpig/BitcoinArmory


So are there any plans to get 0.97 out?
Yes.


If so, any eta?
Im not good with ETAs, don't ask. Soon (TM)
Soon™ :P

Will this new version recognize more than 447,219 blocks?


Title: Re: Armory 0.96.5
Post by: HCP on June 25, 2021, 04:25:59 AM
Will this new version recognize more than 447,219 blocks?
The current version (0.96.5) works perfectly fine and syncs all the way up to the current block height:
https://talkimg.com/images/2023/11/14/zNw4w.png


If you are having issues with Armory 0.96.5 and it is only syncing up to 447219, then there is something wrong with your setup... either Bitcoin Core hasn't actually synced past that block (out of diskspace etc) so the data isn't available for Armory to scan or it could be that you have corrupted blockchain data and it is causing Armory to crash.


If you'd like assistance getting your Armory synced up properly, then I would suggest that you start a new thread, describe your issue as best as you can and make sure that you post your armory logs (ie. armorylog.txt and dblog.txt) to https://pastebin.com/ and copy/paste the generated pastebin links in your thread.


Title: Re: Armory 0.96.5
Post by: NotATether on July 13, 2021, 01:46:15 PM
One annoying detail as a result of goatpig's Armory forking from etothepi's version is that the new, forked Armory can't be searched on Github because it has less stars (401) than the parent repo (677). This causes Github not to index the fork and as a result you can only search for code & issues on the old outdated parent.

[I could just clone it and search offline but it's not as good as on Github]

It was inconvenient to the point where I cloned and uploaded my own copy (https://github.com/ZenulAbidin/armory) just to enable this feature, though I apparently pushed a really out of date version from 2018.

So if you're reading this and you have etithepi's repo starred, unstar it, and star goatpig's Armory I guess, so that Github will finally index it for searching.


Title: Re: Armory 0.96.5
Post by: RoadStress on October 01, 2021, 08:13:57 PM
A bit offtopic question, but I don't know where to ask. Can I send BTC to a native SegWit bc1 address using Armory 0.96.5 + Core 0.19.1? And just for further info: Is any bitcoin core client able to send to a bc1 address?
Thanks!


Title: Re: Armory 0.96.5
Post by: BitMaxz on October 01, 2021, 11:32:34 PM
A bit offtopic question, but I don't know where to ask. Can I send BTC to a native SegWit bc1 address using Armory 0.96.5 + Core 0.19.1? And just for further info: Is any bitcoin core client able to send to a bc1 address?
Thanks!

It seems the current latest version of the armory doesn't support it yet but it might support on their armory 0.97 they don't release it yet.

Read this part
Quote
Break backwards compatibility for unsigned transactions carrying bech32 outputs. Older versions cannot make sense of bech32 addresses, therefore they shouldn’t be able to sign the transaction at all.
Fixed

Look at their release note here https://btcarmory.com/0.96.5-release/

Armory does not fully support bech32 but they support segwit address that starts with 3 or with script type: p2sh-p2wpkh

If you want a wallet that fully supports segwit I would suggest you check Electrum wallet or wait for a new armory release.


Title: Re: Armory 0.96.5
Post by: goatpig on October 02, 2021, 06:58:40 AM
You can send to bech32 addresses (bc1) in 0.96.5. What you cannot do is generate these addresses from Armory wallets.


Title: Re: Armory 0.96.5
Post by: nc50lc on October 03, 2021, 07:00:20 AM
-snip- And just for further info: Is any bitcoin core client able to send to a bc1 address?
Almost all "Bitcoin clients" including Armory can now send to bech32 addresses, only those that aren't maintained or oppose the soft-fork can't.
You can customize this list: https://bitcoin.org/en/choose-your-wallet?step=5&platform=linux (https://bitcoin.org/en/choose-your-wallet?step=5&platform=linux) (link set to linux);
then click a wallet name to see if it has "✓SEGWIT" which means it supports SegWit; additionally, "✓BECH32" if it can generate bc1 addresses.


Title: Re: Armory 0.96.5
Post by: Ethorsen on November 08, 2021, 01:34:28 PM
Hi guys,

Is there any foreseeable problems with usage of Armory 0.96.5 and the incoming Taproot soft-fork?

Thx


Title: Re: Armory 0.96.5
Post by: goatpig on November 08, 2021, 07:28:22 PM
0.96.5 won't be able to spend to native taproot addresses. I'm working to add full support for that address format among other things.


Title: Re: Armory 0.96.5
Post by: AM0751 on May 13, 2022, 09:51:36 PM
Hi all,

I downloaded armory 0.96.5. I wanted to check the integrity of the downloaded file, but for that I need to use GPG4win.
The instruction video to check the integrity of the download on the armory website is from 2014 I believe.
It says I need an offline signing key. I believe that is 4922589A. However, if I input that into GPG4win it doesn’t find anything. So I am stuck, not even mentioning the fact that this method might be completely outdated.

Question: how do I check the integrity of the Armory 0.96.5 download on my computer?
Thanks in advance.


Title: Re: Armory 0.96.5
Post by: nc50lc on May 14, 2022, 02:53:50 AM
Question: how do I check the integrity of the Armory 0.96.5 download on my computer?
I can't seem to get a result with Kleopatra's server lookup either.
In the latest version of the website (btcarmory.com/docs/verify (https://btcarmory.com/docs/verify)), the link to the signing key seems dead, to make it work, just add &op=index at the end of the link's url.
Then import goatpig's signing key from the result: 8c5211764922589a

Then do the rest of the tutorial.


Title: Re: Armory 0.96.5
Post by: goatpig on May 16, 2022, 06:43:02 AM
https://github.com/goatpig/BitcoinArmory/releases

Github release page has the sig files as well.


Title: Re: Armory 0.96.5
Post by: AM0751 on May 31, 2022, 07:11:49 PM
Hi all,

Thanks for the help so far, but I must be incredibly dumb.
I can’t get it to work, and I can’t move forward and copy this install file on my airgapped computer without me knowing it is 100% legit.

I downloaded the version of Kleopatra that is in the tutorial on http://www.bitcoinarmory.com/tutorials/armory-basics/verify-download/

I adjust the settings, and then I input the signing key 4922589a
It tells me I seem to be looking for a fingerprint or key-id. And to add a prefix if my search does not yield any results.
Both options give me zero results.

I have no idea what I am doing wrong. Any help would be much appreciated.

Thanks in advance.




Title: Re: Armory 0.96.5
Post by: BitMaxz on June 01, 2022, 12:19:47 AM
Hi all,

Thanks for the help so far, but I must be incredibly dumb.
I can’t get it to work, and I can’t move forward and copy this install file on my airgapped computer without me knowing it is 100% legit.

I downloaded the version of Kleopatra that is in the tutorial on http://www.bitcoinarmory.com/tutorials/armory-basics/verify-download/

I adjust the settings, and then I input the signing key 4922589a
It tells me I seem to be looking for a fingerprint or key-id. And to add a prefix if my search does not yield any results.
Both options give me zero results.

I have no idea what I am doing wrong. Any help would be much appreciated.

Thanks in advance.




I also tried to verify it with Kleopatra it seems it didn't work.

Anyway, have you checked the last part of the video from that guide you can verify if the software is genuine by creating checksums it will generate a new file with the name sha256sum.txt open it with notepad.

Now download the sha256sum.txt.asc from the link posted by goatpig above and open it again with a notepad it should show the list of hash and the pgp signature under the Signed message or Sha256 hash check the installer hash and compare it with the hash that you created recently under sha256sum.txt.
It should be the same if not then the installer you download is fake or clone.


Title: Re: Armory 0.96.5
Post by: goatpig on June 01, 2022, 07:08:04 AM
You should really use GPG from the terminal instead of a GUI solution. The signature process for Armory is the same as Core: save the sha256sum for each package to a text file, then sign that file. Therefor to verify the package, you have to do things:

- Check the packages sha256sum matches the one in the hash file (for the same name). This is as simple as running `sha256sum *package filename*` in the terminal/powershell and comparing with the entry in the hash file for the same file name.

- Check the signature on the hash file is valid. For you can run `gpg verify *hash filename*`. If you have public key in your keystore, it should tell you the sig is valid.


Title: Re: Armory 0.96.5
Post by: nc50lc on June 01, 2022, 08:14:31 AM
I downloaded the version of Kleopatra that is in the tutorial on http://www.bitcoinarmory.com/tutorials/armory-basics/verify-download/

I adjust the settings, and then I input the signing key 4922589a
It tells me I seem to be looking for a fingerprint or key-id. And to add a prefix if my search does not yield any results.
Both options give me zero results.
In my previous reply, I also mentioned that Kleopatra yields zero result at my end.
Instead, I manually imported the one suggested in the tutorial but added "&op=index" at the end of the link for the link to work.

So, instead of keyserver.ubuntu.com/pks/lookup?search=goatpig, it should be: keyserver.ubuntu.com/pks/lookup?search=goatpig&op=index (https://keyserver.ubuntu.com/pks/lookup?search=goatpig&op=index)
Then, click on "8c5211764922589a", copy everything on the page from "-----BEGIN PGP PUBLIC KEY BLOCK-----" to "-----END PGP PUBLIC KEY BLOCK-----".

Open Kleopatra, click on "Notepad", paste the text there and click "Import Notepad".
After that, certify that the one you're importing is correct; e.g.: ask goatpig himself if the fingerprint (below) is correct.
Lastly, tick the checkboxes and finish the rest of the process.


Title: Re: Armory 0.96.5
Post by: goatpig on June 01, 2022, 10:05:24 AM
Code:
pub   rsa4096 2015-11-22 [SC]
      745D 707F BA53 968B DF63  AA8D 8C52 1176 4922 589A
uid           [ unknown] goatpig (Offline signing key for Armory releases) <moothecowlord@gmail.com>

This is my offline signing key's fingerprint. The short hand fingerprints you are finding either show the last 2 or the last 4 hexit packets of the full fingerprint

Code:
-----BEGIN PGP PUBLIC KEY BLOCK-----

mQINBFZRUpgBEADN/akS+sMnPqG4VigcipiLUmdQIElf2Uj1KTIgR21ifR0xT1Ed
dPtUTIxxeHAYZQN1yanrmtBJmR6NeF7qkROJ4mAisLzrtW/UaIj868fnQv0y+mbc
VGg+NP947E8pRF368cN0RJELDOrKmY2lfyZ5ueq/gC04jFHBgjYfaqEIu8sd16nA
C5ir0ilNGV+FvXjP4BP3fZghTM4y2d69mA+VN4DKBbZce7BVl586ODKUU8flvrsA
N8uDmomIF+DVjPiH/+t0KOizLy8NxoLdzGpJOSktUQF0vhW9EwBkpGp9vVh8PUPU
WjI6orjyoAGQRQvD/oZu4iZCXXNRSHouMMClo9JoZlfbkplZ4EYXJZIlAYpUGolj
YoWf9I4GQHCn3nqcoG7E7u6u+2+thiTQG0QxTl7VE+cnlBAsPg1D86WhPzWzHueA
lvtwlChLCXlZifJFi7MlD3+ijg8o3V8qWMm+cwKJDR8gOvJ0AZ9t11TLPb15o63d
QKcDd++FAc1etCazZnvPH8pjo0+0FZtd870JRkCn9N8yqxlWccCmjaS1hbgYZd1W
8T8rtKDLCW0isZzzB74SpaHiMlcQOlIz2K6WGHqb6Fr2evpzX80LjqANaGXjjEJy
U7HYcT9ffOxm7Idisj6QbW5Y9s135YYg+LR55N/P3cm2FWg09IHVZjd/FwARAQAB
tEtnb2F0cGlnIChPZmZsaW5lIHNpZ25pbmcga2V5IGZvciBBcm1vcnkgcmVsZWFz
ZXMpIDxtb290aGVjb3dsb3JkQGdtYWlsLmNvbT6JAjgEEwECACIFAlZRUpgCGwMG
CwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEIxSEXZJIliadfIQAKsqhFZ3TyXs
u6M0iu6TMYzXcLhRclzxF3i6gsBk2QOn0/d4AOImuPj1lP2BwlH2WuMuej5ZcnJ7
s6xpDNi85AIO5ffq87P6PyX4uCp4mZKD/W9OGhHRBwwEwh3YeyN5nosDQS0kY2hR
Z8nidzIk2mtyeHBgV6jZlG+g3VkzXymmQ5TNMb1syL+MrNlZPnoFdaYW2xtwF8hB
CANry9JaN+F4sKLdewysegQBodkwQyepOsPlavJ+2I3bd0qqSKGmT3rrGmVGzm5g
h3TBHFJl6LAeqrxAegRnpcOnUrxphfnlT8pg7VLkj8lns2MmaZ9t8naQBAvOcGxp
LlXb7U+S04/fxde3TjFSd1WoK0c+XxBfc1p4w47pWaQ0pgQ4d13vuO8/XmqeUXxW
LnWR7Q9eNyPcEqwrRlI5RYAjHGJsYpWvkDx3WYLWMgCD57j9vU/40YX2BPxpKhbN
sngBMfToC49AHI4RDn9+Mc9PrhAjiB+DldTO3zFuJuBMd1EMUmr479i0y5/kzZFt
+Q2Kebyn8I1IVEXvrkQ4gfRiWKAhtOHQGvmviqGEyAhjrKYLRRJWWONbX6P1JC7/
l3L3cnu6PXMGS7XuaqhJqaslpmQrS1h9cMN4uCiUNmERgjQbbUOblzZhhGzeH5+Q
0zAMTm3hJr8ZYJXGRtrAiTAUSVhjJ/eXiQEcBBABCAAGBQJXICPTAAoJEL00DjdN
HMgQXncH/js8G6cqHau6XsZYVLi9hwvWVXuELss+CDjXW4EdiYQ9PHz/O7Zg/UHd
16rMuHNynS6+G144Ft3jqDWBLF27sziEAcOE9AN4kPEeNqw9la7ieyT9Bv6T39Z/
0Q9iZ/DPaZwNvm2CpE5R74o55cXKOFFqsMAkyANJ3DPcqedAWdllrPQvk2Y50bTd
3qoXLrSgUzuE9STXR47ulplF5SURMm9YEF2BCxkahgDSxpBOFNvMP/1QfAcm4Z7l
u2gvsPPCG9LCl0b6jWZTHdunpgvSEcH8I8cBBjHAWuHUKFvk/s+rJBCMQH6Oxs6f
YoF2HQYSQg68deNhTl6m70L8n9cxm+OJARwEEAEIAAYFAldU8XEACgkQo/9aebCR
iCTLoAgAl20DxjVIqxFfE0nXWmgk8l/N/VHmcWlt0nmwccTo3kll+/TlYyKwnDf2
u43jnZOJrJPFnqZ0Ycv8DjstsDdpxEZ5VfDi7FsRqcbQId9ADCprBZXP2KQuNu/c
jMF559V9DdJtBTpnRcUeZZZ2j8tcGpI08Ph6a5Tg3MP23N/ODrsv2CiCYZfbJpBc
jDijTp1Vk2MaUoiCT2tCcg35q+iWzLqu/iu5bzb1z+/72X0q8t8sarwvlsx0drWV
NbvnpDSNVe799GCpUxGJMfTGl2xmN/FuJJYyGJ3MpqPidh7vAszlD4iY1LN8dywg
tj8qC1WBBORDtCARI2XEkjWZY1hJlokCHAQQAQgABgUCV0SvqgAKCRACeCH/exz+
xpB4EACoyDmADNIMQJBbeYYey/aVtC1eyjXaA/kRVxpQWc8XX4pzbnDw0IBHicIt
L8oSyrf8Qf0di+x+BMD+0OKNN7OLQr3T2BPJEs73KRoUnUrjaT0ryBrp3jZ/05Xw
voNNekVtEe7oyOVBbkbGOwgneyMqUEGej4UC1eEcjkh4848ti0Wqkfc4gUzEc7wV
9qYz7kGhyDYUaqnIEMhNHebU1L3YW8OKDAFW90ihkTF6T6UIOrC+w1hgtT+GsECO
K1LAMTb4Uk/I1K6sVo9AbaFTr6S+P7936By0UE58y9fDmFQ0yyUFovuUoAkC7kpb
UBCUxYcGpQ9atezoce5mgoJls/2JQBRS8pFrnWxrCeMJINPzWItxDU4kMaHxtVV6
aqFEyc3j4h7ZdSjdAPidS+36NB9HF5nmtwcN+UaZ2I0x81XIpCSCl3be9uiDIrQQ
uqaXQv7NeWX6ruTpUaC3G8p/jtmg8B7ryD9uK8gW9mBHO9iGySu/NDh+ZY9Dlj4I
B0PquuNj6eRXgzGSiCytTqqaS0yRFUzJuxnVry+Dpx6Xc94Ujd482xBTBYz/VyzP
PPCT3eKILRPh7juM8PBv2NRe0g80gHIyZkGD3zZ1qCobwUJFOQWVMKX/wDCscJjF
Bzytv8AriryniaPw8nQ08ifsVsMgXXtx9IKr00L6am7rAUciD4kCHAQQAQgABgUC
V2M6hQAKCRBi2lJ29X08OhbAD/4zpHeex0ckxalhmJ7xEvHdOtCLWL220+fK6aEl
y6/ae9FE8DvtnWZpQaKeD0/znWU2ksnqVg6jHkh0OhgsE+ZxLwoGgIt2KOUkEccF
ETFX24rbVM/LR8vCL5SfI+muoyqcBCWiM8c+2W8BOxQV0K9w2dCChDwVVQU8TpgU
lOQGhgc9BBnxaO0JVDXD3YWXdVxI2gvGOtLRfZ7rFx7H7fPrjXNvT/Z/cNEtYM+1
C23O/rJW0x3Y+L1YUTu3FETQUq6GwKUs9XlQ6yhgluG4T2/RXZFGHf8G24qZpZl2
+k1wxtReplKRjN2kKH9D3CWlfxjxjzkl8tEjlXwT/K5EA5eNdY/Vu8CXmJ+gQLzb
FpQnljBBI9ttoQnH7FK1dXktxA2L7fdl9U9HUWKHPg8IrH8aA8TLlDIYMi1iJvWZ
piqDAH8ZUUP1N8UrzdtfK9lfXyV4+JYD5b/bvA1nxSJIsAxCdytKLGGYmhRK62qX
GJ2VKreocSA5pKTeQdz4/PLeaMj0EprmmEwu4f+JKD0HOWCHVKncrkpclDIsPbxB
yfcXnXOA2rkkH3EMOPvMGdiuQZnY3s+k2nfyVqSICHZaCQLFijdILIHncDDTvXjI
MP0WYZwFWukFRl0vwunKR1AbCv72HXZHKJKCXTMlwblb3ve+ErKxwrPFD4bU3Tm8
pideUYkBHAQQAQIABgUCWXs04QAKCRB/AiD48Q3xA69ACACaFHjl1us4S8PWs0aT
B3wuHacBbfLgO6sltpRnXYErHJzHZ14nK1pVGkMJjydddMLe++qI9b57qt4k3e7I
q64+M8ke5zKrHV3vr04xryVixS+4MgOz3FfiYY7RVzz6ZY/NgjCUeGQRIlGWIzmD
qVD4C42eCLYh4+/XchuhRYh5m4LMZfnL24dDAU6QD/4zQNmnSfd4GBmX5WRPmJOJ
vBPme5Ir0AS1DHw2FQ1XIH1lJcthkKA36V9tkyUXy4zN/m93ONCEM12BOrRu8l/k
gjBL6M4YjG7H6Ac2rlZFZbAJBOI7xRidkl+RCgfcaQOX2hLIC6n3uOCIUkO/TRuE
29aRiQIcBBABAgAGBQJam5eyAAoJEK0biQkblwbooBQP/1++zNtNOisaNsXkuGlQ
xtg2Oye6GUIEILBOZ09tcHkgl5UTCdmg5NeI3P5g+E5IJkgaOmagrUx/dCWFzVHX
Z5vS1Llyx0YFgyLqCCBjgSwon3qi9FWzvm6noTyY81ftmgxJS+0MUB8wttIO65Hr
vcD8d2XlFgB09rVsKWLZeMeP/kQI1oVspGYTeANO3xcLlDj3pXlSyZsoULstTLm6
8Kf+S+Qp95REFVFeqWCT1Tl04OppuyfCF9624LKhsja5EsUF1DzX13zkYmuljn0O
5Or5NBQwWUFQVPMet5OdvKydkzhw8lq9MCgHLKcv3nJLRPezEIRfwQDnZxrwvivw
kVU13F6WTPxvLc4l+TtsA7lagKjMUCDVnISpk6MFXyLry88dnT5RhREdWXgk9ry7
gHgsdxkQ564IQG1GgqblgzUB/4DhKSRqlTvSN5kg1Y6BtdVO+e2uxBLoGKnVWemt
MsgpAWHnmFUBtlwJzDISVeRlRMiJaTz2dbXFW0NSK7L1LQBjH4hbdBdFIQLUwIY4
fAJYkr6b1Dyf/172lXX5H+3ZwOAlEG6mnGZrVQWpXYSaTyn2yKosdK2wHCk0oGxV
9SRZRSi7L7aKMST6fJxc/uvF2kUgY1MKsWpa0XqOkkzw7hpRF1v/9pBfU1FSbmGb
EIA42p8eQRf7zvD0ExccgdLiiQEzBBABCAAdFiEEcDSnqhxCC9+KsldSIh4BWJIH
xdMFAlriC9cACgkQIh4BWJIHxdOuHwf/St38MSxYu70xfAUGFvjQWDuh4uenOMB5
EVBUxixJ3E1L3REGiu4dDJQqCZ+QIh7BZ5ZP7tsMbr5d/F+tziex66NgdoL6nIBl
Tv5ktubejdrwBUmVf/Fam1ep1fHU2NSPJUB9BZX4dE+BRQKSgJSPSoPZYrfSDFBh
S29ZPlukc0RlSlUF0VNtZGz4rdnBPZchkVGruEP5qcdTCIqzP1tKSsUm40rMs/YX
p/SObbABkKLd1PmGtut497yFLo+DogYxzeiR0UES0Q0/KuwqASRBJNGb2f0N7iV5
EtKYEthkEvfwdzsnhFMdSSrApYSS1rKTj90FIGrJonA56SLCjBXpI4kBSgQQAQgA
NBYhBDn4fkxfbpHorxzLznDPh0hJSdCABQJeBAGiFhSAAAAAAA0AAHJlbUBnbnVw
Zy5vcmcACgkQcM+HSElJ0ID11QgAvi5zMK3W50mGCLIgIlHvF4NOxkz0zWMdTyOL
aCmTmHf6FZ3FmGk3KPH8+8UmGZ797v94p92EBVcIRjX/GYiTmAC7ZtPFp04m2hgp
MQSx+LYeByBbDEKVYqi+pSEVbOzKHVqTunaW2kOZ7mXDuvdXYjwTbFS9H0K2JmAV
So7Zt4es0hFA2E20r8SKEL4b45B52ZG49MwoZEG9KD9ZY0pLEs+TAcOirzRnajHo
eNXTwWwa5NuoHSxZy6TMUm36T6dDkYbsiTxfAgxCnJzx1nIgBwGDUQYxgyQiPuAX
MGWoGui3z20CYHllwxGkSp1iIkMzHXvQ6W+o22pAl6DG0NFXnokBSgQQAQgANBYh
BDn4fkxfbpHorxzLznDPh0hJSdCABQJeBLJvFhSAAAAAAA0AAHJlbUBnbnVwZy5v
cmcACgkQcM+HSElJ0IBz1ggAjRw0Ap4dorO/wkMKx7qp0nyUKd4rI06PkVEmv/uQ
A1AQbNv8Boh9VdXprcWEYg8NAMa9QHpWXTmVaswQXpZtXCycpbk+U2M4wyteUR5R
RmUAt3D+b6buLyB4q/y0RjLUhf63M2JfVbaZDp236QdRJYVhhPeDg4IrXCLd6r2g
/qNSJHwZLNo2Cn8tMmf4dxoiuuDs1cNjagbf9gDqh0cJheN9LcQsdQARRjjdcHIi
LbMN6YENxwhEiIF6x+ZCu+y2wFSOid3LhVza6LoPmhS+bPRbvErmaIL2NwaaqsGT
WUFDmBk8qJbAzbhtw3qpnru3eo0D++rhDa7UfcZgekTcvYkBSgQQAQgANBYhBDn4
fkxfbpHorxzLznDPh0hJSdCABQJeBLKKFhSAAAAAAA0AAHJlbUBnbnVwZy5vcmcA
CgkQcM+HSElJ0IDoeQf/cUzd0Bgr3msVlc/FYBDPobWOYAwsTjTv95APDVvspcVR
gjz/bNoC/SolmDPs88AS1RqXkhSoO9jFokzqjwNeNDz/XfDtXNT7vWsPdLY0UpJx
glq/eYsWq+w+PJ5gGHEiafhbotQB9mh75SggWljjAURV+oaVn+AtUJsFYpfojZYK
BtbNUfJXvs57bzPJ25HQY0dTCbJ6dkiL0oDTNCWxzVWPBz+2Xii4GtyyVVxnf+9s
DLxmsHLWBKSMlZ9vjoay0MD0U4kZ2+2tcv4u1UqNdnTiuYKStmhUNe/memzcYSPg
MeVExGd09GdQsNwKtcFL9kzwZ0FpfbIvzMUWuc3+Gw==
=MOxo
-----END PGP PUBLIC KEY BLOCK-----

This is the key itself, with some sigs added




Title: Re: Armory 0.96.5
Post by: BitMaxz on June 01, 2022, 10:54:03 PM
I did try to verify it through command prompt as the administrator but it fails after verifying the installer with the signature even if I use the sha256sum.txt.asc or the above keys.

https://i.imgur.com/RLn5A90.png

I also got this below I tried to verify it with the sha256sum.txt.asc from releases but got this error below

Code:
C:\Users\~snip~\Downloads\Programs\New folder>gpg --verify sha256sum.txt.asc armory_0.96.5_win64.exe
gpg: not a detached signature


edit:
Since the error above gpg not a detached signature I tried to edit the sha256sum.txt.asc and remove the hashes or the whole PGP signed message and save only the PGP signature and this is the result below.

Code:
C:\Users\Test1\Downloads\Programs\New folder>gpg --recv-keys --keyserver keyserver.ubuntu.com 4922589A
gpg: key 8C5211764922589A: "goatpig (Offline signing key for Armory releases) <moothecowlord@gmail.com>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1

C:\Users\Test1\Downloads\Programs\New folder>gpg --verify sha256sumsignature.txt.asc armory_0.96.5_win64.exe
gpg: Signature made 24/12/2018 4:16:07 pm Malay Peninsula Standard Time
gpg:                using RSA key 8C5211764922589A
gpg: BAD signature from "goatpig (Offline signing key for Armory releases) <moothecowlord@gmail.com>" [unknown]


Title: Re: Armory 0.96.5
Post by: nc50lc on June 02, 2022, 03:24:17 AM
I did try to verify it through command prompt as the administrator but it fails after verifying the installer with the signature even if I use the sha256sum.txt.asc or the above keys.
-snip-
That's because "sha256sum.txt.asc" isn't the signature for the binaries.
It already contains both the signature of the message and the SHA256sum of each binaries (as signed message).

You verify the signed hash file via gpg --verify sha256sum.txt.asc to see if it's legit.
After passing verification, open it using your notepad or text editor, then compare the SHA256sum of the binaries to the listed SHA256 hashes.


Title: Re: Armory 0.96.5
Post by: BitMaxz on June 02, 2022, 11:57:39 PM
That's because "sha256sum.txt.asc" isn't the signature for the binaries.
It already contains both the signature of the message and the SHA256sum of each binaries (as signed message).

You verify the signed hash file via gpg --verify sha256sum.txt.asc to see if it's legit.
After passing verification, open it using your notepad or text editor, then compare the SHA256sum of the binaries to the listed SHA256 hashes.

That's the only thing that works for me the result is below.

Code:
C:\Users\Admin\Downloads\Programs\New folder>gpg --verify sha256sum.txt.asc
gpg: Signature made 24/12/2018 4:16:07 pm Malay Peninsula Standard Time
gpg:                using RSA key 8C5211764922589A
gpg: Good signature from "goatpig (Offline signing key for Armory releases) <moothecowlord@gmail.com>" [unknown]
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
gpg: WARNING: not a detached signature; file 'sha256sum.txt' was NOT verified!


I just trying to include the installer when verifying but it didn't work except on verifying only the sha256sum.txt.asc
So to make sure it's genuine I manually created the checksums with GpgEX and check the hash inside with the notepad and compared it to sha256sum.txt.asc the hash are the same so it's guinuine as I said on my previous suggestion above.


Title: Re: Armory 0.96.5
Post by: AM0751 on June 08, 2022, 09:54:06 AM
Quote
Open Kleopatra, click on "Notepad", paste the text there and click "Import Notepad".
After that, certify that the one you're importing is correct; e.g.: ask goatpig himself if the fingerprint (below) is correct.
Lastly, tick the checkboxes and finish the rest of the process.
Hi and thanks for your answer. I am somewhat closer, but I need to ask you; which version of Kleopatra are you using in this example?
I am using the old version to be able to follow the exact steps on the armory website.
Do you happen to use a newer version? Reason I ask is, in my version there is no “notepad” to be clicked.

Thanks for your patience.


Title: Re: Armory 0.96.5
Post by: nc50lc on June 08, 2022, 11:53:31 AM
Do you happen to use a newer version? Reason I ask is, in my version there is no “notepad” to be clicked.
I'm using 3.1.18.
The "Notepad" in mine is located next to "Lookup on Server..." if "Settings->Show Toolbar" is ticked; check if it's available in your menu "View->Notepad".
If not, you may have to upgrade Kleopatra.


Title: Re: Armory 0.96.5
Post by: BitMaxz on June 08, 2022, 11:17:50 PM
I'm using 3.1.18.
The "Notepad" in mine is located next to "Lookup on Server..." if "Settings->Show Toolbar" is ticked; check if it's available in your menu "View->Notepad".
If not, you may have to upgrade Kleopatra.

Ok, it works with the 4.0.2 and I follow the last part of their video on their guide https://youtu.be/zRljOC71VVc?t=191

https://i.imgur.com/QyoGBos.png

The last part is to verify it through clipboard and that's the result. I manually open the sha256sum.txt.asc with notepad and copy the hash of the installer and then open the checksum file of the armory installer and compare them and they both are the same. Meaning even if the result on Kleopatra couldn't verify the signature it should have the name, email, and keyID like the result of the image above and manually check the hash of both checksum and the hash under sha256sum.txt.asc.


Title: Re: Armory 0.96.5
Post by: nc50lc on June 09, 2022, 02:42:03 AM
Meaning even if the result on Kleopatra couldn't verify the signature it should have the name, email, and keyID like the result of the image above -snip-
That's good.
You can also "Certify" goatpig's certificate so the data can be verified (green);
he posted his fingerprint above, just compare it with the imported certificate's fingerprint.


Title: Re: Armory 0.96.5
Post by: Tolosi on January 09, 2023, 02:17:32 PM
Is there hope to see Armory with bc1 address generation capability soon?

Thar would be a nice feature allowing lower fees in the future.


Title: Re: Armory 0.96.5
Post by: Carlton Banks on January 09, 2023, 02:40:31 PM
Is there hope to see Armory with bc1 address generation capability soon?

Thar would be a nice feature allowing lower fees in the future.

you can send to segwit v0 (bc1) addresses, but you can't receive to them. I believe that's in the works (@goatpig ?) in Armory 0.97. there are also segwit v1 addresses (which also start bc1), but I imagine they will be rejected by Armory. No need to worry, these are taproot addresses, and they are not  commonly used yet.

i think you'll save somewhat on fees even when you're only sending to segwit v0 addresses (the bytesize of segwit v0 outputs is smaller IIRC)


Title: Re: Armory 0.96.5
Post by: goatpig on January 10, 2023, 08:29:10 AM
I believe that's in the works (@goatpig ?) in Armory 0.97.

It works in 0.97. I need to add taproot support and update the lib to support v1 segwit addresses. I'm stuck with day job and UI elements atm =(.


Title: Re: Armory 0.96.5
Post by: Carlton Banks on January 10, 2023, 02:26:58 PM
excellent news. not the day job/stuck with pyQt part :D


Title: Re: Armory 0.96.5
Post by: goatpig on January 10, 2023, 03:22:31 PM
excellent news. not the day job/stuck with pyQt part :D

I'm legit considering paying someone to redo the GUI in flutter/dart.


Title: Re: Armory 0.96.5
Post by: Carlton Banks on January 10, 2023, 05:03:53 PM
interesting choice. I'm frankly suspicious of the way that all these javascript dialects are proliferating and eating everything like an army of king kong/godzilla/ghostbusters marshmallow men, but on the other hand, QT is going weird, gtk already went weird, and they're the only game(s) in town.

I confess to knowing less than zero about javascript-ey thingys and widgets, but like every self-respecting opinionated asshole, I can tell you that I don't like it and that therefore it is bad. :D.


Title: Re: Armory 0.96.5
Post by: goatpig on January 11, 2023, 08:25:07 AM
interesting choice. I'm frankly suspicious of the way that all these javascript dialects are proliferating and eating everything like an army of king kong/godzilla/ghostbusters marshmallow men, but on the other hand, QT is going weird, gtk already went weird, and they're the only game(s) in town.

I confess to knowing less than zero about javascript-ey thingys and widgets, but like every self-respecting opinionated asshole, I can tell you that I don't like it and that therefore it is bad. :D.

The 3 issues i see with Qt:

- Qt5 will be EOL in 2025
- There are complaints about Qt6 licensing shenanigans
- There aren't that many people who are experienced with pyqt. Qt is typically used with C++. This limits my opportunities: It's hard to find a pro to deliver on the kind of GUI elements I'd rather not deal with.

Also, the qt GUI in Armory is straight up hardcoded into the python code files. This isn't very future proof. Cleaning that up would involve big rewrites, which is why changing graphical libs is on the table. For now I'm trying to hang by with what I got, but I'm warming up to the idea.


Title: Re: Armory 0.96.5
Post by: Tolosi on May 22, 2023, 07:18:42 AM
Before the Ledger fiasco I was contemplating moving coins to one of their devices. Reasons were convenience and security.

Now I am glad I did not.

Which makes me more interested *again* in using Armory as my primary air-gapped tool.

I I would really like to see bc1 addresses incorporated in Armory.

Hope that work on it is in progress.


Title: Re: Armory 0.96.5
Post by: goatpig on May 22, 2023, 07:59:21 AM
Before the Ledger fiasco I was contemplating moving coins to one of their devices. Reasons were convenience and security.

Now I am glad I did not.

Which makes me more interested *again* in using Armory as my primary air-gapped tool.

I I would really like to see bc1 addresses incorporated in Armory.

Hope that work on it is in progress.


You can spend to bc1 addresses in 0.96.5.

0.97 can generate them (my current spend wallet uses bech32). It's not very user friendly yet however.


Title: Re: Armory 0.96.5
Post by: Tolosi on May 22, 2023, 02:12:40 PM
Is 97.0 available for download in Windows?


Title: Re: Armory 0.96.5
Post by: goatpig on May 22, 2023, 04:53:18 PM
It's in a "build it yourself on linux" kinda state right now. I won't be looking at Windows builds until after I have a RC.


Title: Re: Armory 0.96.5
Post by: psymoon on February 01, 2024, 10:56:28 PM
Hi! I am creating a wallet with Armory, when it ask if I want to create a backup, I choose the printable paper backup and Single-Sheet option. When I click on Create Paper Backup, nothing happen... Am I doing something wrong?


Title: Re: Armory 0.96.5
Post by: nc50lc on February 02, 2024, 06:24:15 AM
Hi! I am creating a wallet with Armory, when it ask if I want to create a backup, I choose the printable paper backup and Single-Sheet option. When I click on Create Paper Backup, nothing happen... Am I doing something wrong?
There are others who reported the same issue.
Their solution is to skip the backup process during wallet creation and do it later once the wallet is created.

The only similar behavior I encountered in my test is if I selected another option like "Digital", then re-select "Printable Paper Backup".
After that, neither "Single-Sheet" nor "Fragmented" paper backup options are selected, using "Create Paper Backup" button does nothing as expected.
But I failed to reproduce the issue when 'Single-Sheet' is selected.


Title: Re: Armory 0.96.5
Post by: psymoon on February 02, 2024, 08:21:41 AM
Hi! I am creating a wallet with Armory, when it ask if I want to create a backup, I choose the printable paper backup and Single-Sheet option. When I click on Create Paper Backup, nothing happen... Am I doing something wrong?
There are others who reported the same issue.
Their solution is to skip the backup process during wallet creation and do it later once the wallet is created.

The only similar behavior I encountered in my test is if I selected another option like "Digital", then re-select "Printable Paper Backup".
After that, neither "Single-Sheet" nor "Fragmented" paper backup options are selected, using "Create Paper Backup" button does nothing as expected.
But I failed to reproduce the issue when 'Single-Sheet' is selected.

Thank you! Sorry i didnt read others report on this before.