well ive added --satoshi-port=8331 to the shortcut
still shows offline
ive got these lines in my bitcoin.conf in the bitcoin folder still
proxy=127.0.0.1:9051
listen=1
port=8331
with those lines added bitcoin core wont even connect i have to remove those lines in order to get regular tor proxy connectivity with bitcoin cores network settings, and after retesting listen=1 by itself , well bitcoin core connects outside tor as does armory, no wonder it was working for both ,lols , i dont recommend it , any ideas
Topic: Armory - Discussion Thread - page 56. (Read 521749 times)
bitcoin.conf in Armory's datadir? That won't help you.
For Armory, create a shortcut, go the to shortcut properties and at the end of the 'target' input box add --satoshi-port=8331, then start from that shortcut.
Also block all traffic to that port in firewall settings.
I'm pretty sure I said Whonix cause it requires installation, which means persistence, so you can change the settings to fit your use case.
For Armory, create a shortcut, go the to shortcut properties and at the end of the 'target' input box add --satoshi-port=8331, then start from that shortcut.
Also block all traffic to that port in firewall settings.
Quote
because i use obfuscated bridges aka obfs3 protocol , which regular tor doesnt provide which whonix gateway uses and so your isp can see you using tor , not a good thing depending on where you live, what we need is simple support to have armory use bitcoin cores connection
I'm pretty sure I said Whonix cause it requires installation, which means persistence, so you can change the settings to fit your use case.
ok now im quite confused this is what i got in both of my bitcoin.conf folders , yes oddly enough i have 2 bitcoin.conf files in seperate folders is this normal ?, first one is the bitcoin folder in appdata
rpcuser=generated_by_armory
rpcpassword=8-09f8g-09sdf8g0-9df0-sg9stgergregfds
proxy=127.0.0.1:9051
listen=1
port=8331
and this is what i got in my bitcoin.conf file in the armory folder in the appdata folder
rpcuser=generated_by_armory
rpcpassword=4325342645364536756ujfghnfgdgrwgxfjghfkhfj
proxy=127.0.0.1:9051
listen=1
port=8331
armory shows offline and bitcoin core wont sync now , but if i set it as so in the bitcoin folders bitcoin.conf
rpcuser=generated_by_armory
rpcpassword=CKADQejZwtxnQDw8NGRKT6CnkDexAVABX7NoGVc1GmWD
listen=1
then bitcoin core works again and armory goes online , wtf , what do i do , ive even tested this by running armory first and then having bitcoin core connect, well suffice to say , armory shows offline and my
firewall doesnt register any connections from armory until bitcoin core connects , then armory shows as connected and i see connections from armory.exe in my firewall , then i exit out bitcoin core and armory shows disconnected , so there you have it not sure what to make of this thou after hearing listen=1 by its own is a bad idea apparently, btw the suggestion of using whonix gateway isnt a good idea
because i use obfuscated bridges aka obfs3 protocol , which regular tor doesnt provide which whonix gateway uses and so your isp can see you using tor , not a good thing depending on where you live, what we need is simple support to have armory use bitcoin cores connection
for all the connections armory has to make , be it blockchain , updates , and so on , youd think with armorys aim for security this should be default, again please help me out to be able to route all of armorys connections through bitcoin core , thanks
heres the armory log:
rpcuser=generated_by_armory
rpcpassword=8-09f8g-09sdf8g0-9df0-sg9stgergregfds
proxy=127.0.0.1:9051
listen=1
port=8331
and this is what i got in my bitcoin.conf file in the armory folder in the appdata folder
rpcuser=generated_by_armory
rpcpassword=4325342645364536756ujfghnfgdgrwgxfjghfkhfj
proxy=127.0.0.1:9051
listen=1
port=8331
armory shows offline and bitcoin core wont sync now , but if i set it as so in the bitcoin folders bitcoin.conf
rpcuser=generated_by_armory
rpcpassword=CKADQejZwtxnQDw8NGRKT6CnkDexAVABX7NoGVc1GmWD
listen=1
then bitcoin core works again and armory goes online , wtf , what do i do , ive even tested this by running armory first and then having bitcoin core connect, well suffice to say , armory shows offline and my
firewall doesnt register any connections from armory until bitcoin core connects , then armory shows as connected and i see connections from armory.exe in my firewall , then i exit out bitcoin core and armory shows disconnected , so there you have it not sure what to make of this thou after hearing listen=1 by its own is a bad idea apparently, btw the suggestion of using whonix gateway isnt a good idea
because i use obfuscated bridges aka obfs3 protocol , which regular tor doesnt provide which whonix gateway uses and so your isp can see you using tor , not a good thing depending on where you live, what we need is simple support to have armory use bitcoin cores connection
for all the connections armory has to make , be it blockchain , updates , and so on , youd think with armorys aim for security this should be default, again please help me out to be able to route all of armorys connections through bitcoin core , thanks
heres the armory log:
Code:
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:919 - C++ block utilities loaded successfully
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1009 -
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1010 -
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1011 -
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1012 - ************************************************************
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1013 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1014 - ************************************************************
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1015 - Loading Armory Engine:
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1016 - Armory Version : 0.91
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1017 - PyBtcWallet Version : 1.35
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1018 - Detected Operating system: Windows
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1019 - OS Variant : 7-6.1.7601-SP1-Multiprocessor Free
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1020 - User home-directory : C:\Users\bob\AppData\Roaming
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1021 - Satoshi BTC directory : C:\Users\bob\AppData\Roaming\Bitcoin\
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1022 - Armory home dir : C:\Users\bob\AppData\Roaming\Armory\
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1023 - Detected System Specs :
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1024 - Total Available RAM : 15.99 GB
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1025 - CPU ID string : Intel64 Family 5 Model 24 Stepping 2, GenuineIntel
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1026 - Number of CPU cores : 6 cores
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1027 - System is 64-bit : False
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1028 - Preferred Encoding : cp1252
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1029 -
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1030 - Network Name: Main Network
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1031 - Satoshi Port: 8333
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1032 - Named options/arguments to armoryengine.py:
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1034 - maxOpenFiles : 0
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1034 - nettimeout : 2
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1034 - rescan : False
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1034 - leveldbDir : DEFAULT
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1034 - ignoreAllZC : False
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1034 - port : None
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1034 - interport : 8223
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1034 - coverageOutputDir: None
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1034 - rebuild : False
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1034 - datadir : DEFAULT
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1034 - offline : False
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1034 - noWalletCheck : False
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1034 - satoshiPort : DEFAULT
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1034 - netlog : False
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1034 - keypool : 100
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1034 - coverageInclude : None
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1034 - forceOnline : False
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1034 - skipAnnounceCheck: False
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1034 - redownload : False
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1034 - disableTorrent : False
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1034 - testAnnounceCode: False
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1034 - mtdebug : False
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1034 - skipVerCheck : False
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1034 - settingsPath : C:\Users\bob\AppData\Roaming\Armory\ArmorySettings.txt
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1034 - verbosity : None
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1034 - doDebug : False
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1034 - testnet : False
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1034 - rpcport : DEFAULT
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1034 - satoshiHome : DEFAULT
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1034 - satoshiRpcport : DEFAULT
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1034 - logDisable : False
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1034 - logFile : C:\Users\bob\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1035 - Other arguments:
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1038 - ************************************************************
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:1386 - C++ block utilities loaded successfully
2014-04-16 12:46 (INFO) -- BDM.pyc:1420 - Using the asynchronous/multi-threaded BlockDataManager.
2014-04-16 12:46 (INFO) -- BDM.pyc:1421 - Blockchain operations will happen in the background.
2014-04-16 12:46 (INFO) -- BDM.pyc:1422 - Devs: check TheBDM.getBDMState() before asking for data.
2014-04-16 12:46 (INFO) -- BDM.pyc:1423 - Registering addresses during rescans will queue them for
2014-04-16 12:46 (INFO) -- BDM.pyc:1424 - inclusion after the current scan is completed.
2014-04-16 12:46 (INFO) -- ArmoryUtils.pyc:3007 - Using settings file: C:\Users\bob\AppData\Roaming\Armory\ArmorySettings.txt
2014-04-16 12:46 (INFO) -- announcefetch.pyc:83 - Reading files in fetcher directory:
2014-04-16 12:46 (INFO) -- announcefetch.pyc:92 - announce : 52b6e5624ed25b90d2d2a783ab87635b048aa8b7cb14b21a958ad052faee8691
2014-04-16 12:46 (INFO) -- announcefetch.pyc:92 - bootstrap : 0c68367a6126ed922c90fd06f6b3dc2217248b595adf5c6a1832cdeb4a3ae0b7
2014-04-16 12:46 (INFO) -- announcefetch.pyc:92 - changelog : 00e39ea889395a7148dea87274ee60e484c97c67905b65c67782290dad945639
2014-04-16 12:46 (INFO) -- announcefetch.pyc:92 - downloads : b553c42962f36961f7ac56b85bdd8d6656a16a95c2ce0bc9d60670165825f786
2014-04-16 12:46 (INFO) -- announcefetch.pyc:92 - notify : 011ee87ce2b50a18a06ca4a05f95c5a8f7dc9d55cced2a4654c609eea2795f4c
2014-04-16 12:46 (INFO) -- announcefetch.pyc:249 - Fetching: https://bitcoinarmory.com/announce.txt?osvar=7&os=win&ver=0.91&id=e7d396f6
2014-04-16 12:46 (INFO) -- ArmoryQt.py:2244 - loadWalletsAndSettings
2014-04-16 12:46 (INFO) -- ArmoryQt.py:2302 - Loading wallets...
2014-04-16 12:46 (ERROR) -- announcefetch.pyc:261 - Specified URL was inaccessible
2014-04-16 12:46 (ERROR) -- announcefetch.pyc:262 - Tried: https://bitcoinarmory.com/announce.txt?osvar=7&os=win&ver=0.91&id=e7d396f6
2014-04-16 12:46 (INFO) -- announcefetch.pyc:249 - Fetching: https://s3.amazonaws.com/bitcoinarmory-media/announce.txt?ver=0.91
2014-04-16 12:46 (ERROR) -- announcefetch.pyc:261 - Specified URL was inaccessible
2014-04-16 12:46 (ERROR) -- announcefetch.pyc:262 - Tried: https://s3.amazonaws.com/bitcoinarmory-media/announce.txt?ver=0.91
2014-04-16 12:46 (WARNING) -- announcefetch.pyc:275 - Error fetching announce digest
2014-04-16 12:46 (INFO) -- ArmoryQt.py:2351 - Number of wallets read in: 1
2014-04-16 12:46 (INFO) -- ArmoryQt.py:2356 - Wallet (xcvbcvb): "dgfhdfgjhkgjhjhgk" (Encrypted)
2014-04-16 12:46 (INFO) -- ArmoryQt.py:1786 - Setting up networking...
2014-04-16 12:46 (ERROR) -- ArmoryQt.py:1829 - Error checking for internet connection
Traceback (most recent call last):
File "ArmoryQt.py", line 1827, in setupNetworking
File "urllib2.pyc", line 127, in urlopen
File "urllib2.pyc", line 404, in open
File "urllib2.pyc", line 422, in _open
File "urllib2.pyc", line 382, in _call_chain
File "urllib2.pyc", line 1214, in http_open
File "urllib2.pyc", line 1184, in do_open
URLError:
2014-04-16 12:46 (ERROR) -- ArmoryQt.py:1830 - Run --skip-online-check if you think this is an error
2014-04-16 12:46 (INFO) -- ArmoryQt.py:1838 - Internet connection is Available: False
2014-04-16 12:46 (INFO) -- ArmoryQt.py:1839 - Bitcoin-Qt/bitcoind is Available: 0
2014-04-16 12:46 (INFO) -- ArmoryQt.py:1840 - The first blk*.dat was Available: True
2014-04-16 12:46 (INFO) -- ArmoryQt.py:1841 - Online mode currently possible: False
2014-04-16 12:46 (INFO) -- ArmoryQt.py:2028 - loadBlockchainIfNecessary
2014-04-16 12:46 (INFO) -- ArmoryQt.py:2074 - Setting netmode: 0
2014-04-16 12:46 (INFO) -- BDM.pyc:431 - Setting online mode: False (wait=False)
2014-04-16 12:46 (INFO) -- ArmoryQt.py:1099 - setupUriRegistration
2014-04-16 12:46 (INFO) -- ArmoryQt.py:1167 - Armory already registered for current user. Done!
2014-04-16 12:46 (INFO) -- ArmoryQt.py:585 - Usermode: Expert
2014-04-16 12:46 (INFO) -- ArmoryQt.py:1366 - Changing usermode:
2014-04-16 12:46 (INFO) -- ArmoryQt.py:1367 - From: Expert
2014-04-16 12:46 (INFO) -- ArmoryQt.py:1375 - To: Expert
2014-04-16 12:46 (INFO) -- ArmoryQt.py:4914 - Switching Armory state text to Mgmt:User, State:OfflineNoSatoshiNoInternet
2014-04-16 12:46 (INFO) -- ArmoryQt.py:4856 - Switching Armory functional mode to "Offline"
2014-04-16 12:46 (INFO) -- ArmoryQt.py:698 - MinimizeOnOpen is True
2014-04-16 13:07 (INFO) -- ArmoryQt.py:6150 - BDM is safe for clean shutdown
2014-04-16 13:07 (INFO) -- BDM.pyc:1346 - Shutdown Requested
2014-04-16 13:07 (ERROR) -- BDM.pyc:1141 - Resetting BDM and all wallets
2014-04-16 13:07 (INFO) -- BDM.pyc:1393 - BDM is shutdown.
2014-04-16 13:07 (INFO) -- SDM.pyc:636 - Called stopBitcoind
2014-04-16 13:07 (INFO) -- SDM.pyc:638 - ...but bitcoind is not running, to be able to stop
2014-04-16 13:07 (INFO) -- ArmoryQt.py:6162 - Attempting to close the main window!
2014-04-16 13:07 (INFO) -- ArmoryQt.py:6435 - Resetting BlockDataMgr, freeing memory
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:919 - C++ block utilities loaded successfully
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1009 -
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1010 -
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1011 -
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1012 - ************************************************************
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1013 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1014 - ************************************************************
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1015 - Loading Armory Engine:
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1016 - Armory Version : 0.91
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1017 - PyBtcWallet Version : 1.35
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1018 - Detected Operating system: Windows
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1019 - OS Variant : 7-6.1.7601-SP1-Multiprocessor Free
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1020 - User home-directory : C:\Users\bob\AppData\Roaming
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1021 - Satoshi BTC directory : C:\Users\bob\AppData\Roaming\Bitcoin\
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1022 - Armory home dir : C:\Users\bob\AppData\Roaming\Armory\
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1023 - Detected System Specs :
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1024 - Total Available RAM : 15.99 GB
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1025 - CPU ID string : Intel64 Family 5 Model 24 Stepping 2, GenuineIntel
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1026 - Number of CPU cores : 6 cores
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1027 - System is 64-bit : False
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1028 - Preferred Encoding : cp1252
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1029 -
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1030 - Network Name: Main Network
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1031 - Satoshi Port: 8333
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1032 - Named options/arguments to armoryengine.py:
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1034 - maxOpenFiles : 0
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1034 - nettimeout : 2
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1034 - rescan : False
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1034 - leveldbDir : DEFAULT
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1034 - ignoreAllZC : False
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1034 - port : None
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1034 - interport : 8223
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1034 - coverageOutputDir: None
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1034 - rebuild : False
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1034 - datadir : DEFAULT
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1034 - offline : False
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1034 - noWalletCheck : False
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1034 - satoshiPort : DEFAULT
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1034 - netlog : False
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1034 - keypool : 100
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1034 - coverageInclude : None
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1034 - forceOnline : False
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1034 - skipAnnounceCheck: False
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1034 - redownload : False
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1034 - disableTorrent : False
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1034 - testAnnounceCode: False
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1034 - mtdebug : False
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1034 - skipVerCheck : False
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1034 - settingsPath : C:\Users\bob\AppData\Roaming\Armory\ArmorySettings.txt
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1034 - verbosity : None
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1034 - doDebug : False
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1034 - testnet : False
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1034 - rpcport : DEFAULT
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1034 - satoshiHome : DEFAULT
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1034 - satoshiRpcport : DEFAULT
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1034 - logDisable : False
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1034 - logFile : C:\Users\bob\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1035 - Other arguments:
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1038 - ************************************************************
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:1386 - C++ block utilities loaded successfully
2014-04-16 13:07 (INFO) -- BDM.pyc:1420 - Using the asynchronous/multi-threaded BlockDataManager.
2014-04-16 13:07 (INFO) -- BDM.pyc:1421 - Blockchain operations will happen in the background.
2014-04-16 13:07 (INFO) -- BDM.pyc:1422 - Devs: check TheBDM.getBDMState() before asking for data.
2014-04-16 13:07 (INFO) -- BDM.pyc:1423 - Registering addresses during rescans will queue them for
2014-04-16 13:07 (INFO) -- BDM.pyc:1424 - inclusion after the current scan is completed.
2014-04-16 13:07 (INFO) -- ArmoryUtils.pyc:3007 - Using settings file: C:\Users\bob\AppData\Roaming\Armory\ArmorySettings.txt
2014-04-16 13:07 (INFO) -- announcefetch.pyc:83 - Reading files in fetcher directory:
2014-04-16 13:07 (INFO) -- announcefetch.pyc:92 - announce : 52b6e5624ed25b90d2d2a783ab87635b048aa8b7cb14b21a958ad052faee8691
2014-04-16 13:07 (INFO) -- announcefetch.pyc:92 - bootstrap : 0c68367a6126ed922c90fd06f6b3dc2217248b595adf5c6a1832cdeb4a3ae0b7
2014-04-16 13:07 (INFO) -- announcefetch.pyc:92 - changelog : 00e39ea889395a7148dea87274ee60e484c97c67905b65c67782290dad945639
2014-04-16 13:07 (INFO) -- announcefetch.pyc:92 - downloads : b553c42962f36961f7ac56b85bdd8d6656a16a95c2ce0bc9d60670165825f786
2014-04-16 13:07 (INFO) -- announcefetch.pyc:92 - notify : 011ee87ce2b50a18a06ca4a05f95c5a8f7dc9d55cced2a4654c609eea2795f4c
2014-04-16 13:07 (INFO) -- announcefetch.pyc:249 - Fetching: https://bitcoinarmory.com/announce.txt?osvar=7&os=win&ver=0.91&id=e7d396f6
2014-04-16 13:07 (INFO) -- ArmoryQt.py:2244 - loadWalletsAndSettings
2014-04-16 13:07 (INFO) -- ArmoryQt.py:2302 - Loading wallets...
2014-04-16 13:07 (INFO) -- ArmoryQt.py:2351 - Number of wallets read in: 1
2014-04-16 13:07 (INFO) -- ArmoryQt.py:2356 - Wallet (asdfasdf): "sdfasdfasdfasdf" (Encrypted)
2014-04-16 13:07 (INFO) -- ArmoryQt.py:1786 - Setting up networking...
2014-04-16 13:07 (INFO) -- ArmoryQt.py:1838 - Internet connection is Available: True
2014-04-16 13:07 (INFO) -- ArmoryQt.py:1839 - Bitcoin-Qt/bitcoind is Available: 8333
2014-04-16 13:07 (INFO) -- ArmoryQt.py:1840 - The first blk*.dat was Available: True
2014-04-16 13:07 (INFO) -- ArmoryQt.py:1841 - Online mode currently possible: True
2014-04-16 13:07 (INFO) -- ArmoryQt.py:2028 - loadBlockchainIfNecessary
2014-04-16 13:07 (INFO) -- ArmoryQt.py:2074 - Setting netmode: 1
2014-04-16 13:07 (INFO) -- BDM.pyc:431 - Setting online mode: True (wait=False)
2014-04-16 13:07 (INFO) -- BDM.pyc:1358 - Go online requested
2014-04-16 13:07 (ERROR) -- announcefetch.pyc:261 - Specified URL was inaccessible
2014-04-16 13:07 (ERROR) -- announcefetch.pyc:262 - Tried: https://bitcoinarmory.com/announce.txt?osvar=7&os=win&ver=0.91&id=e7d396f6
2014-04-16 13:07 (INFO) -- announcefetch.pyc:249 - Fetching: https://s3.amazonaws.com/bitcoinarmory-media/announce.txt?ver=0.91
2014-04-16 13:07 (INFO) -- ArmoryQt.py:1099 - setupUriRegistration
2014-04-16 13:07 (INFO) -- ArmoryQt.py:1167 - Armory already registered for current user. Done!
2014-04-16 13:07 (INFO) -- ArmoryQt.py:585 - Usermode: Expert
2014-04-16 13:07 (INFO) -- ArmoryQt.py:1366 - Changing usermode:
2014-04-16 13:07 (INFO) -- ArmoryQt.py:1367 - From: Expert
2014-04-16 13:07 (INFO) -- ArmoryQt.py:1375 - To: Expert
2014-04-16 13:07 (INFO) -- ArmoryQt.py:5610 - Dashboard switched to "Scanning" mode
2014-04-16 13:07 (INFO) -- ArmoryQt.py:4914 - Switching Armory state text to Mgmt:User, State:ScanWithWallets
2014-04-16 13:07 (INFO) -- ArmoryQt.py:4914 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo
2014-04-16 13:07 (INFO) -- ArmoryQt.py:4856 - Switching Armory functional mode to "Scanning"
2014-04-16 13:07 (INFO) -- ArmoryQt.py:698 - MinimizeOnOpen is True
2014-04-16 13:07 (INFO) -- ArmoryQt.py:6334 - Another Armory instance just tried to open.
2014-04-16 13:07 (INFO) -- Networking.pyc:63 - Connection initiated. Start handshake
2014-04-16 13:07 (INFO) -- ArmoryQt.py:5610 - Dashboard switched to "Scanning" mode
2014-04-16 13:07 (INFO) -- ArmoryQt.py:4914 - Switching Armory state text to Mgmt:User, State:ScanWithWallets
2014-04-16 13:07 (INFO) -- ArmoryQt.py:4914 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo
2014-04-16 13:07 (INFO) -- ArmoryQt.py:4856 - Switching Armory functional mode to "Scanning"
2014-04-16 13:07 (INFO) -- Networking.pyc:152 - Received version message from peer:
2014-04-16 13:07 (INFO) -- Networking.pyc:153 - Version: 70002
2014-04-16 13:07 (INFO) -- Networking.pyc:154 - SubVersion: /Satoshi:0.9.1/
2014-04-16 13:07 (INFO) -- Networking.pyc:155 - TimeStamp: 1397646436
2014-04-16 13:07 (INFO) -- Networking.pyc:156 - StartHeight: 296082
2014-04-16 13:07 (INFO) -- Networking.pyc:348 - Handshake finished, connection open!
2014-04-16 13:07 (ERROR) -- announcefetch.pyc:162 - Loop was busy for more than one second
2014-04-16 13:08 (INFO) -- ArmoryQt.py:6147 - BDM state is scanning -- force shutdown BDM
2014-04-16 13:08 (INFO) -- SDM.pyc:636 - Called stopBitcoind
2014-04-16 13:08 (INFO) -- SDM.pyc:638 - ...but bitcoind is not running, to be able to stop
2014-04-16 13:08 (INFO) -- ArmoryQt.py:6162 - Attempting to close the main window!
2014-04-16 13:08 (INFO) -- ArmoryQt.py:6435 - Resetting BlockDataMgr, freeing memory
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:919 - C++ block utilities loaded successfully
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1009 -
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1010 -
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1011 -
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1012 - ************************************************************
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1013 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1014 - ************************************************************
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1015 - Loading Armory Engine:
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1016 - Armory Version : 0.91
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1017 - PyBtcWallet Version : 1.35
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1018 - Detected Operating system: Windows
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1019 - OS Variant : 7-6.1.7601-SP1-Multiprocessor Free
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1020 - User home-directory : C:\Users\bob\AppData\Roaming
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1021 - Satoshi BTC directory : C:\Users\bob\AppData\Roaming\Bitcoin\
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1022 - Armory home dir : C:\Users\bob\AppData\Roaming\Armory\
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1023 - Detected System Specs :
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1024 - Total Available RAM : 15.99 GB
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1025 - CPU ID string : Intel64 Family 5 Model 24 Stepping 2, GenuineIntel
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1026 - Number of CPU cores : 6 cores
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1027 - System is 64-bit : False
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1028 - Preferred Encoding : cp1252
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1029 -
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1030 - Network Name: Main Network
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1031 - Satoshi Port: 8333
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1032 - Named options/arguments to armoryengine.py:
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1034 - maxOpenFiles : 0
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1034 - nettimeout : 2
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1034 - rescan : False
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1034 - leveldbDir : DEFAULT
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1034 - ignoreAllZC : False
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1034 - port : None
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1034 - interport : 8223
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1034 - coverageOutputDir: None
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1034 - rebuild : False
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1034 - datadir : DEFAULT
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1034 - offline : False
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1034 - noWalletCheck : False
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1034 - satoshiPort : DEFAULT
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1034 - netlog : False
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1034 - keypool : 100
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1034 - coverageInclude : None
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1034 - forceOnline : False
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1034 - skipAnnounceCheck: False
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1034 - redownload : False
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1034 - disableTorrent : False
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1034 - testAnnounceCode: False
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1034 - mtdebug : False
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1034 - skipVerCheck : False
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1034 - settingsPath : C:\Users\bob\AppData\Roaming\Armory\ArmorySettings.txt
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1034 - verbosity : None
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1034 - doDebug : False
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1034 - testnet : False
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1034 - rpcport : DEFAULT
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1034 - satoshiHome : DEFAULT
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1034 - satoshiRpcport : DEFAULT
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1034 - logDisable : False
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1034 - logFile : C:\Users\bob\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1035 - Other arguments:
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1038 - ************************************************************
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:1386 - C++ block utilities loaded successfully
2014-04-16 13:29 (INFO) -- BDM.pyc:1420 - Using the asynchronous/multi-threaded BlockDataManager.
2014-04-16 13:29 (INFO) -- BDM.pyc:1421 - Blockchain operations will happen in the background.
2014-04-16 13:29 (INFO) -- BDM.pyc:1422 - Devs: check TheBDM.getBDMState() before asking for data.
2014-04-16 13:29 (INFO) -- BDM.pyc:1423 - Registering addresses during rescans will queue them for
2014-04-16 13:29 (INFO) -- BDM.pyc:1424 - inclusion after the current scan is completed.
2014-04-16 13:29 (INFO) -- ArmoryUtils.pyc:3007 - Using settings file: C:\Users\bob\AppData\Roaming\Armory\ArmorySettings.txt
2014-04-16 13:29 (INFO) -- announcefetch.pyc:83 - Reading files in fetcher directory:
2014-04-16 13:29 (INFO) -- announcefetch.pyc:92 - announce : 52b6e5624ed25b90d2d2a783ab87635b048aa8b7cb14b21a958ad052faee8691
2014-04-16 13:29 (INFO) -- announcefetch.pyc:92 - bootstrap : 0c68367a6126ed922c90fd06f6b3dc2217248b595adf5c6a1832cdeb4a3ae0b7
2014-04-16 13:29 (INFO) -- announcefetch.pyc:92 - changelog : 00e39ea889395a7148dea87274ee60e484c97c67905b65c67782290dad945639
2014-04-16 13:29 (INFO) -- announcefetch.pyc:92 - downloads : b553c42962f36961f7ac56b85bdd8d6656a16a95c2ce0bc9d60670165825f786
2014-04-16 13:29 (INFO) -- announcefetch.pyc:92 - notify : 011ee87ce2b50a18a06ca4a05f95c5a8f7dc9d55cced2a4654c609eea2795f4c
2014-04-16 13:29 (INFO) -- announcefetch.pyc:249 - Fetching: https://bitcoinarmory.com/announce.txt?osvar=7&os=win&ver=0.91&id=e7d396f6
2014-04-16 13:29 (INFO) -- ArmoryQt.py:2244 - loadWalletsAndSettings
2014-04-16 13:29 (INFO) -- ArmoryQt.py:2302 - Loading wallets...
2014-04-16 13:29 (INFO) -- ArmoryQt.py:2351 - Number of wallets read in: 1
2014-04-16 13:29 (INFO) -- ArmoryQt.py:2356 - Wallet (sdfgdsfg): "nvbmghnfgdhsdfg" (Encrypted)
2014-04-16 13:29 (INFO) -- ArmoryQt.py:1786 - Setting up networking...
2014-04-16 13:29 (ERROR) -- announcefetch.pyc:261 - Specified URL was inaccessible
2014-04-16 13:29 (ERROR) -- announcefetch.pyc:262 - Tried: https://bitcoinarmory.com/announce.txt?osvar=7&os=win&ver=0.91&id=e7d396f6
2014-04-16 13:29 (INFO) -- announcefetch.pyc:249 - Fetching: https://s3.amazonaws.com/bitcoinarmory-media/announce.txt?ver=0.91
2014-04-16 13:29 (INFO) -- ArmoryQt.py:1838 - Internet connection is Available: True
2014-04-16 13:29 (INFO) -- ArmoryQt.py:1839 - Bitcoin-Qt/bitcoind is Available: 8333
2014-04-16 13:29 (INFO) -- ArmoryQt.py:1840 - The first blk*.dat was Available: True
2014-04-16 13:29 (INFO) -- ArmoryQt.py:1841 - Online mode currently possible: True
2014-04-16 13:29 (INFO) -- ArmoryQt.py:2028 - loadBlockchainIfNecessary
2014-04-16 13:29 (INFO) -- ArmoryQt.py:2074 - Setting netmode: 1
2014-04-16 13:29 (INFO) -- BDM.pyc:431 - Setting online mode: True (wait=False)
2014-04-16 13:29 (INFO) -- BDM.pyc:1358 - Go online requested
2014-04-16 13:29 (INFO) -- ArmoryQt.py:1099 - setupUriRegistration
2014-04-16 13:29 (INFO) -- ArmoryQt.py:1167 - Armory already registered for current user. Done!
2014-04-16 13:29 (INFO) -- ArmoryQt.py:585 - Usermode: Expert
2014-04-16 13:29 (INFO) -- ArmoryQt.py:1366 - Changing usermode:
2014-04-16 13:29 (INFO) -- ArmoryQt.py:1367 - From: Expert
2014-04-16 13:29 (INFO) -- ArmoryQt.py:1375 - To: Expert
2014-04-16 13:29 (INFO) -- ArmoryQt.py:5610 - Dashboard switched to "Scanning" mode
2014-04-16 13:29 (INFO) -- ArmoryQt.py:4914 - Switching Armory state text to Mgmt:User, State:ScanWithWallets
2014-04-16 13:29 (INFO) -- ArmoryQt.py:4914 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo
2014-04-16 13:29 (INFO) -- ArmoryQt.py:4856 - Switching Armory functional mode to "Scanning"
2014-04-16 13:29 (INFO) -- ArmoryQt.py:698 - MinimizeOnOpen is True
2014-04-16 13:29 (INFO) -- Networking.pyc:63 - Connection initiated. Start handshake
2014-04-16 13:29 (INFO) -- ArmoryQt.py:5610 - Dashboard switched to "Scanning" mode
2014-04-16 13:29 (INFO) -- ArmoryQt.py:4914 - Switching Armory state text to Mgmt:User, State:ScanWithWallets
2014-04-16 13:29 (INFO) -- ArmoryQt.py:4914 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo
2014-04-16 13:29 (INFO) -- ArmoryQt.py:4856 - Switching Armory functional mode to "Scanning"
2014-04-16 13:29 (INFO) -- Networking.pyc:152 - Received version message from peer:
2014-04-16 13:29 (INFO) -- Networking.pyc:153 - Version: 70002
2014-04-16 13:29 (INFO) -- Networking.pyc:154 - SubVersion: /Satoshi:0.9.1/
2014-04-16 13:29 (INFO) -- Networking.pyc:155 - TimeStamp: 1397647769
2014-04-16 13:29 (INFO) -- Networking.pyc:156 - StartHeight: 296143
2014-04-16 13:29 (INFO) -- Networking.pyc:348 - Handshake finished, connection open!
2014-04-16 13:31 (ERROR) -- Networking.pyc:357 - ***Connection to Satoshi client LOST! Attempting to reconnect...
2014-04-16 13:31 (INFO) -- ArmoryQt.py:5610 - Dashboard switched to "Scanning" mode
2014-04-16 13:31 (INFO) -- ArmoryQt.py:4914 - Switching Armory state text to Mgmt:User, State:ScanWithWallets
2014-04-16 13:31 (INFO) -- ArmoryQt.py:4914 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo
2014-04-16 13:31 (INFO) -- ArmoryQt.py:4856 - Switching Armory functional mode to "Scanning"
2014-04-16 13:31 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 0.0
2014-04-16 13:31 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 0.0
2014-04-16 13:32 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 0.1
2014-04-16 13:32 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 0.1
2014-04-16 13:32 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 0.2
2014-04-16 13:32 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 0.2
2014-04-16 13:32 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 0.3
2014-04-16 13:32 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 0.5
2014-04-16 13:32 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 0.6
2014-04-16 13:32 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 0.8
2014-04-16 13:32 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 0.8
2014-04-16 13:33 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 0.9
2014-04-16 13:33 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 1.1
2014-04-16 13:33 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 1.2
2014-04-16 13:33 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 1.3
2014-04-16 13:33 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 1.5
2014-04-16 13:34 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 1.5
2014-04-16 13:34 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 1.7
2014-04-16 13:34 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 1.7
2014-04-16 13:34 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 1.8
2014-04-16 13:34 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 1.9
2014-04-16 13:34 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 2.0
2014-04-16 13:34 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 2.1
2014-04-16 13:34 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 2.1
2014-04-16 13:34 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 2.1
2014-04-16 13:34 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 2.2
2014-04-16 13:35 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 2.3
2014-04-16 13:35 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 2.3
2014-04-16 13:35 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 2.4
2014-04-16 13:35 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 2.5
2014-04-16 13:35 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 2.6
2014-04-16 13:35 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 2.6
2014-04-16 13:35 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 2.8
2014-04-16 13:35 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 2.8
2014-04-16 13:36 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 2.8
2014-04-16 13:36 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 2.9
2014-04-16 13:36 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 3.0
2014-04-16 13:36 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 3.1
2014-04-16 13:36 (INFO) -- ArmoryQt.py:2074 - Setting netmode: 1
2014-04-16 13:36 (INFO) -- Networking.pyc:63 - Connection initiated. Start handshake
2014-04-16 13:36 (INFO) -- ArmoryQt.py:5610 - Dashboard switched to "Scanning" mode
2014-04-16 13:36 (INFO) -- ArmoryQt.py:4914 - Switching Armory state text to Mgmt:User, State:ScanWithWallets
2014-04-16 13:36 (INFO) -- ArmoryQt.py:4914 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo
2014-04-16 13:36 (INFO) -- ArmoryQt.py:4856 - Switching Armory functional mode to "Scanning"
2014-04-16 13:36 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 3.2
2014-04-16 13:36 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 3.2
2014-04-16 13:36 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 3.3
2014-04-16 13:37 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 3.4
2014-04-16 13:37 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 3.4
2014-04-16 13:37 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 3.5
2014-04-16 13:37 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 3.6
2014-04-16 13:37 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 3.6
2014-04-16 13:37 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 3.6
2014-04-16 13:37 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 3.7
2014-04-16 13:37 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 3.8
2014-04-16 13:38 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 3.8
2014-04-16 13:38 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 3.8
2014-04-16 13:38 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 3.9
2014-04-16 13:38 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 4.0
2014-04-16 13:38 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 4.0
2014-04-16 13:38 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 4.1
2014-04-16 13:39 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 4.2
2014-04-16 13:39 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 4.2
2014-04-16 13:39 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 4.3
2014-04-16 13:39 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 4.3
2014-04-16 13:39 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 4.3
2014-04-16 13:39 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 4.4
2014-04-16 13:39 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 4.5
2014-04-16 13:40 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 4.5
2014-04-16 13:40 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 4.6
2014-04-16 13:40 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 4.7
2014-04-16 13:40 (INFO) -- Networking.pyc:152 - Received version message from peer:
2014-04-16 13:40 (INFO) -- Networking.pyc:153 - Version: 70002
2014-04-16 13:40 (INFO) -- Networking.pyc:154 - SubVersion: /Satoshi:0.9.1/
2014-04-16 13:40 (INFO) -- Networking.pyc:155 - TimeStamp: 1397648420
2014-04-16 13:40 (INFO) -- Networking.pyc:156 - StartHeight: 296143
2014-04-16 13:40 (INFO) -- Networking.pyc:348 - Handshake finished, connection open!
2014-04-16 13:40 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 4.7
2014-04-16 13:40 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 4.8
2014-04-16 13:40 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 4.8
2014-04-16 13:40 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 4.9
2014-04-16 13:40 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 5.0
2014-04-16 13:40 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 5.1
2014-04-16 13:40 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 5.1
2014-04-16 13:41 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 5.1
2014-04-16 13:41 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 5.2
2014-04-16 13:41 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 5.2
2014-04-16 13:41 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 5.3
2014-04-16 13:41 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 5.3
2014-04-16 13:41 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 5.4
2014-04-16 13:41 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 5.5
2014-04-16 13:41 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 5.5
2014-04-16 13:41 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 5.5
2014-04-16 13:41 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 5.6
2014-04-16 13:42 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 5.7
2014-04-16 13:42 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 5.8
2014-04-16 13:42 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 5.8
2014-04-16 13:42 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 5.9
2014-04-16 13:42 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 5.9
2014-04-16 13:42 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 6.0
2014-04-16 13:42 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 6.0
2014-04-16 13:42 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 6.1
2014-04-16 13:43 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 6.2
2014-04-16 13:43 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 6.2
2014-04-16 13:43 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 6.3
2014-04-16 13:43 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 6.4
2014-04-16 13:43 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 6.4
2014-04-16 13:43 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 6.5
2014-04-16 13:43 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 6.6
2014-04-16 13:43 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 6.6
2014-04-16 13:43 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 6.6
2014-04-16 13:43 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 6.7
2014-04-16 13:43 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 6.7
2014-04-16 13:44 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 6.8
2014-04-16 13:44 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 6.9
2014-04-16 13:44 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 6.9
2014-04-16 13:44 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 7.0
2014-04-16 13:44 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 7.0
2014-04-16 13:44 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 7.1
2014-04-16 13:44 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 7.2
2014-04-16 13:45 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 7.2
2014-04-16 13:45 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 7.2
2014-04-16 13:45 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 7.3
2014-04-16 13:45 (INFO) -- Networking.pyc:63 - Connection initiated. Start handshake
2014-04-16 13:45 (INFO) -- ArmoryQt.py:5610 - Dashboard switched to "Scanning" mode
2014-04-16 13:45 (INFO) -- ArmoryQt.py:4914 - Switching Armory state text to Mgmt:User, State:ScanWithWallets
2014-04-16 13:45 (INFO) -- ArmoryQt.py:4914 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo
2014-04-16 13:45 (INFO) -- ArmoryQt.py:4856 - Switching Armory functional mode to "Scanning"
2014-04-16 13:45 (INFO) -- Networking.pyc:152 - Received version message from peer:
2014-04-16 13:45 (INFO) -- Networking.pyc:153 - Version: 70002
2014-04-16 13:45 (INFO) -- Networking.pyc:154 - SubVersion: /Satoshi:0.9.1/
2014-04-16 13:45 (INFO) -- Networking.pyc:155 - TimeStamp: 1397648714
2014-04-16 13:45 (INFO) -- Networking.pyc:156 - StartHeight: 296145
2014-04-16 13:45 (INFO) -- Networking.pyc:348 - Handshake finished, connection open!
2014-04-16 13:45 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 7.4
2014-04-16 13:45 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 7.4
2014-04-16 13:45 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 7.4
2014-04-16 13:45 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 7.5
2014-04-16 13:45 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 7.5
2014-04-16 13:46 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 7.6
2014-04-16 13:46 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 7.6
2014-04-16 13:46 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 7.7
2014-04-16 13:46 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 7.7
2014-04-16 13:46 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 7.7
2014-04-16 13:46 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 7.8
2014-04-16 13:46 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 7.8
2014-04-16 13:46 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 7.9
2014-04-16 13:46 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 7.9
2014-04-16 13:46 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 8.0
2014-04-16 13:46 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 8.0
2014-04-16 13:47 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 8.1
2014-04-16 13:47 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 8.1
2014-04-16 13:47 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 8.1
2014-04-16 13:47 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 8.2
2014-04-16 13:47 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 8.2
2014-04-16 13:47 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 8.3
2014-04-16 13:47 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 8.3
2014-04-16 13:47 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 8.4
2014-04-16 13:47 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 8.4
2014-04-16 13:47 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 8.5
2014-04-16 13:47 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 8.5
2014-04-16 13:47 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 8.5
2014-04-16 13:48 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 8.6
2014-04-16 13:48 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 8.6
2014-04-16 13:48 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 8.7
2014-04-16 13:48 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 8.7
2014-04-16 13:48 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 8.7
2014-04-16 13:48 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 8.8
2014-04-16 13:48 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 8.8
2014-04-16 13:48 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 8.9
2014-04-16 13:52 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 8.9
2014-04-16 13:52 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 9.0
2014-04-16 13:52 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 9.1
2014-04-16 13:52 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 9.2
2014-04-16 13:52 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 9.3
2014-04-16 13:53 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 9.4
2014-04-16 13:53 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 9.4
2014-04-16 13:53 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 9.5
2014-04-16 13:53 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 9.6
2014-04-16 13:53 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 9.6
2014-04-16 13:53 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 9.7
2014-04-16 13:53 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 9.8
2014-04-16 13:54 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 9.9
2014-04-16 13:54 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 10.0
2014-04-16 13:54 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 10.1
2014-04-16 13:54 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 10.2
2014-04-16 13:54 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 10.3
2014-04-16 13:54 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 10.4
2014-04-16 13:54 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 10.4
2014-04-16 13:54 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 10.5
2014-04-16 13:54 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 10.5
2014-04-16 13:54 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 10.6
2014-04-16 13:55 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 10.7
2014-04-16 13:55 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 10.8
2014-04-16 13:55 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 10.8
2014-04-16 13:55 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 10.8
2014-04-16 13:55 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 10.9
2014-04-16 13:55 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 10.9
2014-04-16 13:55 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 11.0
2014-04-16 13:55 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 11.1
2014-04-16 13:55 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 11.1
2014-04-16 13:55 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 11.1
2014-04-16 13:55 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 11.2
2014-04-16 13:56 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 11.3
2014-04-16 13:56 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 11.3
2014-04-16 13:56 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 11.4
2014-04-16 13:56 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 11.4
2014-04-16 13:56 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 11.5
2014-04-16 13:56 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 11.5
2014-04-16 13:56 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 11.6
2014-04-16 13:56 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 11.7
2014-04-16 13:57 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 11.7
2014-04-16 13:57 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 11.8
2014-04-16 13:57 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 11.8
2014-04-16 13:57 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 11.9
2014-04-16 13:57 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 11.9
2014-04-16 13:57 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 11.9
2014-04-16 13:57 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 12.0
2014-04-16 13:57 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 12.1
2014-04-16 13:57 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 12.1
2014-04-16 13:57 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 12.1
2014-04-16 13:57 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 12.2
2014-04-16 13:58 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 12.3
2014-04-16 13:58 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 12.3
2014-04-16 13:58 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 12.3
2014-04-16 13:58 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 12.4
2014-04-16 13:58 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 12.4
2014-04-16 13:58 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 12.5
2014-04-16 13:58 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 12.5
2014-04-16 13:58 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 12.6
2014-04-16 13:58 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 12.6
2014-04-16 13:58 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 12.6
2014-04-16 13:58 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 12.7
2014-04-16 13:58 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 12.7
2014-04-16 13:59 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 12.8
2014-04-16 13:59 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 12.8
2014-04-16 13:59 (INFO) -- announcefetch.pyc:249 - Fetching: https://bitcoinarmory.com/announce.txt?ver=0.91
2014-04-16 13:59 (ERROR) -- announcefetch.pyc:261 - Specified URL was inaccessible
2014-04-16 13:59 (ERROR) -- announcefetch.pyc:262 - Tried: https://bitcoinarmory.com/announce.txt?ver=0.91
2014-04-16 13:59 (INFO) -- announcefetch.pyc:249 - Fetching: https://s3.amazonaws.com/bitcoinarmory-media/announce.txt?ver=0.91
2014-04-16 13:59 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 12.8
2014-04-16 13:59 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 12.9
2014-04-16 13:59 (INFO) -- BDM.pyc:384 - Reading blockchain, pct complete: 12.9
I dont know the range of connections listen=1 allows. Changing the default port and blocking all external traffic to it takes care of potential surprises.
Ok, I just crapped my pants - I won't be using --satoshi-port=9150 anymore, I think you are right and I was connecting to an outside node (while I had massive disconnections, synch and balances were OK all the time, so Armory wasn't in "offline" mode but connected to a node).
..good thing all blocks are cryptographically signed and will be verified locally, right? :-)
Ente
Armory doesnt verify the blocks it reads, it trusts Bitcoin Core to do that. Ill let you imagine how nasty that can get when an attacker gets to connect to your instance of Armory as its "good" node.
Got it work in a somewhat acceptable setting.
This is my bitcoin.conf:
proxy=127.0.0.1:9050
listen=1
port=8331
My Tor is set to run its proxy on 9050 by default.
8331 is a port I chose for Armory to connect to. Armory has to run with the --satoshi-port=8331 switch.
In my firewall, I added a rule to block all network traffic to port 8331. This way only localhost can connect to a socket listening on that port. This seems to work fine. Observing bitcoin, it only connects to nodes through the Tor proxy besides Armory, locally.
If I add only "listen=1" to bitcoin.conf and I run Armory with no arguments whatsoever it works fine, how is that more insecure/worst than the set up you suggest? I don't seem to need "port=8331" in bitcoin.conf nor the "--satoshi-port=8331" argument for Armory, all the additional steps you mention seem to complicate the process unnecesarily.
Testing that now actually.
Ok, I just crapped my pants - I won't be using --satoshi-port=9150 anymore, I think you are right and I was connecting to an outside node (while I had massive disconnections, synch and balances were OK all the time, so Armory wasn't in "offline" mode but connected to a node).
..good thing all blocks are cryptographically signed and will be verified locally, right? :-)
Ente
Armory doesnt verify the blocks it reads, it trusts Bitcoin Core to do that. Ill let you imagine how nasty that can get when an attacker gets to connect to your instance of Armory as its "good" node.
Oopsie..
Got it work in a somewhat acceptable setting.
This is my bitcoin.conf:
proxy=127.0.0.1:9050
listen=1
port=8331
My Tor is set to run its proxy on 9050 by default.
8331 is a port I chose for Armory to connect to. Armory has to run with the --satoshi-port=8331 switch.
In my firewall, I added a rule to block all network traffic to port 8331. This way only localhost can connect to a socket listening on that port. This seems to work fine. Observing bitcoin, it only connects to nodes through the Tor proxy besides Armory, locally.
This is my bitcoin.conf:
proxy=127.0.0.1:9050
listen=1
port=8331
My Tor is set to run its proxy on 9050 by default.
8331 is a port I chose for Armory to connect to. Armory has to run with the --satoshi-port=8331 switch.
In my firewall, I added a rule to block all network traffic to port 8331. This way only localhost can connect to a socket listening on that port. This seems to work fine. Observing bitcoin, it only connects to nodes through the Tor proxy besides Armory, locally.
Thank you! I too will eventually play with bitcoin, Armory and TOR.
Since we are at it already: It shouldn't make any problems to have one bitcoin-core listen/connect to both TOR and clearnet, through two ports, at the same time? It would be some kind of bitcoin clearnet-TOR gateway that way I imagine..
Ente
Ok, I just crapped my pants - I won't be using --satoshi-port=9150 anymore, I think you are right and I was connecting to an outside node (while I had massive disconnections, synch and balances were OK all the time, so Armory wasn't in "offline" mode but connected to a node).
..good thing all blocks are cryptographically signed and will be verified locally, right? :-)
Ente
Armory doesnt verify the blocks it reads, it trusts Bitcoin Core to do that. Ill let you imagine how nasty that can get when an attacker gets to connect to your instance of Armory as its "good" node.
Got it work in a somewhat acceptable setting.
This is my bitcoin.conf:
proxy=127.0.0.1:9050
listen=1
port=8331
My Tor is set to run its proxy on 9050 by default.
8331 is a port I chose for Armory to connect to. Armory has to run with the --satoshi-port=8331 switch.
In my firewall, I added a rule to block all network traffic to port 8331. This way only localhost can connect to a socket listening on that port. This seems to work fine. Observing bitcoin, it only connects to nodes through the Tor proxy besides Armory, locally.
Ok, I just crapped my pants - I won't be using --satoshi-port=9150 anymore, I think you are right and I was connecting to an outside node (while I had massive disconnections, synch and balances were OK all the time, so Armory wasn't in "offline" mode but connected to a node).
..good thing all blocks are cryptographically signed and will be verified locally, right? :-)
Ente
An update on my work in progress to get Armory to work with Tor on OSX 10.9.2 and Bitcoin Core 0.9.1
There are only two ways in which I succeed:
a) I start Bitcoin Core with the -listen=1 argument. I'm a bit fearful of this solution because while I understand what "listening to incoming connections" means, I'm not sure what are the risks involved - I'm behind a NAT router and I should probably be OK, but I'm not confident because I don't understand what kind of attack I might suffer with this config. Using -listen=1 with Bitcoin Core I just start Armory normally and it works perfectly.
b) I start Armory with the --satoshi-port=9150 argument (note: 9150 is the port Tor uses, and through which my Bitcoin Core connects). With this solution I don't need any argument on Bitcoin Core (obviously not "listen=1", but neither "addnode=127.0.0.1"), it just works... But there is a tradeoff. Armory is less stable and while it synchs OK, scans transactions correctly, and displays the right balance, the connected/disconnected word in the right bottom corner blinks non stop, switching from "discconected" to "connected" like crazy - same thing happens with the Offline/Online word on the main screen.
Just to be clear, I have this issues only because I'm using Tor, if I remove the proxy settings from Bitcoin Core thus not routing it through Tor Armory just works great without any additional arguments on Bitcoin Core or Armory.
There are only two ways in which I succeed:
a) I start Bitcoin Core with the -listen=1 argument. I'm a bit fearful of this solution because while I understand what "listening to incoming connections" means, I'm not sure what are the risks involved - I'm behind a NAT router and I should probably be OK, but I'm not confident because I don't understand what kind of attack I might suffer with this config. Using -listen=1 with Bitcoin Core I just start Armory normally and it works perfectly.
b) I start Armory with the --satoshi-port=9150 argument (note: 9150 is the port Tor uses, and through which my Bitcoin Core connects). With this solution I don't need any argument on Bitcoin Core (obviously not "listen=1", but neither "addnode=127.0.0.1"), it just works... But there is a tradeoff. Armory is less stable and while it synchs OK, scans transactions correctly, and displays the right balance, the connected/disconnected word in the right bottom corner blinks non stop, switching from "discconected" to "connected" like crazy - same thing happens with the Offline/Online word on the main screen.
Just to be clear, I have this issues only because I'm using Tor, if I remove the proxy settings from Bitcoin Core thus not routing it through Tor Armory just works great without any additional arguments on Bitcoin Core or Armory.
Do not use this port. You are letting Armory connect through the Tor proxy. That's bad, Armory could possibly connect to an outside node this way, and this is what I think you are seeing with the massive disconnect.
I'm busy right now but I'll setup the Tor proxy later tonight and figure out a proper setting.
Ok, I just crapped my pants - I won't be using --satoshi-port=9150 anymore, I think you are right and I was connecting to an outside node (while I had massive disconnections, synch and balances were OK all the time, so Armory wasn't in "offline" mode but connected to a node).
An update on my work in progress to get Armory to work with Tor on OSX 10.9.2 and Bitcoin Core 0.9.1
There are only two ways in which I succeed:
a) I start Bitcoin Core with the -listen=1 argument. I'm a bit fearful of this solution because while I understand what "listening to incoming connections" means, I'm not sure what are the risks involved - I'm behind a NAT router and I should probably be OK, but I'm not confident because I don't understand what kind of attack I might suffer with this config. Using -listen=1 with Bitcoin Core I just start Armory normally and it works perfectly.
b) I start Armory with the --satoshi-port=9150 argument (note: 9150 is the port Tor uses, and through which my Bitcoin Core connects). With this solution I don't need any argument on Bitcoin Core (obviously not "listen=1", but neither "addnode=127.0.0.1"), it just works... But there is a tradeoff. Armory is less stable and while it synchs OK, scans transactions correctly, and displays the right balance, the connected/disconnected word in the right bottom corner blinks non stop, switching from "discconected" to "connected" like crazy - same thing happens with the Offline/Online word on the main screen.
Just to be clear, I have this issues only because I'm using Tor, if I remove the proxy settings from Bitcoin Core thus not routing it through Tor Armory just works great without any additional arguments on Bitcoin Core or Armory.
There are only two ways in which I succeed:
a) I start Bitcoin Core with the -listen=1 argument. I'm a bit fearful of this solution because while I understand what "listening to incoming connections" means, I'm not sure what are the risks involved - I'm behind a NAT router and I should probably be OK, but I'm not confident because I don't understand what kind of attack I might suffer with this config. Using -listen=1 with Bitcoin Core I just start Armory normally and it works perfectly.
b) I start Armory with the --satoshi-port=9150 argument (note: 9150 is the port Tor uses, and through which my Bitcoin Core connects). With this solution I don't need any argument on Bitcoin Core (obviously not "listen=1", but neither "addnode=127.0.0.1"), it just works... But there is a tradeoff. Armory is less stable and while it synchs OK, scans transactions correctly, and displays the right balance, the connected/disconnected word in the right bottom corner blinks non stop, switching from "discconected" to "connected" like crazy - same thing happens with the Offline/Online word on the main screen.
Just to be clear, I have this issues only because I'm using Tor, if I remove the proxy settings from Bitcoin Core thus not routing it through Tor Armory just works great without any additional arguments on Bitcoin Core or Armory.
Do not use this port. You are letting Armory connect through the Tor proxy. That's bad, Armory could possibly connect to an outside node this way, and this is what I think you are seeing with the massive disconnect.
I'm busy right now but I'll setup the Tor proxy later tonight and figure out a proper setting.
so i just upgraded to satoshi 0.9.1. i failed to delete 0.9.0 so how do i tell which version Armory is running off of?
An update on my work in progress to get Armory to work with Tor on OSX 10.9.2 and Bitcoin Core 0.9.1
There are only two ways in which I succeed:
a) I start Bitcoin Core with the -listen=1 argument. I'm a bit fearful of this solution because while I understand what "listening to incoming connections" means, I'm not sure what are the risks involved - I'm behind a NAT router and I should probably be OK, but I'm not confident because I don't understand what kind of attack I might suffer with this config. Using -listen=1 with Bitcoin Core I just start Armory normally and it works perfectly.
b) I start Armory with the --satoshi-port=9150 argument (note: 9150 is the port Tor uses, and through which my Bitcoin Core connects). With this solution I don't need any argument on Bitcoin Core (obviously not "listen=1", but neither "addnode=127.0.0.1"), it just works... But there is a tradeoff. Armory is less stable and while it synchs OK, scans transactions correctly, and displays the right balance, the connected/disconnected word in the right bottom corner blinks non stop, switching from "discconected" to "connected" like crazy - same thing happens with the Offline/Online word on the main screen.
Just to be clear, I have this issues only because I'm using Tor, if I remove the proxy settings from Bitcoin Core thus not routing it through Tor Armory just works great without any additional arguments on Bitcoin Core or Armory.
There are only two ways in which I succeed:
a) I start Bitcoin Core with the -listen=1 argument. I'm a bit fearful of this solution because while I understand what "listening to incoming connections" means, I'm not sure what are the risks involved - I'm behind a NAT router and I should probably be OK, but I'm not confident because I don't understand what kind of attack I might suffer with this config. Using -listen=1 with Bitcoin Core I just start Armory normally and it works perfectly.
b) I start Armory with the --satoshi-port=9150 argument (note: 9150 is the port Tor uses, and through which my Bitcoin Core connects). With this solution I don't need any argument on Bitcoin Core (obviously not "listen=1", but neither "addnode=127.0.0.1"), it just works... But there is a tradeoff. Armory is less stable and while it synchs OK, scans transactions correctly, and displays the right balance, the connected/disconnected word in the right bottom corner blinks non stop, switching from "discconected" to "connected" like crazy - same thing happens with the Offline/Online word on the main screen.
Just to be clear, I have this issues only because I'm using Tor, if I remove the proxy settings from Bitcoin Core thus not routing it through Tor Armory just works great without any additional arguments on Bitcoin Core or Armory.
I thought OSX has issues with command line arguments. Add it to the .conf and get back to me.
Also, why :9150? Is this your personal setting? If so you have to set Armory to use that port too.
Also, why :9150? Is this your personal setting? If so you have to set Armory to use that port too.
Still not working. I tried with port 9150 too because that's the port Tor uses. Any idea on how to fix this?
EDIT: just made it work. I had to start Armory with the following argument: --satoshi-port=9150
First of all, my apologies if I'm going the wrong route for this type of question. I realize the development team has a very full plate with development and responding to threads such as this. If proper protocol is to plug this into an issue / suggesting tracking system, I would be happy to do so - I just didn't see one in my looking around.
I also didn't see the answer to this question anywhere else. I saw some mention of it from a year ago where it was a single line change in the python code but this question reaches beyond that, I think. Let me describe my scenario:
Let's say I am dealing with many machines (for the sake of conversation, let's say 2 desktops, 2 laptops, and an offline machine I use for Armory cold storage - all with various OS's). I would like to be able to have a master machine that is responsible for downloading the blockchain and maintaining it for the rest of the machines (especially the laptops since they have limited storage on SSDs). Is there a way to accomplish this? Ideally I would set up Desktop A as the main client that is on all the time and downloads the blockchain. The rest of the machines would use that copy of the blockchain, ideally. I don't necessarily care if the Armory DB is locally stored (for instance having it on a NAS or something on the same network). It would still be a lot less storage overhead than I'm currently dealing with.
Thanks in advance.
I also didn't see the answer to this question anywhere else. I saw some mention of it from a year ago where it was a single line change in the python code but this question reaches beyond that, I think. Let me describe my scenario:
Let's say I am dealing with many machines (for the sake of conversation, let's say 2 desktops, 2 laptops, and an offline machine I use for Armory cold storage - all with various OS's). I would like to be able to have a master machine that is responsible for downloading the blockchain and maintaining it for the rest of the machines (especially the laptops since they have limited storage on SSDs). Is there a way to accomplish this? Ideally I would set up Desktop A as the main client that is on all the time and downloads the blockchain. The rest of the machines would use that copy of the blockchain, ideally. I don't necessarily care if the Armory DB is locally stored (for instance having it on a NAS or something on the same network). It would still be a lot less storage overhead than I'm currently dealing with.
Thanks in advance.
Yes, it's been asked before, but it's not implemented yet.
The closest you can get to that is to either
- have one machine with a regular "online" Bitcoin node, connected to the internet
- have all other local clients connect to that "online" node only, with two full blockchains on every node still
- use a different, light client, like electrum for example. You could even set up your own electrum server on one computer, as I understand it
The general problem, I believe, is that several computers accessing and writing to the same (blockchain-)database will immediately corrupt it, if no precautions are made. So this feature would need a lot of changes under the hood. And probably has a somewhat low demand, for that much effort, compared to other features..
I'm in your boat here. And I run a local "always on" node, where all other nodes connect to when they run, from time to time.
Ente
First of all, my apologies if I'm going the wrong route for this type of question. I realize the development team has a very full plate with development and responding to threads such as this. If proper protocol is to plug this into an issue / suggesting tracking system, I would be happy to do so - I just didn't see one in my looking around.
I also didn't see the answer to this question anywhere else. I saw some mention of it from a year ago where it was a single line change in the python code but this question reaches beyond that, I think. Let me describe my scenario:
Let's say I am dealing with many machines (for the sake of conversation, let's say 2 desktops, 2 laptops, and an offline machine I use for Armory cold storage - all with various OS's). I would like to be able to have a master machine that is responsible for downloading the blockchain and maintaining it for the rest of the machines (especially the laptops since they have limited storage on SSDs). Is there a way to accomplish this? Ideally I would set up Desktop A as the main client that is on all the time and downloads the blockchain. The rest of the machines would use that copy of the blockchain, ideally. I don't necessarily care if the Armory DB is locally stored (for instance having it on a NAS or something on the same network). It would still be a lot less storage overhead than I'm currently dealing with.
Thanks in advance.
I also didn't see the answer to this question anywhere else. I saw some mention of it from a year ago where it was a single line change in the python code but this question reaches beyond that, I think. Let me describe my scenario:
Let's say I am dealing with many machines (for the sake of conversation, let's say 2 desktops, 2 laptops, and an offline machine I use for Armory cold storage - all with various OS's). I would like to be able to have a master machine that is responsible for downloading the blockchain and maintaining it for the rest of the machines (especially the laptops since they have limited storage on SSDs). Is there a way to accomplish this? Ideally I would set up Desktop A as the main client that is on all the time and downloads the blockchain. The rest of the machines would use that copy of the blockchain, ideally. I don't necessarily care if the Armory DB is locally stored (for instance having it on a NAS or something on the same network). It would still be a lot less storage overhead than I'm currently dealing with.
Thanks in advance.
You're not the first to ask this question, and I believe the answer is still "not yet". It's possible that it's been implemented in 0.9x and I didn't notice it, but I don't think that's the case. The developers are aware of requests for this type of thing though, and have stated a commitment to providing the feature in the past.
First of all, my apologies if I'm going the wrong route for this type of question. I realize the development team has a very full plate with development and responding to threads such as this. If proper protocol is to plug this into an issue / suggesting tracking system, I would be happy to do so - I just didn't see one in my looking around.
I also didn't see the answer to this question anywhere else. I saw some mention of it from a year ago where it was a single line change in the python code but this question reaches beyond that, I think. Let me describe my scenario:
Let's say I am dealing with many machines (for the sake of conversation, let's say 2 desktops, 2 laptops, and an offline machine I use for Armory cold storage - all with various OS's). I would like to be able to have a master machine that is responsible for downloading the blockchain and maintaining it for the rest of the machines (especially the laptops since they have limited storage on SSDs). Is there a way to accomplish this? Ideally I would set up Desktop A as the main client that is on all the time and downloads the blockchain. The rest of the machines would use that copy of the blockchain, ideally. I don't necessarily care if the Armory DB is locally stored (for instance having it on a NAS or something on the same network). It would still be a lot less storage overhead than I'm currently dealing with.
Thanks in advance.
I also didn't see the answer to this question anywhere else. I saw some mention of it from a year ago where it was a single line change in the python code but this question reaches beyond that, I think. Let me describe my scenario:
Let's say I am dealing with many machines (for the sake of conversation, let's say 2 desktops, 2 laptops, and an offline machine I use for Armory cold storage - all with various OS's). I would like to be able to have a master machine that is responsible for downloading the blockchain and maintaining it for the rest of the machines (especially the laptops since they have limited storage on SSDs). Is there a way to accomplish this? Ideally I would set up Desktop A as the main client that is on all the time and downloads the blockchain. The rest of the machines would use that copy of the blockchain, ideally. I don't necessarily care if the Armory DB is locally stored (for instance having it on a NAS or something on the same network). It would still be a lot less storage overhead than I'm currently dealing with.
Thanks in advance.
I thought OSX has issues with command line arguments.
CL args are okay as of 0.91.
I thought OSX has issues with command line arguments. Add it to the .conf and get back to me.
Also, why :9150? Is this your personal setting? If so you have to set Armory to use that port too.
Also, why :9150? Is this your personal setting? If so you have to set Armory to use that port too.
The only way to have Armory working with Tor is to have listen=1 on bitcoin.conf, or to start bitcoin with the -listen=1 argument, right?
addnode=127.0.0.1 will make bitcoind try to connect to Armory, which is what you want, and not more. listen=1 is more aggressive than necessary.
Tried to start Bitcoin-QT (I'm using OSX and thus no bitcoind self management) with the following arguments, to no avail:
Code:
-addnode=127.0.0.1
-addnode=127.0.0.1:9150
-addnode=localhost
-addnode=localhost:9150
Armory says it is offline.
Didn't try to add that to bitcoin.conf, but I guess that the result should be the same as if I start the client from the commad line with the aforementioned arguments?
The only way I got armory to work with tor is with -listen=1, which I do not like too much as I worry I'm exposing my Bitcoin client to the world.
Jump to: