Bitcoin over radio and TV is the future, and Armory helps make that happen.
See also inevitable discussion of how to avoid financial censorship using (not internet, but) radio - unlicensed MURS, and TV, at
https://github.com/bitsquare/bitsquare/issues/483#issuecomment-296042774
Topic: Armory 0.94 is out (Read 7138 times)
I've used Armory for several years now and 0.94.1 by far the most stable, reliable and efficient version I've used so far.
More improvements are planned, the developer (goatpig) has been doing some excellent coding and design.
Right now, Armory (and Bitcoin Core itself)1 are the only (maintained) wallets that operate as a complete participant on the Bitcoin network. This not only supports Bitcoin overall, but is also the best way to maintain the privacy of BTC transactions. There are several other advantages to Armory, but this is easily the most important IMO.
1(maybe Bitcore is a full node wallet too, but I don't trust Bitpay to put out clean code/binaries even if it is)
Just an FYI and a bit of a thanks. I've used Armory for several years now and 0.94.1 by far the most stable, reliable and efficient version I've used. I've got several instances running on Linux and Windows without a hiccup and with far less disk space and iops used.
There are other options certainly, but I sleep better using Armory.
There are other options certainly, but I sleep better using Armory.
Why such a difference in block count? Because my Core client (and Armory...) is outdated? The getinfo command returns the block we are in, so everything seems to be working (I think).
Sometimes that happens if you start Armory when Core is fully started or synced yet.Never happened to me. And Armory manages Core automatically here.
What top block is Armory displaying on the bottom right corner? Also, update to 0.94.1 already.
It's in the screenshot above, there was a difference of about 15000 blocks or so. You're right, I've been slacking off on updates
Updated Core and Armory, issues still persisted. Rebuilt databases, it just finished syncing now and everything seems back to normal. Thanks!
What top block is Armory displaying on the bottom right corner? Also, update to 0.94.1 already.
Why such a difference in block count? Because my Core client (and Armory...) is outdated? The getinfo command returns the block we are in, so everything seems to be working (I think).
Sometimes that happens if you start Armory when Core is fully started or synced yet.
Haven't been having much time in my hands so Armory and Core have been running "unattended" for... Two months or more? Not even sure. Noticed this today:
Why such a difference in block count? Because my Core client (and Armory...) is outdated? The getinfo command returns the block we are in, so everything seems to be working (I think).
Log file
Why such a difference in block count? Because my Core client (and Armory...) is outdated? The getinfo command returns the block we are in, so everything seems to be working (I think).
Log file
Code:
ArmoryUtils.pyc:1196 - ************************************************************
ArmoryUtils.pyc:1197 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe --satoshi-datadir=D:\Bitcoin --datadir=D:\Armory
ArmoryUtils.pyc:1198 - ************************************************************
ArmoryUtils.pyc:1199 - Loading Armory Engine:
ArmoryUtils.pyc:1200 - Armory Version : 0.94
ArmoryUtils.pyc:1201 - Armory Build: : b0033fb356
ArmoryUtils.pyc:1202 - PyBtcWallet Version : 1.35
ArmoryUtils.pyc:1203 - Detected Operating system: Windows
ArmoryUtils.pyc:1204 - OS Variant : 8-6.2.9200--Multiprocessor Free
ArmoryUtils.pyc:1205 - User home-directory : C:\Users\********\AppData\Roaming
ArmoryUtils.pyc:1206 - Satoshi BTC directory : D:\Bitcoin
ArmoryUtils.pyc:1207 - Armory home dir : D:\Armory
ArmoryUtils.pyc:1208 - Detected System Specs :
ArmoryUtils.pyc:1209 - Total Available RAM : 2.00 GB
ArmoryUtils.pyc:1210 - CPU ID string : Intel64 Family 6 Model 15 Stepping 11, GenuineIntel
ArmoryUtils.pyc:1211 - Number of CPU cores : 2 cores
ArmoryUtils.pyc:1212 - System is 64-bit : True
ArmoryUtils.pyc:1213 - Preferred Encoding : cp1252
ArmoryUtils.pyc:1214 - Machine Arch : amd64
ArmoryUtils.pyc:1215 - Available HDD (ARM) : 19 GB
ArmoryUtils.pyc:1216 - Available HDD (BTC) : 19 GB
ArmoryUtils.pyc:1217 -
ArmoryUtils.pyc:1218 - Network Name: Main Network
ArmoryUtils.pyc:1219 - Satoshi Port: 8333
ArmoryUtils.pyc:1220 - Do wlt check: True
ArmoryUtils.pyc:1221 - Named options/arguments to armoryengine.py:
ArmoryUtils.pyc:1223 - nettimeout : 2
ArmoryUtils.pyc:1223 - rescan : False
ArmoryUtils.pyc:1223 - ignoreAllZC : False
ArmoryUtils.pyc:1223 - rescanBalance : False
ArmoryUtils.pyc:1223 - disableModules : False
ArmoryUtils.pyc:1223 - port : None
ArmoryUtils.pyc:1223 - interport : 8223
ArmoryUtils.pyc:1223 - skipStatsReport : False
ArmoryUtils.pyc:1223 - forceWalletCheck: False
ArmoryUtils.pyc:1223 - rebuild : False
ArmoryUtils.pyc:1223 - datadir : D:\Armory
ArmoryUtils.pyc:1223 - clearMempool : False
ArmoryUtils.pyc:1223 - offline : False
ArmoryUtils.pyc:1223 - coverageOutputDir: None
ArmoryUtils.pyc:1223 - armoryDBDir : DEFAULT
ArmoryUtils.pyc:1223 - satoshiPort : DEFAULT
ArmoryUtils.pyc:1223 - useTorSettings : False
ArmoryUtils.pyc:1223 - netlog : False
ArmoryUtils.pyc:1223 - keypool : 100
ArmoryUtils.pyc:1223 - coverageInclude : None
ArmoryUtils.pyc:1223 - forceOnline : False
ArmoryUtils.pyc:1223 - skipAnnounceCheck: False
ArmoryUtils.pyc:1223 - redownload : False
ArmoryUtils.pyc:1223 - multisigFile : DEFAULT
ArmoryUtils.pyc:1223 - disableTorrent : False
ArmoryUtils.pyc:1223 - testAnnounceCode: False
ArmoryUtils.pyc:1223 - mtdebug : False
ArmoryUtils.pyc:1223 - logDisable : False
ArmoryUtils.pyc:1223 - settingsPath : D:\Armory\ArmorySettings.txt
ArmoryUtils.pyc:1223 - verbosity : None
ArmoryUtils.pyc:1223 - doDebug : False
ArmoryUtils.pyc:1223 - enableDetSign : True
ArmoryUtils.pyc:1223 - testnet : False
ArmoryUtils.pyc:1223 - rpcport : DEFAULT
ArmoryUtils.pyc:1223 - satoshiHome : D:\Bitcoin
ArmoryUtils.pyc:1223 - satoshiRpcport : DEFAULT
ArmoryUtils.pyc:1223 - logFile : D:\Armory\ArmoryQt.exe.log.txt
ArmoryUtils.pyc:1223 - disableConfPermis: False
ArmoryUtils.pyc:1223 - enableSupernode : False
ArmoryUtils.pyc:1224 - Other arguments:
ArmoryUtils.pyc:1227 - ************************************************************
ArmoryUtils.pyc:1627 - C++ block utilities loaded successfully
BDM.pyc:420 - Using the asynchronous/multi-threaded BlockDataManager.
BDM.pyc:421 - Blockchain operations will happen in the background.
BDM.pyc:422 - Devs: check TheBDM.getState() before asking for data.
BDM.pyc:423 - Registering addresses during rescans will queue them for
BDM.pyc:424 - inclusion after the current scan is completed.
ArmoryUtils.pyc:3538 - Using settings file: D:\Armory\ArmorySettings.txt
ArmoryQt.py:2752 - loadWalletsAndSettings
ArmoryQt.py:2806 - Loading wallets...
ArmoryQt.py:2865 - Number of wallets read in: 1
ArmoryQt.py:2879 - Loading Multisig Lockboxes
ArmoryQt.py:2311 - Setting up networking...
ArmoryQt.py:2340 - Internet status: 0
ArmoryQt.py:2455 - startBitcoindIfNecessary
ArmoryQt.py:2504 - setSatoshiPaths
SDM.pyc:321 - Found bitcoind in the following places:
SDM.pyc:323 - C:\Program Files\Bitcoin\daemon\bitcoind.exe
SDM.pyc:325 - Using: C:\Program Files\Bitcoin\daemon\bitcoind.exe
SDM.pyc:496 - Reading bitcoin.conf file
SDM.pyc:515 - Setting permissions on bitcoin.conf
SDM.pyc:524 - Setting permissions on bitcoin.conf
ArmoryUtils.pyc:596 - Executing popen: [u'icacls', u'D:\\Bitcoin\\bitcoin.conf', u'/inheritance:r', u'/grant:r', u'********:F']
SDM.pyc:530 - icacls returned:
SDM.pyc:597 - Called startBitcoind
ArmoryUtils.pyc:596 - Executing popen: ['C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=D:\\Bitcoin']
SDM.pyc:669 - PID of bitcoind: 3352
SDM.pyc:670 - PID of armory: 6136
ArmoryUtils.pyc:596 - Executing popen: ['.\\guardian.exe', '6136', '3352']
SDM.pyc:848 - Creating proxy in SDM: host=127.0.0.1, port=8332
ArmoryQt.py:1527 - setupUriRegistration
ArmoryQt.py:1595 - Armory already registered for current user. Done!
ArmoryQt.py:664 - Usermode: Expert
ArmoryQt.py:1823 - Changing usermode:
ArmoryQt.py:1824 - From: Expert
ArmoryQt.py:1832 - To: Expert
ArmoryQt.py:5855 - Dashboard switched to auto-InitSync
ArmoryQt.py:2541 - loadBlockchainIfNecessary
ArmoryQt.py:2562 - Setting netmode: 1
ArmoryQt.py:5978 - Dashboard switched to "Scanning" mode
Networking.pyc:65 - Connection initiated. Start handshake
ArmoryQt.py:5978 - Dashboard switched to "Scanning" mode
Networking.pyc:156 - Received version message from peer:
Networking.pyc:157 - Version: 70012
Networking.pyc:158 - SubVersion: /Satoshi:0.12.0/
Networking.pyc:159 - TimeStamp: 1470351923
Networking.pyc:160 - StartHeight: 423711
Networking.pyc:350 - Handshake finished, connection open!
ArmoryQt.py:3164 - Current block number: 408718
ArmoryUtils.pyc:1197 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe --satoshi-datadir=D:\Bitcoin --datadir=D:\Armory
ArmoryUtils.pyc:1198 - ************************************************************
ArmoryUtils.pyc:1199 - Loading Armory Engine:
ArmoryUtils.pyc:1200 - Armory Version : 0.94
ArmoryUtils.pyc:1201 - Armory Build: : b0033fb356
ArmoryUtils.pyc:1202 - PyBtcWallet Version : 1.35
ArmoryUtils.pyc:1203 - Detected Operating system: Windows
ArmoryUtils.pyc:1204 - OS Variant : 8-6.2.9200--Multiprocessor Free
ArmoryUtils.pyc:1205 - User home-directory : C:\Users\********\AppData\Roaming
ArmoryUtils.pyc:1206 - Satoshi BTC directory : D:\Bitcoin
ArmoryUtils.pyc:1207 - Armory home dir : D:\Armory
ArmoryUtils.pyc:1208 - Detected System Specs :
ArmoryUtils.pyc:1209 - Total Available RAM : 2.00 GB
ArmoryUtils.pyc:1210 - CPU ID string : Intel64 Family 6 Model 15 Stepping 11, GenuineIntel
ArmoryUtils.pyc:1211 - Number of CPU cores : 2 cores
ArmoryUtils.pyc:1212 - System is 64-bit : True
ArmoryUtils.pyc:1213 - Preferred Encoding : cp1252
ArmoryUtils.pyc:1214 - Machine Arch : amd64
ArmoryUtils.pyc:1215 - Available HDD (ARM) : 19 GB
ArmoryUtils.pyc:1216 - Available HDD (BTC) : 19 GB
ArmoryUtils.pyc:1217 -
ArmoryUtils.pyc:1218 - Network Name: Main Network
ArmoryUtils.pyc:1219 - Satoshi Port: 8333
ArmoryUtils.pyc:1220 - Do wlt check: True
ArmoryUtils.pyc:1221 - Named options/arguments to armoryengine.py:
ArmoryUtils.pyc:1223 - nettimeout : 2
ArmoryUtils.pyc:1223 - rescan : False
ArmoryUtils.pyc:1223 - ignoreAllZC : False
ArmoryUtils.pyc:1223 - rescanBalance : False
ArmoryUtils.pyc:1223 - disableModules : False
ArmoryUtils.pyc:1223 - port : None
ArmoryUtils.pyc:1223 - interport : 8223
ArmoryUtils.pyc:1223 - skipStatsReport : False
ArmoryUtils.pyc:1223 - forceWalletCheck: False
ArmoryUtils.pyc:1223 - rebuild : False
ArmoryUtils.pyc:1223 - datadir : D:\Armory
ArmoryUtils.pyc:1223 - clearMempool : False
ArmoryUtils.pyc:1223 - offline : False
ArmoryUtils.pyc:1223 - coverageOutputDir: None
ArmoryUtils.pyc:1223 - armoryDBDir : DEFAULT
ArmoryUtils.pyc:1223 - satoshiPort : DEFAULT
ArmoryUtils.pyc:1223 - useTorSettings : False
ArmoryUtils.pyc:1223 - netlog : False
ArmoryUtils.pyc:1223 - keypool : 100
ArmoryUtils.pyc:1223 - coverageInclude : None
ArmoryUtils.pyc:1223 - forceOnline : False
ArmoryUtils.pyc:1223 - skipAnnounceCheck: False
ArmoryUtils.pyc:1223 - redownload : False
ArmoryUtils.pyc:1223 - multisigFile : DEFAULT
ArmoryUtils.pyc:1223 - disableTorrent : False
ArmoryUtils.pyc:1223 - testAnnounceCode: False
ArmoryUtils.pyc:1223 - mtdebug : False
ArmoryUtils.pyc:1223 - logDisable : False
ArmoryUtils.pyc:1223 - settingsPath : D:\Armory\ArmorySettings.txt
ArmoryUtils.pyc:1223 - verbosity : None
ArmoryUtils.pyc:1223 - doDebug : False
ArmoryUtils.pyc:1223 - enableDetSign : True
ArmoryUtils.pyc:1223 - testnet : False
ArmoryUtils.pyc:1223 - rpcport : DEFAULT
ArmoryUtils.pyc:1223 - satoshiHome : D:\Bitcoin
ArmoryUtils.pyc:1223 - satoshiRpcport : DEFAULT
ArmoryUtils.pyc:1223 - logFile : D:\Armory\ArmoryQt.exe.log.txt
ArmoryUtils.pyc:1223 - disableConfPermis: False
ArmoryUtils.pyc:1223 - enableSupernode : False
ArmoryUtils.pyc:1224 - Other arguments:
ArmoryUtils.pyc:1227 - ************************************************************
ArmoryUtils.pyc:1627 - C++ block utilities loaded successfully
BDM.pyc:420 - Using the asynchronous/multi-threaded BlockDataManager.
BDM.pyc:421 - Blockchain operations will happen in the background.
BDM.pyc:422 - Devs: check TheBDM.getState() before asking for data.
BDM.pyc:423 - Registering addresses during rescans will queue them for
BDM.pyc:424 - inclusion after the current scan is completed.
ArmoryUtils.pyc:3538 - Using settings file: D:\Armory\ArmorySettings.txt
ArmoryQt.py:2752 - loadWalletsAndSettings
ArmoryQt.py:2806 - Loading wallets...
ArmoryQt.py:2865 - Number of wallets read in: 1
ArmoryQt.py:2879 - Loading Multisig Lockboxes
ArmoryQt.py:2311 - Setting up networking...
ArmoryQt.py:2340 - Internet status: 0
ArmoryQt.py:2455 - startBitcoindIfNecessary
ArmoryQt.py:2504 - setSatoshiPaths
SDM.pyc:321 - Found bitcoind in the following places:
SDM.pyc:323 - C:\Program Files\Bitcoin\daemon\bitcoind.exe
SDM.pyc:325 - Using: C:\Program Files\Bitcoin\daemon\bitcoind.exe
SDM.pyc:496 - Reading bitcoin.conf file
SDM.pyc:515 - Setting permissions on bitcoin.conf
SDM.pyc:524 - Setting permissions on bitcoin.conf
ArmoryUtils.pyc:596 - Executing popen: [u'icacls', u'D:\\Bitcoin\\bitcoin.conf', u'/inheritance:r', u'/grant:r', u'********:F']
SDM.pyc:530 - icacls returned:
SDM.pyc:597 - Called startBitcoind
ArmoryUtils.pyc:596 - Executing popen: ['C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=D:\\Bitcoin']
SDM.pyc:669 - PID of bitcoind: 3352
SDM.pyc:670 - PID of armory: 6136
ArmoryUtils.pyc:596 - Executing popen: ['.\\guardian.exe', '6136', '3352']
SDM.pyc:848 - Creating proxy in SDM: host=127.0.0.1, port=8332
ArmoryQt.py:1527 - setupUriRegistration
ArmoryQt.py:1595 - Armory already registered for current user. Done!
ArmoryQt.py:664 - Usermode: Expert
ArmoryQt.py:1823 - Changing usermode:
ArmoryQt.py:1824 - From: Expert
ArmoryQt.py:1832 - To: Expert
ArmoryQt.py:5855 - Dashboard switched to auto-InitSync
ArmoryQt.py:2541 - loadBlockchainIfNecessary
ArmoryQt.py:2562 - Setting netmode: 1
ArmoryQt.py:5978 - Dashboard switched to "Scanning" mode
Networking.pyc:65 - Connection initiated. Start handshake
ArmoryQt.py:5978 - Dashboard switched to "Scanning" mode
Networking.pyc:156 - Received version message from peer:
Networking.pyc:157 - Version: 70012
Networking.pyc:158 - SubVersion: /Satoshi:0.12.0/
Networking.pyc:159 - TimeStamp: 1470351923
Networking.pyc:160 - StartHeight: 423711
Networking.pyc:350 - Handshake finished, connection open!
ArmoryQt.py:3164 - Current block number: 408718
Isn't there some way that you could ultimately be posting your releases here?
https://www.bitcoinarmory.com/download/ Or is that where your new releases will soon go also, based on the new arrangement? Sorry if I should already know this, but just trying to clear it up / better understand.
Finally, back to my original question, when I asked "will the next release support offline transactions?" I was thinking of 0.94 when I said "the next release... so, I have seen it said in this thread that somehow offline transactions aren't supported in 0.94, is this correct or not? I am hoping they will be. (And if not, will they be in the next release?)
https://www.bitcoinarmory.com/download/ Or is that where your new releases will soon go also, based on the new arrangement? Sorry if I should already know this, but just trying to clear it up / better understand.
Finally, back to my original question, when I asked "will the next release support offline transactions?" I was thinking of 0.94 when I said "the next release... so, I have seen it said in this thread that somehow offline transactions aren't supported in 0.94, is this correct or not? I am hoping they will be. (And if not, will they be in the next release?)
Offline transactions have always been supported in Armory, 0.94 is no different.
I don't have access to bitcoinarmory.com, that domain belongs to ATI and is under their control. What goes in there is what they choose to.
Thank you!
Isn't there some way that you could ultimately be posting your releases here?
https://www.bitcoinarmory.com/download/ Or is that where your new releases will soon go also, based on the new arrangement? Sorry if I should already know this, but just trying to clear it up / better understand.
Finally, back to my original question, when I asked "will the next release support offline transactions?" I was thinking of 0.94 when I said "the next release... so, I have seen it said in this thread that somehow offline transactions aren't supported in 0.94, is this correct or not? I am hoping they will be. (And if not, will they be in the next release?)
https://www.bitcoinarmory.com/download/ Or is that where your new releases will soon go also, based on the new arrangement? Sorry if I should already know this, but just trying to clear it up / better understand.
Finally, back to my original question, when I asked "will the next release support offline transactions?" I was thinking of 0.94 when I said "the next release... so, I have seen it said in this thread that somehow offline transactions aren't supported in 0.94, is this correct or not? I am hoping they will be. (And if not, will they be in the next release?)
Offline transactions have always been supported in Armory, 0.94 is no different.
I don't have access to bitcoinarmory.com, that domain belongs to ATI and is under their control. What goes in there is what they choose to.
What do you mean by offline mode? Why can't .94 be used offline without a mode like the old ones? Just do it offline.
0.94 can be used offline like the previous versions, I'm not sure what you are referring to.
This part
There won't be offline builds for this release, as nothing was modified on the offline signing part. You can keep on using 0.92-93 to sign transactions created with 0.94.
Goatpig, can you confirm this? As per my question from another thread at
https://bitcointalksearch.org/topic/m.15121804
"will the next release support offline transactions? (Right now I think you have to offline sign with 0.92 and broadcast with 0.93.3, or am I mistaken? Can any version handle offline transactions?)
see for example: http://betteroffbitcoin.com/a-protocol-for-offline-bitcoin-over-radio-transactions/ (something which I think is very cool)"
Also, if I understand correctly, the releases should also now be found under https://github.com/goatpig/BitcoinArmory/releases
But, what I am also wondering is this:
Isn't there some way that you could ultimately be posting your releases here?
https://www.bitcoinarmory.com/download/ Or is that where your new releases will soon go also, based on the new arrangement? Sorry if I should already know this, but just trying to clear it up / better understand.
Finally, back to my original question, when I asked "will the next release support offline transactions?" I was thinking of 0.94 when I said "the next release... so, I have seen it said in this thread that somehow offline transactions aren't supported in 0.94, is this correct or not? I am hoping they will be. (And if not, will they be in the next release?)
Thanks to goatpig (and all others involved) for continuing this work on Armory!
That's a tremendous contribution to the community - and I hope that a sustainable way can be found to support you in return as well.
That's a tremendous contribution to the community - and I hope that a sustainable way can be found to support you in return as well.
thx
I need to delete the 0.93 db cause i have only 40MB left, but i couldnt find the dir/file in user/.armory/databases
where to look for the 0.93 db?
where to look for the 0.93 db?
Which OS are you using?
Ubuntu, i just deleted in the databases-dir the blocks directory as i discovered that under .bitcoin is also a blocks-dir with 69GB.
edit: next question: where to get a save version of 0.94.1 ?
I need to delete the 0.93 db cause i have only 40MB left, but i couldnt find the dir/file in user/.armory/databases
where to look for the 0.93 db?
where to look for the 0.93 db?
Which OS are you using?
Is there any reason at this point in time to keep the 60GB database from 0.93.3? I'd prefer to delete it and reclaim the HD space.
Not really. You can delete it if you want, the only point of keeping it is just in case something fails horribly, which I don't think will happen.I need to delete the 0.93 db cause i have only 40MB left, but i couldnt find the dir/file in user/.armory/databases
where to look for the 0.93 db?
I haven't fully thought it out, but I'd guess that segwit will require a new offline build, no?
I expect it will.
What do you mean by offline mode? Why can't .94 be used offline without a mode like the old ones? Just do it offline.
0.94 can be used offline like the previous versions, I'm not sure what you are referring to.
This part
There won't be offline builds for this release, as nothing was modified on the offline signing part. You can keep on using 0.92-93 to sign transactions created with 0.94.
I haven't fully thought it out, but I'd guess that segwit will require a new offline build, no?
What do you mean by offline mode? Why can't .94 be used offline without a mode like the old ones? Just do it offline.
0.94 can be used offline like the previous versions, I'm not sure what you are referring to.
This part
There won't be offline builds for this release, as nothing was modified on the offline signing part. You can keep on using 0.92-93 to sign transactions created with 0.94.
What do you mean by offline mode? Why can't .94 be used offline without a mode like the old ones? Just do it offline.
0.94 can be used offline like the previous versions, I'm not sure what you are referring to.
Jump to: