Latest posts of: creamers

Show Posts
Pages: [1] 2 3 »

Bitcoin / Armory / Re: 0.96.1 testing build #4

on: July 17, 2017, 08:39:08 PM

You can see it in the picture.....typed 200, but it only says 20. As soon as I type anything <=197 is shows the correct value, otherwise like in the picture. *edit I see that it didnt max the spendable amount cause I edited the fee. The button should be pressed automatically again when the fee is changed imo

Bitcoin / Armory / Re: 0.96.1 testing build #4

on: July 17, 2017, 06:40:37 PM

While trying to create a unsigned transaction I notice this: https://www.screencast.com/t/2hhmT0R9o Fee rate per node is set to 197 sat/byte and it gave me a warning, so I wanted to change this and set it to Fee/Byte (Satoshi/Byte) and wanted to set it to 200. Now it seems that it doesnt change as soon as I go above 197 in the Fee/Byte field. (In above movie is recorded) Is this a bug or why can't I set a higher "Fee/Byte" than the current "Fee Rate per Node" ?

Bitcoin / Armory / Re: 0.96.1 testing build #3

on: July 10, 2017, 05:59:44 AM

Quote from: creamers on June 16, 2017, 04:54:52 PM oke, will have to wait for the build to test it out. *EDIT: since I started without the bitcoind and with bitcoin core in the foreground it runs without crashes. Since build #4 it is running stable again with bitcoind in the background. Thank you for your effort!

Alternate cryptocurrencies / Altcoin Discussion / Re: EOS hardcore scam - renamed BitShares - You will NOT like this?

on: July 03, 2017, 09:06:50 PM

LOL , listen and read up, it does use some tech from bitshares and steem.....

Bitcoin / Armory / Re: different blocks between bitcoin core and armory

on: June 18, 2017, 06:15:55 PM

This latest problem is noticed here and probably solved in test version 4. https://bitcointalk.org/index.php?topic=1917955.msg19593847#msg19593847 (This thread can be closed)

Bitcoin / Armory / Re: Armory

on: June 18, 2017, 05:58:25 PM

One extra tip for this "0.96.1 testing build #3" version that you are gonna use if you experience crashes: 3B: First start bitcoin core and let it sync up, then start armory with the bitcoin core still running as client.

Bitcoin / Armory / Re: 0.96.1 testing build #3

on: June 16, 2017, 04:54:52 PM

oke, will have to wait for the build to test it out. *EDIT: since I started without the bitcoind and with bitcoin core in the foreground it runs without crashes.

Bitcoin / Armory / Re: 0.96.1 testing build #3

on: June 16, 2017, 10:30:43 AM

and again: Cleared the logs first and started armory...I just let it run (with bitcoind in background) and it crashed: dblog: https://pastebin.com/cfNL4WBM armorylog: https://pastebin.com/ixRCKe2t

Bitcoin / Armory / Re: 0.96.1 testing build #3

on: June 15, 2017, 08:00:57 PM

Quote from: goatpig on June 14, 2017, 09:55:34 PM Code: running 2340 zc parser threads This is a relevant symptom. How large is your node's mempool? Anything worth of note getting to that point? Let the Armory run for a few hours, does it get to that point? Taskmanager: It's running fine untill it crashes. .2 test version didnt do that. Cleared the log files and started it again. Here they are: armory log: https://pastebin.com/TiWpt0yr dblog: https://pastebin.com/DFJ7TrBc Quote from: goatpig on June 14, 2017, 09:55:34 PM Which one is it? WO's can be considered your wallet as long as you specify that in the ownership field. They are not by default however. Let me rephrase, I have two wallets, one mine and one not mine. When I start armory the filter is default to MyWallets setting but it's showing ALL wallets until I change something in the comments fields, then it will show only My Wallets and thus showing one wallet in my case. (If armory start defaulting to My Wallets then it should only show my wallets and not all of them.)

Bitcoin / Armory / Re: 0.96.1 testing build #3

