 Show Posts
|
|
Pages: [1] 2 3 4 5 »
|
|
2
|
Bitcoin / Armory / Bitcoin Core 0.16.0 vs Armory 0.96.3
|
on: March 11, 2018, 09:30:12 PM
|
|
Will Armory 0.96.3 run as smoothly with Bitcoin Core 0.16.0 like it runs with Bitcoin Core 0.15.1 ?
Has anyone tried the combination yet?
I run the combination on Windows.
|
|
|
|
|
6
|
Local / Nederlands (Dutch) / Re: Belasting thread
|
on: November 05, 2017, 09:58:38 PM
|
|
Eigen beleggingen vallen in box 3.
Ook bitcoins dus. En of je winst of verlies maakt, maakt niet uit.
Zolang je het voor eigen gewin doet, valt het in box 3.
Als je belegt voor iemand anders en daar geld mee verdient, vallen jouw inkomsten in box 1.
Voor die andere persoon valt het in box 3. BV's e.d. uitgezonderd, want dat is een ander verhaal.
De pijldatum voor dat wat in box 3 valt is 1 januari van het jaar waarin je de belasting betaald.
Voorbeeld: Als de pijldatum 1 januari 2018 is, dan geef je het box 3 vermogen op bij de belastingopgave van 2018.
Het gaat dan om de waarde in euro's op 1 januari.
De uitleg van box 3 vermogen staat ook op bijvoorbeeld de bijlage van een aangifteformulier. Het is geen abacadabra. Het woord "bitcoin" staat er letterlijk in genoemd.
|
|
|
|
|
8
|
Bitcoin / Armory / Re: Armory 0.96 is out
|
on: May 10, 2017, 06:24:34 PM
|
Armory crashed every time after scanning.
Emptied %appdata%\Armory\databases , causing Armory to rebuild the database solved this problem.
btw: Amazing that this is the only piece of software that manages to fully use my 16 GB RAM while rebuilding the database. No problem for me.
mmaped RAM, not allocated. Every time another application is started, Windows needs to swap the memory to/from the pagefile. It slows down my system. Even with an SSD.  Problem: Saving/Backing up a wallet unencrypted to a file does not work. "Save to File"
I want to use it to backup the private keys to another encrypted medium. CTRL-C and -V would work, but that is annoying after a while.
Need to see armorylog.txt armorylog.txt Just the parts that are of interest, I think. 2017-05-09 23:15 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 1117, in clickedDoIt
File "ArmoryQt.py", line 1614, in makeWalletCopy
File "armoryengine\Decorators.pyc", line 48, in inner
File "ArmoryQt.py", line 2224, in getFileSave
TypeError: sequence item 0: expected string, QString found
2017-05-09 23:16 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 1117, in clickedDoIt
File "ArmoryQt.py", line 1614, in makeWalletCopy
File "armoryengine\Decorators.pyc", line 48, in inner
File "ArmoryQt.py", line 2224, in getFileSave
TypeError: sequence item 0: expected string, QString found
2017-05-09 23:16 (INFO) -- ArmoryQt.py:4876 - New Block! : 465659
2017-05-09 23:16 (INFO) -- ArmoryQt.py:4884 - Current block number: 465659
2017-05-09 23:18 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 1119, in clickedDoIt
File "ArmoryQt.py", line 1614, in makeWalletCopy
File "armoryengine\Decorators.pyc", line 48, in inner
File "ArmoryQt.py", line 2224, in getFileSave
TypeError: sequence item 0: expected string, QString found
2017-05-09 23:18 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 1119, in clickedDoIt
File "ArmoryQt.py", line 1614, in makeWalletCopy
File "armoryengine\Decorators.pyc", line 48, in inner
File "ArmoryQt.py", line 2224, in getFileSave
TypeError: sequence item 0: expected string, QString found
2017-05-09 23:18 (ERROR) -- ArmoryUtils.pyc:3223 - Error in pybkgdthread: Incorrect passphrase for wallet
Traceback (most recent call last):
File "armoryengine\ArmoryUtils.pyc", line 3221, in run
File "armoryengine\ArmoryUtils.pyc", line 3158, in funcPartial
File "qtdialogs.pyc", line 12949, in exec_async
PassphraseError: Incorrect passphrase for wallet
2017-05-09 23:19 (ERROR) -- Traceback (most recent call last):
File "qtdialogs.pyc", line 5065, in saveToFile
ValueError: unsupported format character '_' (0x5f) at index 10
2017-05-09 23:19 (ERROR) -- Traceback (most recent call last):
File "qtdialogs.pyc", line 5065, in saveToFile
ValueError: unsupported format character '_' (0x5f) at index 10
2017-05-09 23:19 (ERROR) -- Traceback (most recent call last):
File "qtdialogs.pyc", line 5065, in saveToFile
ValueError: unsupported format character '_' (0x5f) at index 10
2017-05-09 23:19 (ERROR) -- Traceback (most recent call last):
File "qtdialogs.pyc", line 5065, in saveToFile
ValueError: unsupported format character '_' (0x5f) at index 10
2017-05-09 23:19 (ERROR) -- Traceback (most recent call last):
File "qtdialogs.pyc", line 5065, in saveToFile
ValueError: unsupported format character '_' (0x5f) at index 10
2017-05-09 23:19 (ERROR) -- Traceback (most recent call last):
File "qtdialogs.pyc", line 5065, in saveToFile
ValueError: unsupported format character '_' (0x5f) at index 10
2017-05-09 23:22 (ERROR) -- Traceback (most recent call last):
File "qtdialogs.pyc", line 5092, in reject
File "qtdialogs.pyc", line 5081, in cleanup
AttributeError: 'NoneType' object has no attribute 'binPrivKey32_Plain'
2017-05-09 23:22 (ERROR) -- Traceback (most recent call last):
File "qtdialogs.pyc", line 5092, in reject
File "qtdialogs.pyc", line 5081, in cleanup
AttributeError: 'NoneType' object has no attribute 'binPrivKey32_Plain'
2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:25 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
2017-05-09 23:26 (ERROR) -- Traceback (most recent call last):
File "ui\WalletFrames.pyc", line 593, in cardClicked
TypeError: unsupported operand type(s) for %: 'QString' and 'int'
Compressed public keys, never said anything about compressed private keys Any chance that import of private keys will be supported too in the future? Today this happened: ArmoryQT,exe has stoppen working dblog.txt: Log file opened at 1494434109: C:\Users\jeff\AppData\Roaming\Armory\dbLog.txt
-INFO - 1494434109: (..\main.cpp:23) Running on 4 threads
-INFO - 1494434109: (..\main.cpp:24) Ram usage level: 4
-INFO - 1494434109: (..\BlockUtils.cpp:907) blkfile dir: C:\Users\jeff\AppData\Roaming\Bitcoin\blocks
-INFO - 1494434109: (..\BlockUtils.cpp:908) lmdb dir: C:\Users\jeff\AppData\Roaming\Armory\databases
-INFO - 1494434109: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1494434111: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO - 1494434111: (..\BDM_Server.cpp:996) registered bdv: eb0a1e06064ffaddef7b
-INFO - 1494434113: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO - 1494434113: (..\DatabaseBuilder.cpp:169) Reading headers from db
-WARN - 1494434114: (..\BDM_supportClasses.cpp:1891) running 0 zc parser threads
-WARN - 1494434114: (..\BDM_supportClasses.cpp:1891) running 5 zc parser threads
-WARN - 1494434114: (..\BDM_supportClasses.cpp:1891) running 10 zc parser threads
-WARN - 1494434114: (..\BDM_supportClasses.cpp:1891) running 15 zc parser threads
-WARN - 1494434114: (..\BDM_supportClasses.cpp:1891) running 20 zc parser threads
-WARN - 1494434114: (..\BDM_supportClasses.cpp:1891) running 25 zc parser threads
-WARN - 1494434114: (..\BDM_supportClasses.cpp:1891) running 30 zc parser threads
-INFO - 1494434120: (..\DatabaseBuilder.cpp:208) Found 465669 headers in db
-INFO - 1494434123: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1494434123: (..\DatabaseBuilder.cpp:477) Found next block after skipping 508317bytes
-INFO - 1494434124: (..\DatabaseBuilder.cpp:268) parsed block file #862
-INFO - 1494434125: (..\DatabaseBuilder.cpp:268) parsed block file #863
-DEBUG - 1494434125: (..\Blockchain.cpp:242) Organizing chain
-INFO - 1494434125: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 2.139s
-INFO - 1494434125: (..\DatabaseBuilder.cpp:106) scanning new blocks from #465668 to #465771
-INFO - 1494434125: (..\BlockchainScanner.cpp:650) scanned from height #465668 to #465771
-INFO - 1494434125: (..\BlockchainScanner.cpp:225) scanned transaction history in 0.382s
-INFO - 1494434125: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.419s
-INFO - 1494434125: (..\DatabaseBuilder.cpp:160) init db in 12.574s
-INFO - 1494434125: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking
-INFO - 1494434245: (..\BDM_Server.cpp:1025) unregistered bdv: eb0a1e06064ffaddef7b
after restart: Hung on: Preparing Databases Unsure if it was the same error as previous start Log file opened at 1494434426: C:\Users\jeff\AppData\Roaming\Armory\dbLog.txt
-INFO - 1494434426: (..\main.cpp:23) Running on 4 threads
-INFO - 1494434426: (..\main.cpp:24) Ram usage level: 4
-INFO - 1494434426: (..\BlockUtils.cpp:907) blkfile dir: C:\Users\jeff\AppData\Roaming\Bitcoin\blocks
-INFO - 1494434426: (..\BlockUtils.cpp:908) lmdb dir: C:\Users\jeff\AppData\Roaming\Armory\databases
-INFO - 1494434426: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1494434427: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO - 1494434428: (..\BDM_Server.cpp:996) registered bdv: 756b7c3b483e1b28a8b8
-WARN - 1494434429: (..\BDM_supportClasses.cpp:1891) running 0 zc parser threads
-WARN - 1494434429: (..\BDM_supportClasses.cpp:1891) running 5 zc parser threads
-WARN - 1494434429: (..\BDM_supportClasses.cpp:1891) running 10 zc parser threads
-WARN - 1494434429: (..\BDM_supportClasses.cpp:1891) running 15 zc parser threads
-WARN - 1494434429: (..\BDM_supportClasses.cpp:1891) running 20 zc parser threads
-WARN - 1494434429: (..\BDM_supportClasses.cpp:1891) running 25 zc parser threads
-INFO - 1494434429: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO - 1494434430: (..\DatabaseBuilder.cpp:169) Reading headers from db
-INFO - 1494434433: (..\DatabaseBuilder.cpp:208) Found 465773 headers in db
-INFO - 1494434436: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1494434436: (..\DatabaseBuilder.cpp:477) Found next block after skipping 170595bytes
-INFO - 1494434437: (..\DatabaseBuilder.cpp:268) parsed block file #863
-DEBUG - 1494434437: (..\Blockchain.cpp:242) Organizing chain
-INFO - 1494434437: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 0.682s
-INFO - 1494434437: (..\DatabaseBuilder.cpp:106) scanning new blocks from #465772 to #465771
-INFO - 1494434437: (..\BlockchainScanner.cpp:52) no history to scan
-INFO - 1494434437: (..\BlockchainScanner.cpp:813) no SSH to scan
-INFO - 1494434437: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.014s
-INFO - 1494434437: (..\DatabaseBuilder.cpp:160) init db in 7.691s
-INFO - 1494434437: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking
-WARN - 1494434438: (..\BDM_supportClasses.cpp:1891) running 35 zc parser threads
-INFO - 1494434557: (..\BDM_Server.cpp:1025) unregistered bdv: 756b7c3b483e1b28a8b8
armorylog.txt Just the part of the last start. Some parts are censored by replacing them with ###CENSORED### 2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1138 - C++ block utilities loaded successfully
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1255 -
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1256 -
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1257 -
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1258 - ************************************************************
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1259 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1260 - ************************************************************
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1261 - Loading Armory Engine:
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1262 - Armory Version : 0.96
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1263 - Armory Build: : a3d01aa722
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1264 - PyBtcWallet Version : 1.35
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1265 - Detected Operating system: Windows
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1266 - OS Variant : 7-6.1.7601-SP1-Multiprocessor Free
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1267 - User home-directory : C:\Users\jeff\AppData\Roaming
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1268 - Satoshi BTC directory : C:\Users\jeff\AppData\Roaming\Bitcoin\
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1269 - Armory home dir : C:\Users\jeff\AppData\Roaming\Armory\
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1270 - Detected System Specs :
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1271 - Total Available RAM : 15.91 GB
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1272 - CPU ID string : Intel64 Family 6 Model 58 Stepping 9, GenuineIntel
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1273 - Number of CPU cores : 4 cores
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1274 - System is 64-bit : True
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1275 - Preferred Encoding : cp1252
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1276 - Machine Arch : amd64
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1277 - Available HDD (ARM) : 425 GB
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1278 - Available HDD (BTC) : 425 GB
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1279 -
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1280 - Network Name: Main Network
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1281 - Satoshi Port: 8333
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1282 - Do wlt check: True
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1283 - Named options/arguments to armoryengine.py:
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - thread_count : -1
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - rescan : False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - ignoreAllZC : False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - rescanBalance : False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - disableModules : False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - port : None
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - interport : 8223
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - coverageOutputDir: None
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - forceWalletCheck: False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - regtest : False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - rebuild : False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - nettimeout : 2
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - datadir : DEFAULT
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - clearMempool : False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - offline : False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - armoryDBDir : DEFAULT
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - armorydb_port : 9001
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - satoshiPort : DEFAULT
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - useTorSettings : False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - netlog : False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - keypool : 100
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - coverageInclude : None
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - forceOnline : False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - redownload : False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - rpcBindAddr : 127.0.0.1
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - armorydb_ip : 127.0.0.1
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - multisigFile : DEFAULT
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - ram_usage : -1
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - mtdebug : False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - logDisable : False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - settingsPath : C:\Users\jeff\AppData\Roaming\Armory\ArmorySettings.txt
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - language : en
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - db_type : DB_FULL
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - doDebug : False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - enableDetSign : True
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - disableConfPermis: False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - testnet : False
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - rpcport : DEFAULT
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - satoshiHome : DEFAULT
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - satoshiRpcport : DEFAULT
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - logFile : C:\Users\jeff\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1285 - verbosity : None
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1286 - Other arguments:
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1289 - ************************************************************
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:1692 - C++ block utilities loaded successfully
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:3590 - Using settings file: C:\Users\jeff\AppData\Roaming\Armory\ArmorySettings.txt
2017-05-10 18:40 (ERROR) -- ArmoryUtils.pyc:3747 - Unsupported language specified. Defaulting to English (en)
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:3750 - Using Language: en
2017-05-10 18:40 (INFO) -- BDM.pyc:368 - Using the asynchronous/multi-threaded BlockDataManager.
2017-05-10 18:40 (INFO) -- BDM.pyc:369 - Blockchain operations will happen in the background.
2017-05-10 18:40 (INFO) -- BDM.pyc:370 - Devs: check TheBDM.getState() before asking for data.
2017-05-10 18:40 (INFO) -- BDM.pyc:371 - Registering addresses during rescans will queue them for
2017-05-10 18:40 (INFO) -- BDM.pyc:372 - inclusion after the current scan is completed.
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:3590 - Using settings file: C:\Users\jeff\AppData\Roaming\Armory\ArmorySettings.txt
2017-05-10 18:40 (INFO) -- ArmoryQt.py:2042 - loadWalletsAndSettings
2017-05-10 18:40 (INFO) -- ArmoryQt.py:2102 - Loading wallets...
2017-05-10 18:40 (WARNING) -- ArmoryQt.py:2129 - ***WARNING: Duplicate wallet detected, ###CENSORED###
2017-05-10 18:40 (WARNING) -- ArmoryQt.py:2140 - Second wallet is more useful than the first one...
2017-05-10 18:40 (WARNING) -- ArmoryQt.py:2141 - Wallet 1 (skipped): C:\Users\jeff\AppData\Roaming\Armory\armory_###CENSORED###__WatchOnly.wallet
2017-05-10 18:40 (WARNING) -- ArmoryQt.py:2142 - Wallet 2 (loaded): C:\Users\jeff\AppData\Roaming\Armory\armory_###CENSORED###_.wallet
2017-05-10 18:40 (WARNING) -- ArmoryQt.py:2129 - ***WARNING: Duplicate wallet detected, ###CENSORED###
2017-05-10 18:40 (WARNING) -- ArmoryQt.py:2140 - Second wallet is more useful than the first one...
2017-05-10 18:40 (WARNING) -- ArmoryQt.py:2141 - Wallet 1 (skipped): C:\Users\jeff\AppData\Roaming\Armory\armory_###CENSORED###__WatchOnly.wallet
2017-05-10 18:40 (WARNING) -- ArmoryQt.py:2142 - Wallet 2 (loaded): C:\Users\jeff\AppData\Roaming\Armory\armory_###CENSORED###_.wallet
2017-05-10 18:40 (INFO) -- ArmoryQt.py:2167 - Number of wallets read in: 8
2017-05-10 18:40 (INFO) -- ArmoryQt.py:2172 - Wallet ###CENSORED###" (Encrypted)
2017-05-10 18:40 (INFO) -- ArmoryQt.py:2172 - Wallet ###CENSORED###" (Encrypted)
2017-05-10 18:40 (INFO) -- ArmoryQt.py:2172 - Wallet ###CENSORED###" (No Encryption)
2017-05-10 18:40 (INFO) -- ArmoryQt.py:2172 - Wallet ###CENSORED###" (Encrypted)
2017-05-10 18:40 (INFO) -- ArmoryQt.py:2172 - Wallet ###CENSORED###" (Encrypted)
2017-05-10 18:40 (INFO) -- ArmoryQt.py:2172 - Wallet ###CENSORED###" (Encrypted)
2017-05-10 18:40 (INFO) -- ArmoryQt.py:2172 - Wallet ###CENSORED###" (No Encryption)
2017-05-10 18:40 (INFO) -- ArmoryQt.py:2172 - Wallet ###CENSORED###" (Encrypted)
2017-05-10 18:40 (INFO) -- ArmoryQt.py:2177 - Loading Multisig Lockboxes
2017-05-10 18:40 (INFO) -- ArmoryQt.py:1747 - acquiring process mutex...
2017-05-10 18:40 (INFO) -- ArmoryQt.py:1385 - setupUriRegistration
2017-05-10 18:40 (INFO) -- ArmoryQt.py:1503 - URL-register action: AskUser
2017-05-10 18:40 (INFO) -- ArmoryQt.py:558 - Usermode: Expert
2017-05-10 18:40 (INFO) -- ArmoryQt.py:1681 - Changing usermode:
2017-05-10 18:40 (INFO) -- ArmoryQt.py:1682 - From: Expert
2017-05-10 18:40 (INFO) -- ArmoryQt.py:1690 - To: Expert
2017-05-10 18:40 (INFO) -- ArmoryQt.py:1814 - startBitcoindIfNecessary
2017-05-10 18:40 (INFO) -- ArmoryQt.py:1850 - setSatoshiPaths
2017-05-10 18:40 (WARNING) -- SDM.pyc:396 - Spawning DB with command:./ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="C:\Users\jeff\AppData\Roaming\Bitcoin\blocks" --datadir="C:\Users\jeff\AppData\Roaming\Armory\" --dbdir="C:\Users\jeff\AppData\Roaming\Armory\databases"
2017-05-10 18:40 (INFO) -- ArmoryUtils.pyc:665 - Executing popen: ['./ArmoryDB.exe', '--db-type="DB_FULL"', '--cookie', u'--satoshi-datadir="C:\\Users\\jeff\\AppData\\Roaming\\Bitcoin\\blocks"', u'--datadir="C:\\Users\\jeff\\AppData\\Roaming\\Armory\\"', u'--dbdir="C:\\Users\\jeff\\AppData\\Roaming\\Armory\\databases"']
2017-05-10 18:40 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-05-10 18:40 (INFO) -- ArmoryQt.py:1882 - loadBlockchainIfNecessary
2017-05-10 18:40 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:40 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:41 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-10 18:42 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
After restart: same problem Restarting BitcoinCore before this restart did not solve it. I re-installed 0.95.1 because rebuilding the Armory database every day is annoying. * I had created a backup of my 0.95.1 wallets before I upgraded to 0.96 * Removing all wallet-files of 0.96 * Restoring all wallet-files of 0.95.1 * emptying %appdata%\Armory\databases * Installing 0.95.1 over 0.96 0.95.1 is running fine now.  |
|
|
|
|
9
|
Bitcoin / Armory / Re: Armory 0.96 is out
|
on: May 09, 2017, 10:26:34 PM
|
I just upgraded Bitcoin Core and Armory. Here are the notes I made of my first experiences after the upgrade. Windows 7 64bit Updated Bitcoin Core from 0.14.0 to 0.14.1 Updated Armory from 0.95.1 to 0.96 Armory crashed every time after scanning. Emptied %appdata%\Armory\databases , causing Armory to rebuild the database solved this problem. btw: Amazing that this is the only piece of software that manages to fully use my 16 GB RAM while rebuilding the database. No problem for me. Errormesage from tray-icon after starting Armory about the connection being lost to BitcoinCore while that is not really so. I am running BitcoinCore continuously in the background, regardless of Armory running or not. The CMD-window is still always visible. Problem: Saving/Backing up a wallet unencrypted to a file does not work. "Save to File" I want to use it to backup the private keys to another encrypted medium. CTRL-C and -V would work, but that is annoying after a while. Compressed keys: MultiBit Classis private keys are not accepted at Private Key Import: No valid private key data was entered. https://bitcointalk.org/index.php?topic=175389.msg14100768#msg14100768Wallet properties: Used addresses: Addresses not visible. Unsure after which this happens. Solved after restarting Armory. Address Book: changed Comment, but it does not stick. Or on the other hand: The comment for an address changed in the wallet does not display in the addressbook. After doing one transaction, and restarting Armory: Does not fully start. Solved by restarting BitcoinCore before starting Armory. dblog.txt: Log file opened at 1494367860: C:\Users\jeff\AppData\Roaming\Armory\dbLog.txt
-INFO - 1494367860: (..\main.cpp:23) Running on 4 threads
-INFO - 1494367860: (..\main.cpp:24) Ram usage level: 4
-INFO - 1494367860: (..\BlockUtils.cpp:907) blkfile dir: C:\Users\jeff\AppData\Roaming\Bitcoin\blocks
-INFO - 1494367860: (..\BlockUtils.cpp:908) lmdb dir: C:\Users\jeff\AppData\Roaming\Armory\databases
-INFO - 1494367860: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1494367860: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO - 1494367862: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO - 1494367863: (..\DatabaseBuilder.cpp:169) Reading headers from db
-WARN - 1494367865: (..\BDM_supportClasses.cpp:1891) running 0 zc parser threads
-WARN - 1494367865: (..\BDM_supportClasses.cpp:1891) running 5 zc parser threads
-WARN - 1494367865: (..\BDM_supportClasses.cpp:1891) running 10 zc parser threads
-INFO - 1494367866: (..\DatabaseBuilder.cpp:208) Found 465669 headers in db
-INFO - 1494367868: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1494367868: (..\DatabaseBuilder.cpp:477) Found next block after skipping 508317bytes
-INFO - 1494367869: (..\DatabaseBuilder.cpp:268) parsed block file #862
-DEBUG - 1494367869: (..\Blockchain.cpp:242) Organizing chain
-INFO - 1494367869: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 0.491s
-INFO - 1494367869: (..\DatabaseBuilder.cpp:106) scanning new blocks from #465668 to #465667
-INFO - 1494367869: (..\BlockchainScanner.cpp:52) no history to scan
-INFO - 1494367869: (..\BlockchainScanner.cpp:813) no SSH to scan
-INFO - 1494367869: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.009s
-INFO - 1494367869: (..\DatabaseBuilder.cpp:160) init db in 6.281s
-INFO - 1494367869: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking
-WARN - 1494367875: (..\BDM_supportClasses.cpp:1891) running 20 zc parser threads
-WARN - 1494367875: (..\BDM_supportClasses.cpp:1891) running 25 zc parser threads
-WARN - 1494367875: (..\BDM_supportClasses.cpp:1891) running 30 zc parser threads
-WARN - 1494367875: (..\BDM_supportClasses.cpp:1891) running 35 zc parser threads
successful start and shutdown after previous mentioned problem: Log file opened at 1494368069: C:\Users\jeff\AppData\Roaming\Armory\dbLog.txt
-INFO - 1494368069: (..\main.cpp:23) Running on 4 threads
-INFO - 1494368069: (..\main.cpp:24) Ram usage level: 4
-INFO - 1494368069: (..\BlockUtils.cpp:907) blkfile dir: C:\Users\jeff\AppData\Roaming\Bitcoin\blocks
-INFO - 1494368069: (..\BlockUtils.cpp:908) lmdb dir: C:\Users\jeff\AppData\Roaming\Armory\databases
-INFO - 1494368069: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1494368070: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO - 1494368071: (..\BDM_Server.cpp:996) registered bdv: eb311f97a355b2f2dd5a
-INFO - 1494368072: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO - 1494368073: (..\DatabaseBuilder.cpp:169) Reading headers from db
-INFO - 1494368076: (..\DatabaseBuilder.cpp:208) Found 465669 headers in db
-INFO - 1494368079: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1494368079: (..\DatabaseBuilder.cpp:477) Found next block after skipping 508317bytes
-INFO - 1494368079: (..\DatabaseBuilder.cpp:268) parsed block file #862
-DEBUG - 1494368079: (..\Blockchain.cpp:242) Organizing chain
-INFO - 1494368079: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 0.726s
-INFO - 1494368079: (..\DatabaseBuilder.cpp:106) scanning new blocks from #465668 to #465667
-INFO - 1494368079: (..\BlockchainScanner.cpp:52) no history to scan
-INFO - 1494368079: (..\BlockchainScanner.cpp:813) no SSH to scan
-INFO - 1494368079: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.015s
-INFO - 1494368079: (..\DatabaseBuilder.cpp:160) init db in 7.121s
-INFO - 1494368079: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking
-WARN - 1494368102: (..\BDM_supportClasses.cpp:1891) running 10 zc parser threads
-WARN - 1494368102: (..\BDM_supportClasses.cpp:1891) running 15 zc parser threads
-WARN - 1494368102: (..\BDM_supportClasses.cpp:1891) running 20 zc parser threads
-WARN - 1494368102: (..\BDM_supportClasses.cpp:1891) running 25 zc parser threads
-WARN - 1494368109: (..\BDM_supportClasses.cpp:1891) running 30 zc parser threads
-WARN - 1494368109: (..\BDM_supportClasses.cpp:1891) running 35 zc parser threads
-WARN - 1494368110: (..\BDM_supportClasses.cpp:1891) running 40 zc parser threads
-WARN - 1494368110: (..\BDM_supportClasses.cpp:1891) running 45 zc parser threads
-WARN - 1494368110: (..\BDM_supportClasses.cpp:1891) running 50 zc parser threads
-WARN - 1494368110: (..\BDM_supportClasses.cpp:1891) running 55 zc parser threads
-WARN - 1494368110: (..\BDM_supportClasses.cpp:1891) running 60 zc parser threads
-WARN - 1494368110: (..\BDM_supportClasses.cpp:1891) running 65 zc parser threads
-WARN - 1494368110: (..\BDM_supportClasses.cpp:1891) running 70 zc parser threads
-INFO - 1494368200: (..\BDM_Server.cpp:1025) unregistered bdv: eb311f97a355b2f2dd5a
-INFO - 1494368200: (..\BDM_Server.cpp:936) proceeding to shutdown
-ERROR - 1494368200: (..\BitcoinP2P.cpp:1027) caught SocketError exception in processDataStackThread: POLLNVAL in readFromSocketThread
-INFO - 1494368200: (..\BitcoinP2P.cpp:969) Disconnected from Bitcoin node
-ERROR - 1494368202: (..\BDM_mainthread.cpp:286) caught exception in main thread: terminate
|
|
|
|
|
10
|
Bitcoin / Armory / Re: Armory 0.95.1 is out
|
on: March 12, 2017, 09:22:59 PM
|
|
FYI:
I have been running BitcoinCore 0.14.0 together with Armory 0.95.1 without any problem on Windows 7 64bit.
|
|
|
|
|
11
|
Bitcoin / Mining / Re: いい gekkorun.de - Gekkoscience Fun-Run - compare your share いい
|
on: December 07, 2016, 09:00:19 PM
|
Well I moved up one spot, 2nd to last now hehe.
Congrats to edonkey on the 3rd highest share to date since we started this fun run.
And I dunno how I missed the 1.15G share by JeffZwolle or when he pulled that one out, but that's one of only a handful of >1G shares I know of from these sticks, nice one!
Thanks! I saw that one of my sticks was in first place yesterday, but the forum was down. I guess that large share (relatively speaking) will keep me in first for while, probably until the solo pool finds another block and resets everything. I'll enjoy it while I can  Yeah, I saw that huge share by JeffZwolle before. Incredible. Probably none of us will ever beat that... I even got a bigger share than that 1.15G. 8.83G But I was mining to another address at that time. Same Gekko Stick though.  That share of 5.85G by zOU 2 is amazing too. |
|
|
|
|
12
|
Bitcoin / Armory / Re: Failed import of private key
|
on: November 14, 2016, 05:37:13 PM
|
|
Ok, thank you.
I think I will try to do a fresh test project on github in the future, just to find out how it all functions.
I don't want to mess up your project.
|
|
|
|
|
13
|
Bitcoin / Armory / Re: Failed import of private key
|
on: November 13, 2016, 02:51:08 PM
|
Pull request. The website is open source, the code is available on the gh-pages branch. If you write a patch to modify the page and PR it, I will review it and merge.
So a person has to have experience in developing to be able to have something added to a To Do list? Why? The majority of Bitcoin-clients accepts compressed keys, while Armory does not. I have no experience in doing a PR. Can you or somebody else please add this item to the To Do list? |
|
|
|
|
16
|
Bitcoin / Hardware / Re: GekkoScience Compac BM1384 Stickminer Official Support Thread
|
on: July 20, 2016, 09:15:03 PM
|
I like the little fan mount, cool idea. You could probably even get 2 of them on there and then cover the entire heat sink. Do you have a laser thermometer? Would be interesting to see what the temp difference is on the heat sink beneath the fan and on the sides.
Yes, I do have one of those. temperatures: Room: 30 degr C Heatsink side: 40 degr C Fan top: 41 degr C Heatsink under fan: 61 degr C Room temperature is pretty high because of outside temperature being 34 degr C here today. |
|
|
|
|