on: June 14, 2017, 06:35:06 PM

see previous post about Filter.

Now about the crashes...it seems to crash while it was running oke....now happened several times.

Code:

2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1135 - C++ block utilities loaded successfully
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1252 - 
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1253 - 
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1254 - 
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1255 - ************************************************************
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1256 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe --datadir=c:\Armory Database --satoshi-datadir=c:\Bitcoin Core Database
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1257 - ************************************************************
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1258 - Loading Armory Engine:
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1259 -    Armory Version        : 0.96.0.3
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1260 -    Armory Build:         : 1a126dd6ec
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1261 -    PyBtcWallet  Version  : 1.35
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1262 - Detected Operating system: Windows
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1263 -    OS Variant            : 2008ServerR2-6.1.7601-SP1-Multiprocessor Free
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1264 -    User home-directory   : C:\Users\Administrator\AppData\Roaming
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1265 -    Satoshi BTC directory : c:\Bitcoin Core Database
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1266 -    Armory home dir       : c:\Armory Database
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1267 - Detected System Specs    : 
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1268 -    Total Available RAM   : 3.87 GB
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1269 -    CPU ID string         : AMD64 Family 16 Model 6 Stepping 3, AuthenticAMD
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1270 -    Number of CPU cores   : 2 cores
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1271 -    System is 64-bit      : True
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1272 -    Preferred Encoding    : cp1252
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1273 -    Machine Arch          : amd64
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1274 -    Available HDD (ARM)   : 657 GB
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1275 -    Available HDD (BTC)   : 657 GB
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1276 - 
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1277 - Network Name: Main Network
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1278 - Satoshi Port: 8333
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1279 - Do wlt check: True
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1280 - Named options/arguments to armoryengine.py:
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     thread_count    : -1
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     rescan          : False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     ignoreAllZC     : False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     rescanBalance   : False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     disableModules  : False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     port            : None
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     interport       : 8223
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     coverageOutputDir: None
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     forceWalletCheck: False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     regtest         : False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     rebuild         : False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     nettimeout      : 2
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     datadir         : c:\Armory Database
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     clearMempool    : False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     offline         : False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     armoryDBDir     : DEFAULT
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     armorydb_port   : 9001
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     satoshiPort     : DEFAULT
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     useTorSettings  : False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     netlog          : False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     keypool         : 100
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     coverageInclude : None
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     forceOnline     : False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     redownload      : False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     rpcBindAddr     : 127.0.0.1
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     armorydb_ip     : 127.0.0.1
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     multisigFile    : DEFAULT
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     ram_usage       : -1
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     mtdebug         : False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     logDisable      : False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     settingsPath    : c:\Armory Database\ArmorySettings.txt
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     language        : en
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     db_type         : DB_FULL
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     doDebug         : False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     enableDetSign   : True
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     disableConfPermis: False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     testnet         : False
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     rpcport         : DEFAULT
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     satoshiHome     : c:\Bitcoin Core Database
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     satoshiRpcport  : DEFAULT
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     logFile         : c:\Armory Database\ArmoryQt.exe.log.txt
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1282 -     verbosity       : None
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1283 - Other arguments:
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1286 - ************************************************************
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:1689 - C++ block utilities loaded successfully
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:3587 - Using settings file: c:\Armory Database\ArmorySettings.txt
2017-06-14 19:53:13 (ERROR) -- ArmoryUtils.pyc:3744 - Unsupported language  specified. Defaulting to English (en)
2017-06-14 19:53:13 (INFO) -- ArmoryUtils.pyc:3747 - Using Language: en
2017-06-14 19:53:13 (INFO) -- BDM.pyc:365 - Using the asynchronous/multi-threaded BlockDataManager.
2017-06-14 19:53:13 (INFO) -- BDM.pyc:366 - Blockchain operations will happen in the background.  
2017-06-14 19:53:13 (INFO) -- BDM.pyc:367 - Devs: check TheBDM.getState() before asking for data.
2017-06-14 19:53:13 (INFO) -- BDM.pyc:368 - Registering addresses during rescans will queue them for 
2017-06-14 19:53:13 (INFO) -- BDM.pyc:369 - inclusion after the current scan is completed.
2017-06-14 19:53:14 (INFO) -- ArmoryUtils.pyc:3587 - Using settings file: c:\Armory Database\ArmorySettings.txt
2017-06-14 19:53:14 (INFO) -- ArmoryQt.py:2045 - loadWalletsAndSettings
2017-06-14 19:53:14 (INFO) -- ArmoryQt.py:2105 - Loading wallets...
2017-06-14 19:53:16 (INFO) -- ArmoryQt.py:2170 - Number of wallets read in: 2
2017-06-14 19:53:16 (INFO) -- ArmoryQt.py:2175 -    Wallet (7GuJwatF):    "BurtsWallet (Watch)             "   (No Encryption)
2017-06-14 19:53:16 (INFO) -- ArmoryQt.py:2175 -    Wallet (DW1EHSXZ):    "Restored - DW1EHSXZ             "   (Encrypted)
2017-06-14 19:53:16 (INFO) -- ArmoryQt.py:1747 - acquiring process mutex...
2017-06-14 19:53:17 (INFO) -- ArmoryQt.py:1386 - setupUriRegistration
2017-06-14 19:53:17 (INFO) -- ArmoryQt.py:1454 - Armory already registered for current user.  Done!
2017-06-14 19:53:17 (INFO) -- ArmoryQt.py:560 - Usermode: Advanced
2017-06-14 19:53:17 (INFO) -- ArmoryQt.py:1682 - Changing usermode:
2017-06-14 19:53:17 (INFO) -- ArmoryQt.py:1683 -    From: Advanced
2017-06-14 19:53:17 (INFO) -- ArmoryQt.py:1691 -      To: Advanced
2017-06-14 19:53:17 (INFO) -- ArmoryQt.py:1820 - startBitcoindIfNecessary
2017-06-14 19:53:17 (INFO) -- ArmoryQt.py:1856 - setSatoshiPaths
2017-06-14 19:53:17 (INFO) -- SDM.pyc:251 - Found Bitcoin Core link on desktop: C:\Program Files\Bitcoin
2017-06-14 19:53:17 (INFO) -- SDM.pyc:251 - Found Bitcoin Core link on desktop: C:\Program Files\Bitcoin
2017-06-14 19:53:17 (INFO) -- SDM.pyc:169 - Found bitcoind in the following places:
2017-06-14 19:53:17 (INFO) -- SDM.pyc:171 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-06-14 19:53:17 (INFO) -- SDM.pyc:171 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-06-14 19:53:17 (INFO) -- SDM.pyc:171 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-06-14 19:53:17 (INFO) -- SDM.pyc:173 - Using: C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-06-14 19:53:17 (INFO) -- SDM.pyc:337 - Called startBitcoind
2017-06-14 19:53:18 (INFO) -- ArmoryUtils.pyc:664 - Executing popen: ['C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=c:\\Bitcoin Core Database']
2017-06-14 19:53:18 (INFO) -- SDM.pyc:442 - PID of bitcoind: 17984
2017-06-14 19:53:18 (INFO) -- SDM.pyc:443 - PID of armory:   4924
2017-06-14 19:53:18 (INFO) -- ArmoryUtils.pyc:664 - Executing popen: ['.\\guardian.exe', '4924', '17984']
2017-06-14 19:53:21 (INFO) -- ArmoryQt.py:1856 - setSatoshiPaths
2017-06-14 19:53:21 (WARNING) -- SDM.pyc:395 - Spawning DB with command:./ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="c:\Bitcoin Core Database\blocks" --datadir="c:\Armory Database" --dbdir="c:\Armory Database\databases"
2017-06-14 19:53:21 (INFO) -- ArmoryUtils.pyc:664 - Executing popen: ['./ArmoryDB.exe', '--db-type="DB_FULL"', '--cookie', u'--satoshi-datadir="c:\\Bitcoin Core Database\\blocks"', '--datadir="c:\\Armory Database"', u'--dbdir="c:\\Armory Database\\databases"']
2017-06-14 19:53:23 (INFO) -- ArmoryQt.py:1808 - Connecting on port 50655
2017-06-14 19:53:23 (INFO) -- ArmoryQt.py:1908 - Setting netmode: 1
2017-06-14 19:53:24 (INFO) -- ArmoryQt.py:1890 - loadBlockchainIfNecessary
2017-06-14 19:53:25 (INFO) -- ArmoryQt.py:1908 - Setting netmode: 1
2017-06-14 19:53:25 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-06-14 19:53:25 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-06-14 19:53:25 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-06-14 19:53:25 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-06-14 19:53:26 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-06-14 19:53:27 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-06-14 19:53:28 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-06-14 19:53:29 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-06-14 19:53:30 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-06-14 19:53:31 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-06-14 19:53:32 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-06-14 19:53:33 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-06-14 19:53:45 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-06-14 19:53:48 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-06-14 19:53:48 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-06-14 19:53:49 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-06-14 19:53:49 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-06-14 19:54:15 (WARNING) -- ArmoryQt.py:4078 - Called updateSyncProgress while not sync'ing
2017-06-14 20:00:38 (INFO) -- ArmoryQt.py:4914 - New Block! : 471263
2017-06-14 20:00:38 (INFO) -- ArmoryQt.py:4922 - Current block number: 471263
2017-06-14 20:13:33 (INFO) -- ArmoryQt.py:4914 - New Block! : 471264
2017-06-14 20:13:33 (INFO) -- ArmoryQt.py:4922 - Current block number: 471264
2017-06-14 20:19:23 (INFO) -- ArmoryQt.py:4914 - New Block! : 471265
2017-06-14 20:19:23 (INFO) -- ArmoryQt.py:4922 - Current block number: 471265
2017-06-14 20:23:18 (WARNING) -- ArmoryQt.py:4078 - Called updateSyncProgress while not sync'ing

Code:

-WARN  - 20:22:40.241: (..\BDM_supportClasses.cpp:1898) running 2285 zc parser threads
-WARN  - 20:22:40.241: (..\BDM_supportClasses.cpp:1898) running 2290 zc parser threads
-WARN  - 20:22:53.924: (..\BDM_supportClasses.cpp:1898) running 2295 zc parser threads
-WARN  - 20:22:53.924: (..\BDM_supportClasses.cpp:1898) running 2300 zc parser threads
-WARN  - 20:22:53.939: (..\BDM_supportClasses.cpp:1898) running 2305 zc parser threads
-WARN  - 20:22:53.939: (..\BDM_supportClasses.cpp:1898) running 2310 zc parser threads
-WARN  - 20:22:53.955: (..\BDM_supportClasses.cpp:1898) running 2315 zc parser threads
-ERROR - 20:23:18.024: (..\SocketObject.cpp:285--ERROR - 20:23:18.040: (WARN  - ..\SocketObject.cpp:134) POLLERR error in readFromSocketThread
20:23:18.040) POLLERR in writeToSocket
: (..\BDM_supportClasses.cpp:1898) running 2320 zc parser threads
-WARN  - 20:23:18.055: (..\BDM_supportClasses.cpp:1898) running 2325 zc parser threads
-WARN  - 20:23:18.071: (..\BDM_supportClasses.cpp:1898) running 2330 zc parser threads
-WARN  - 20:23:18.071: (..\BDM_supportClasses.cpp:1898) running 2335 zc parser threads
-ERROR - 20:23:18.087: (..\SocketObject.cpp:134) POLLERR in writeToSocket
-ERROR - 20:23:18.087: (..\SocketObject.cpp:126) poll() error in writeToSocket: 10038
-ERROR - 20:23:18.102: (..\SocketObject.cpp:126) poll() error in writeToSocket: 10038
-WARN  - 20:23:18.102: (..\BDM_supportClasses.cpp:1898) running 2340 zc parser threads
-ERROR - 20:23:18.133: (..\SocketObject.cpp:126) poll() error in writeToSocket: 10038
-ERROR - 20:23:18.133: (..\SocketObject.cpp:126) poll() error in writeToSocket: 10038
-WARN  - 20:23:18.149: (..\BDM_supportClasses.cpp-ERROR - :189820:23:18.149: (..\SocketObject.cpp:126) poll() error in writeToSocket: 10038) running 2345
 zc parser threads-ERROR - 
20:23:18.165: (..\SocketObject.cpp:126) poll() error in writeToSocket: 10038
-ERROR - 20:23:18.180: (..\SocketObject.cpp:126-WARN  - ) 20:23:18.196: (..\BDM_supportClasses.cpp:1898poll() error in writeToSocket: 10038
) running 2350 zc parser threads
-ERROR - 20:23:18.196: (..\SocketObject.cpp:126) poll() error in writeToSocket: 10038
-ERROR - 20:23:18.211: (..\SocketObject.cpp:126-ERROR - ) 20:23:18.211: (..\BitcoinP2P.cpp:1027poll() error in writeToSocket: 10038) caught SocketError exception in processDataStackThread: POLLERR error in readFromSocketThread

-ERROR - -INFO  - 20:23:18.227: (..\SocketObject.cpp:12620:23:18.227: (..\BitcoinP2P.cpp:969) ) Disconnected from Bitcoin node
poll() error in writeToSocket: 10038

Bitcoin / Armory / Re: 0.96.1 testing build #3

on: June 14, 2017, 05:57:44 PM

Found the problem. I have two wallets. One watch only wallet en one native wallet. When I open Armory it defaults to "My Wallets" showing both wallets !! (Think this is already wrong as it should not show the WatchOnly wallet.) Changing a comment activates the Filter, meaning, it then becomes active and the WatchOnly wallet disappears because it doesnt belong in the filter view My Wallets. It's either case, the watch only wallet should be visible in 'my wallets' OR the filter should become active at startup and not only when comments are changed. I think it should be set to All Wallets at startup showing all wallets. Problem solved Hope it helps, otherwise let me know. (ps, I noticed alot more crashes at closing but will investigate / narrow it down)

Bitcoin / Armory / Re: 0.96.1 testing build #3

on: June 14, 2017, 04:43:30 PM

Nice! ( https://github.com/goatpig/BitcoinArmory/commit/eb826b671155eb57fe7271c8d140431ebe8b8bbc ) Will test some more. *EDIT First time ~~after installation~~ after every startup and changing the comments it flipped back. The second edit it didnt flip back to my wallet and stayed at all wallets.

Bitcoin / Armory / Re: different blocks between bitcoin core and armory

on: June 13, 2017, 05:58:47 PM

Starting and stopping bitcoind vs manual 10 manual all oke: log https://pastebin.com/K5g6Sux5 dblog: https://pastebin.com/zq35e08c 2/10 gave me an armory Error/Crash , when clicking at the confirming Close button when closing down.: log: https://pastebin.com/eMQsGN26 dblog: https://pastebin.com/iNMpcfia I didnt wait long before starting again. I checked if all processes stopped before starting the cycle over again. Hope it gives you something to work with

Bitcoin / Armory / Re: 0.96.1 testing build #2

on: June 13, 2017, 08:33:27 AM

I cleared the log, then started armory and did what I described earlier. (add a comment and then the filter switches to my wallet when it was set on all wallets) https://pastebin.com/Gxqr5nZ6 I think this is some sort of gui bug thingy ? : http://imgur.com/a/ECgRQ

Bitcoin / Armory / Re: 0.96.1 testing build #2

on: June 12, 2017, 08:41:37 PM

Bug ? I have two wallets, one native and one cold wallet. When Filter is set to "all wallets" and I double click on Comments in that particular colomn, paste the text and press oke , the Filter will jump to My Wallets automatically.... imo it should stay at the same filter settings.

Bitcoin / Armory / Re: different blocks between bitcoin core and armory

on: June 12, 2017, 08:34:52 PM

Second time without bitcoincore started already didnt do anything. Processes were started but nothing happend. I had to kill the armorydb.exe process. Followed your advice and started bitcoin core first, let it sync completely, started armory.... finished successfully! Balance correct! Guess there are still some issues when running bitcoincore as daemon in the background ? Is there something you want me to test?

Bitcoin / Armory / Re: different blocks between bitcoin core and armory

on: June 12, 2017, 03:49:38 PM

bitcoin core chain complete synct. started armory with a empty database folder. After some time: armorylog: https://pastebin.com/MmeSBPtD dblog.txt: https://pastebin.com/AGrSLwES For me it looks just like before, except I resynct the whole bitcoin core database on a new disk. I also placed armory's database on a new disk. What could be the problem here? *will restart armory again

Alternate cryptocurrencies / Announcements (Altcoins) / Re: VERITASEUM DISCUSSION THREAD

on: June 12, 2017, 02:18:33 PM

Quote from: creamers on June 11, 2017, 05:03:27 PM I was reading about veritaseum and I noticed that alot of the same people advertise about it on youtube. Then I read a reaction about a transaction: https://www.youtube.com/watch?v=V4HcfKcaGRA&lc=z13qivabfvbqtd10p23xxfbh1taoh1doj04 And who can tell me why these two addresses still have ALOT of VERI tokens ? Doesnt seem right, or what am I missing here? https://ethplorer.io/address/0x8f3470a7388c05ee4e7af3d01d8c722b0ff52374#tab=tab-holders Probably a one way trip for Reggie to the bahama's ... @Reggie, please answer or try to explain above question instead of a marketing story ..

Alternate cryptocurrencies / Announcements (Altcoins) / Re: VERITASEUM DISCUSSION THREAD

on: June 11, 2017, 05:03:27 PM

I was reading about veritaseum and I noticed that alot of the same people advertise about it on youtube. Then I read a reaction about a transaction: https://www.youtube.com/watch?v=V4HcfKcaGRA&lc=z13qivabfvbqtd10p23xxfbh1taoh1doj04 And who can tell me why these two addresses still have ALOT of VERI tokens ? Doesnt seem right, or what am I missing here? https://ethplorer.io/address/0x8f3470a7388c05ee4e7af3d01d8c722b0ff52374#tab=tab-holders

Bitcoin / Armory / Re: different blocks between bitcoin core and armory

on: June 09, 2017, 09:51:50 AM

Bitcoin core still reindexing, but armory crashed on the way : Quote -INFO - 07:16:04.576: (..\BlockchainScanner.cpp:650) scanned from height #432971 to #433637 -INFO - 07:16:06.307: (..\BlockchainScanner.cpp:650) scanned from height #433638 to #433787 -INFO - 07:16:06.619: (..\BlockchainScanner.cpp:225) scanned transaction history in 1907.24s -INFO - 07:16:08.836: (..\BlockchainScanner.cpp:1560) resolving txhashes -INFO - 07:21:47.731: (..\BlockchainScanner.cpp:1616) 4 blocks hit by tx filters -ERROR - 11:47:52.546: (..\SocketObject.cpp:126) poll() error in writeToSocket: 10038 -ERROR - 11:47:53.858: (..\BitcoinP2P.cpp:1027) caught SocketError exception in processDataStackThread: poll() error in writeToSocket: 10038 -INFO - 11:47:53.936: (..\BitcoinP2P.cpp:969) Disconnected from Bitcoin node

Pages: [1] 2 3 »