 Show Posts
|
|
Pages: [1] 2 »
|
For anyone upgrading from v9, please be aware there are a LOT of config changes. To make your lives easier, we wrote a tool to help you... https://gunbot.toolsSimply paste in your current v9 config, this tool will validate it and tell you everything that is wrong. (This happens purely client side) We can also fix it for you, in which case your config (minus its keys, smtp user/pass, withdraw address, telegram token, and other sensitive data) is sent to our server to be upgraded. |
|
|
|
Kick in the teeth for anyone who paid full price, especially recently.
Wouldn't this stance then apply to pretty much all discounts, anywhere? Therefore, that stance is rather invalid. There are quite the number of discount codes, and you can pay 10-15% off usually. Another 10% off as a special deal is nothing too drastic IMO. Yes, regardless of the time or what the product/service is. Just sell it for what it's worth in the first place. If $seller can sell it for that and make a profit, why isn't it just that price all the time. $seller would get more sales in general then, and not have to jump on stupid marketing bandwagons. |
|
|
|
Did you think your favorite Trading Bot would turn a blind eye to Black Friday and Cyber Monday?
I would have hoped it would, yes. Kick in the teeth for anyone who paid full price, especially recently. |
|
|
|
The config file in Gunbot does not account for exchange fees. So if you set your config to 1%, you'd only get a profit of .5% as you'd pay .25% for the purchase and another .25% for the sale. Gunbot only looks at the purchase and sell price... it's up to you to setup your confit to account for the transaction fees.
It varies by exchange, but for Bittrex, I've calculated it at a minimum 0.54% profit needed on a trade to break even. In Microprofits strategies, I've always used 0.8% as the baseline minimum to sell for, or all you end up doing is making the exchanges a tidy profit from your fees, greatly outweighing your own profits. |
|
|
|
How is that possible you made 1.103 profit your "GAIN": 1.4, and "SELLLVL1": 1.4, am i missing something?
Basically, because I didnt  Bug in the telegram bot found..... From telegram bot @ 05:08 Tue, 21 Nov 2017 05:06:34 GMT
New Bittrex order
Sell BTC-PAY
Total: 0.05079952 BTC
Rate: 0.00021851 BTC
Profit: 0.0006 BTC ($4.39)
Bought on: 21/11/2017 05:07
Percentage: 1.103% From telegram bot @ 05:23 Tue, 21 Nov 2017 05:18:46 GMT
New Bittrex order
Sell BTC-PAY
Total: 0.05101738 BTC
Rate: 0.00022064 BTC
Profit: 0.001 BTC ($8.1)
Bought on: 21/11/2017 05:07
Percentage: 2.035% The actual trades:  So this is actually "fake news". The telegram bot isnt very clever at checking, all it sees is "new sell order", and looks at "last by order", which at the time the bot sent the message, was NOT the buy that had been sold. In reality there was a 1.546% profit on the first trade, and 2.035% on the second. (Note these figures DO take into account the exchange fees - they are figures obtained from the exchange, NOT gunbot) (edit: Note that I am running a customised version of the telegram bot, based on code 95+ commits behind the current: https://github.com/mehtadone/CryptoGramBot so this bug may not exist in current/unmodified ones) |
|
|
|
<snip> 4. BBRSI / Stepgain. "strategies": {
"bbrsistepgain": {
"NAME": "bbrsistepgain",
"TRADING_LIMIT": 0.05,
"PERIOD": 15,
"RSI_BUY_LEVEL": 30,
"GAIN": 1.4,
"EMA1": 16,
"EMA2": 8,
"HIGH_BB": 40,
"LOW_BB": 30,
"STDV": 2,
"SMAPERIOD": 50,
"SELLLVL1": 1.4,
"SELLLVL2": 2.6,
"SELLLVL3": 70,
"SELLLVL": 3,
"PANIC_SELL": false,
"DOUBLE_UP": false,
"DOUBLE_UP_CAP": 1,
"STOP_LIMIT": 50,
"BUY_ENABLED": true,
"MIN_VOLUME_TO_BUY": 0.0001,
"MIN_VOLUME_TO_SELL": 0.0001,
"TRADES_TIMEOUT": 120
},
<snip> Are you really running SELLLVL set to 3? My understanding of Stepgain is that it wont sell until your sell level is met, in your case, Stepgain wont sell until a 70% return? Did something change? Yup, and having just re-read the stuff here I can only blame a bug for me actually getting any sales. Theres been 19 sells in the past 24h, all profitable, ranging from 1.103% to 5.959% |
|
|
|
--> Contest <-- 1.- Result in % of profit/loss (calculated with any tool you like, i.e. FrilledShark's, Cointracking, custom tools etc) 2.- A screenshot of your best trade in % of profit/loss taken directly from your exchange's trading history 3.- A screenshot of Gunbot-Gui logs showing your best trade 4.- The strategy you are using and the settings of that strategy 1. 94.022% (Reported by my https://github.com/mehtadone/CryptoGramBot ) Mon, 20 Nov 2017 22:17:28 GMT
New Bittrex order
Sell BTC-POT
Total: 0.097011 BTC
Rate: 0.00003699 BTC
Profit: 0.047 BTC ($388.88)
Bought on: 15/11/2017 02:48
Percentage: 94.022% 2.  ( https://imgur.com/a/9bhlz ) 3. Dont have logs of the purchase, but heres the sale. 26|b_BTC-P | GBXT_v6.0.1 BTC-POT Round # 1461
26|b_BTC-P | ------------------------------------------------------------------------------------------------
26|b_BTC-P | ɢՍÑßǾŦ XT Edition Scanning bittrex for trading opportunities 2017/11/20 22:13:49
26|b_BTC-P | ------------------------------------------------------------------------------------------------
26|b_BTC-P | 2017/11/20 22:13:50: BTC-POT Last Bid/Ask 0.00003891/0.00003894
26|b_BTC-P | ------------------------------------------------------------------------------------------------
26|b_BTC-P | EMA1: 0.00001768 === EMA2: 0.00001971
26|b_BTC-P | ------------------------------------------------------------------------------------------------
26|b_BTC-P | [HEARTBEAT] Sending message to exchanges we are alive
26|b_BTC-P | 2017/11/20 22:15:22: Got Trading History
26|b_BTC-P | 2017/11/20 22:15:23: Checking Open Orders
26|b_BTC-P | 2017/11/20 22:15:23: Price to buy: 0.00001373
26|b_BTC-P | 2017/11/20 22:15:23: Last Bid/Strategy Exit Point: 0.00003891/0.00001934
26|b_BTC-P | 2017/11/20 22:15:23: Last Ask/Strategy Entry Point: 0.00003894/0.00001373
26|b_BTC-P | 2017/11/20 22:15:23: XTrend for BTC-POT: UP!!!
26|b_BTC-P | 2017/11/20 22:15:23: There are some trading opportunities for BTC-POT at bittrex. Scanning Trade History
26|b_BTC-P | ɢƱÑ฿ʘͳ XT Edition Tips&Tricks: BTC-POT can be sold!!!
26|b_BTC-P | 2017/11/20 22:15:23: Last Bid price BTC-POT: 0.00003891 | Last Ask: 0.00003894
26|b_BTC-P | 2017/11/20 22:15:23: Balance BTC: 1.5180688
26|b_BTC-P | 2017/11/20 22:15:23: Balance POT: 2621.91924488
26|b_BTC-P | 2017/11/20 22:15:23: On Orders POT: 0
26|b_BTC-P | Processing strategy bbrsistepgain for BTC-POT on bittrex
26|b_BTC-P | 2017/11/20 22:15:23: Entering sell cycle
26|b_BTC-P | ┌───────────────────┬────────────┬────────────────┬────────────────┬────────────┬───────────────┬────────────┬─────────┐
26|b_BTC-P | │ ɢƱҊɮǾͳ XT Edition │ SMA │ LowBB │ HighBB │ Last │ POT │ Last Buy │ Pair │
26|b_BTC-P | ├───────────────────┼────────────┼────────────────┼────────────────┼────────────┼───────────────┼────────────┼─────────┤
26|b_BTC-P | │ Sell cycle │ 0.00001594 │ 0.000010419269 │ 0.000021451131 │ 0.00003891 │ 2621.91924488 │ 0.00001907 │ BTC-POT │
26|b_BTC-P | └───────────────────┴────────────┴────────────────┴────────────────┴────────────┴───────────────┴────────────┴─────────┘
26|b_BTC-P | ************************************************************************************************
26|b_BTC-P | XTreme Trend Watcher says: Trend is still up !!! Waiting to sell
26|b_BTC-P | ************************************************************************************************
26|b_BTC-P | GBXT_v6.0.1 BTC-POT Round # 1462
26|b_BTC-P | ------------------------------------------------------------------------------------------------
26|b_BTC-P | ɢƱΠßǾŁ XT Edition Scanning bittrex for trading opportunities 2017/11/20 22:16:03
26|b_BTC-P | ------------------------------------------------------------------------------------------------
26|b_BTC-P | 2017/11/20 22:16:03: BTC-POT Last Bid/Ask 0.00003699/0.00003700
26|b_BTC-P | ------------------------------------------------------------------------------------------------
26|b_BTC-P | EMA1: 0.00001768 === EMA2: 0.00001971
26|b_BTC-P | ------------------------------------------------------------------------------------------------
26|b_BTC-P | 2017/11/20 22:17:29: Got Trading History
26|b_BTC-P | 2017/11/20 22:17:29: Checking Open Orders
26|b_BTC-P | 2017/11/20 22:17:29: Price to buy: 0.00001373
26|b_BTC-P | 2017/11/20 22:17:29: Last Bid/Strategy Exit Point: 0.00003699/0.00001934
26|b_BTC-P | 2017/11/20 22:17:29: Last Ask/Strategy Entry Point: 0.00003700/0.00001373
26|b_BTC-P | 2017/11/20 22:17:29: XTrend for BTC-POT: DOWN!!!
26|b_BTC-P | 2017/11/20 22:17:29: There are some trading opportunities for BTC-POT at bittrex. Scanning Trade History
26|b_BTC-P | ɢՍͶɃØͳ XT Edition Tips&Tricks: BTC-POT can be sold!!!
26|b_BTC-P | 2017/11/20 22:17:29: Last Bid price BTC-POT: 0.00003699 | Last Ask: 0.000037
26|b_BTC-P | 2017/11/20 22:17:29: Balance BTC: 1.5180688
26|b_BTC-P | 2017/11/20 22:17:29: Balance POT: 2621.91924488
26|b_BTC-P | 2017/11/20 22:17:29: On Orders POT: 0
26|b_BTC-P | Processing strategy bbrsistepgain for BTC-POT on bittrex
26|b_BTC-P | 2017/11/20 22:17:29: Entering sell cycle
26|b_BTC-P | ┌───────────────────┬────────────┬────────────────┬────────────────┬────────────┬───────────────┬────────────┬─────────┐
26|b_BTC-P | │ ɢƱͶƁøŁ XT Edition │ SMA │ LowBB │ HighBB │ Last │ POT │ Last Buy │ Pair │
26|b_BTC-P | ├───────────────────┼────────────┼────────────────┼────────────────┼────────────┼───────────────┼────────────┼─────────┤
26|b_BTC-P | │ Sell cycle │ 0.00001594 │ 0.000010419269 │ 0.000021451131 │ 0.00003699 │ 2621.91924488 │ 0.00001907 │ BTC-POT │
26|b_BTC-P | └───────────────────┴────────────┴────────────────┴────────────────┴────────────┴───────────────┴────────────┴─────────┘
26|b_BTC-P | ************************************************************************************************
26|b_BTC-P | Strategy GAIN for BTC-POT on bittrex -| Selling 2621.91924488 of BTC-POT at rate 0.00003699
26|b_BTC-P | ************************************************************************************************
4. BBRSI / Stepgain. "strategies": {
"bbrsistepgain": {
"NAME": "bbrsistepgain",
"TRADING_LIMIT": 0.05,
"PERIOD": 15,
"RSI_BUY_LEVEL": 30,
"GAIN": 1.4,
"EMA1": 16,
"EMA2": 8,
"HIGH_BB": 40,
"LOW_BB": 30,
"STDV": 2,
"SMAPERIOD": 50,
"SELLLVL1": 1.4,
"SELLLVL2": 2.6,
"SELLLVL3": 70,
"SELLLVL": 3,
"PANIC_SELL": false,
"DOUBLE_UP": false,
"DOUBLE_UP_CAP": 1,
"STOP_LIMIT": 50,
"BUY_ENABLED": true,
"MIN_VOLUME_TO_BUY": 0.0001,
"MIN_VOLUME_TO_SELL": 0.0001,
"TRADES_TIMEOUT": 120
},
My Honest review of GunbotI first found gunbot via this thread, when looking at the various trading bots just before BCC/BCH spawned into existance. I started trading using v3.3.2, and within a couple of days v5 was announced. Initially I traded on Kraken, with limited results, due to being rather buggy. Whether thats entirely the bot or krakens fault is still unclear to me, but I was recommended to try bittrex instead. So I bought an additional licence for bittrex, and started trading, initially using bb with some good results. Some of the issues I have had with gunbot include; Polling speed can be rather random, which was a major problem with v4, so I wrote a script to launch 1 pair in its own instance of the bot, which allows me to finely tune the polling time for each pair individually. This is freely available here: https://github.com/tandyuk/gblauncher/Memory usage used to be a problem with v4/5, the server I was running it on had 16gb ram, and when running 100+ pairs, I remember having to increase it to 24Gb ram. This seems to be solved in v6 however, as 120 pairs is now using a little over 12Gb ram. Bandwidth is currently an issue with v6.0.1, however I am told this has been fixed in v6.0.2 which is currently undergoing beta testing. Running 84 pairs, at a 30second resolution, the bot used 750GB in one day, so beware if you are trading from home, or have a vps with a bandwidth limit. The final issue I have had, is the bot missing trades due to open orders, eg bot buys, price rises, bot places sell order at eg 0.001, price drops slightly, but existing order to sell at 0.001 just sits there, in some cases for hours. This I believe has also been fixed in v6.0.2, however in the interim I wrote the following script to deal with it: bittrex-govenor.php in https://github.com/tandyuk/gunbotscriptsSo, Gunbot, like all software, is not without its issues! However the dev team are generally pretty good at fixing issues and adding/tweaking features to make the bot better. So, is Gunbot profitable?The honest answer to this, is I don't know. Individual trades, for sure, it picks up on some things that you would never catch trading manually (Like the epic trade above), but overall I dont actually know how much the bot has made me since I started trading. 2 months ago I started trading with a 15BTC fund. I track my trading with cointracking.info however I have no way to identify trades done by the bot, vs trades done by me manually. During that time, I have certainly incurred some big losses, most of which are definitely the result of my manual (bad) trades! Taking into account the losses which I know 100% were incurred by me, rather than the bot, I should have a balance of 14.25BTC. My current portfolio according to cointracking is worth 14.73BTC, so at a minimum, the bot has earnt around 0.5BTC for me, but quite possibly more. Would I recommend gunbot?Overall, yes. However it is not a magic 'make money for me with no work required' machine - it requires a LOT of research to learn about the different trading strategies, which strategies to use on which types of markets, which coins to trade at a particular time, when to sell 'bags' at a loss and when to hold onto them (I know some people would have considered the POT buy that led to this epic trade as being a bag having been held for 5 days) Maybe the learning curve would be less steep for someone who is already familiar with trading, but from what I've seen the vast majority of the users of gunbot are completely new to trading. |
|
|
|
I just started with Gunbot. I have some questions.
I am running Gunbot XT on an Ubuntu VPS. I am using another local Windows Installation to edit the config via the web gui. Afterwards I transfer this to the VPS via Win SCP. I am connected to the VPS by using Putty.
Q1: How could I execute Gunbot and still be able to close the SSH Session? I know it is possible to run with PM2 with yaml files, but for now I am looking for an easier solution.
Q2: Is Gunbot writing a log (where can I find it?) or do I have to pipe the output into a log?
Q3: After editing the config on the windows machine I would like to save the file in order to copy it via SCP to the VPS. But there is no save button. By now I can just start gunbot and instantly stop it in order to save the config.js file. Is there a better solution?
Q1 I wrote a solution for: https://github.com/tandyuk/gblauncherQ2: It logs to stdout, but is redirectable using things like pm2 Q3: If you look closely at the commented out code in gblaunch.php, you'll see the code I use to execute "php gblaunch.php reload" via cron, which pulls the then-current master config file (and gunbot archive if it needs) from my fileserver via SFTP. All the source files are hosted on my "windows" fileserver (debian + samba), and edited on my windows client. |
|
|
|
I am not good in editing config file..
how to create separate strategies for pairs ..
like btc-ltc stepgain with 3/10 and btc-eth with 5/15
Use the overrides section, eg: "BTC-BCC": {
"strategy": "bbrsistepgain",
"override": {
"TRADING_LIMIT": 1,
"RSI_BUY_LEVEL": 20,
"PERIOD": 1
}
} |
|
|
|
With 0.96.2, I sent a transaction with a low fee. It says 'Right click to bump fee', but when I do so, nothing happens. This is the log of the original tx, and my attempt to bump the fee: 2017-09-18 13:38:04 (INFO) -- TxFrames.pyc:727 - Change address behavior: NewAddr
2017-09-18 13:38:20 (INFO) -- (PPRINT from ArmoryQt.py:3118)
01000000 013c0da7 aae5ca8c e6190a75 7f38cf83 8b96a8cf 589255bb d1978cb9
f48922ae 9d010000 008b4830 45022100 f7bbe930 12b3bd1f 206e418c a672bad0
<snip>
00001976 a914d9d0 32d542ed de06a5d1 59a6da53 c6cc98c9 9cb788ac c0568d01
00000000 1976a914 0456126c 17301d0e 8383054f a723c6fe ec68bf39 88ac006a
0700
2017-09-18 13:38:20 (INFO) -- (PPRINT from ArmoryQt.py:3119)
Transaction:
TxHash: 3c4faaffb3640e3a9566ca310b6bc6a1c174e38cc7812573d757e97037d3c29d (BE)
Version: 1
nInputs: 1
nOutputs: 2
LockTime: 485888
Inputs:
PyTxIn:
PrevTxHash: 9dae2289f4b98c97d1bb559258cfa8968b83cf387f750a19e68ccae5aaa70d3c (BE)
TxOutIndex: 1
Script: (483045022100f7bbe93012b3bd1f206e418ca672bad07092cd405435e5827d34)
Sender: 154Enja33FvFaRT6QtqgXiWd7D2K6KNddy
Seq: 4294967293
Outputs:
TxOut:
Value: 300000000 (3.0)
Script: OP_DUP OP_HASH160 (1Lrh3WzuXJhFLKdahccsFtv5j7Fq62qZZa) OP_EQUALVERIFY OP_CHECKSIG
TxOut:
Value: 26040000 (0.2604)
Script: OP_DUP OP_HASH160 (1Pvp9paFSV7y3fhSk4AFyLHu8XeqJd3vS) OP_EQUALVERIFY OP_CHECKSIG
2017-09-18 13:38:20 (INFO) -- ArmoryQt.py:3124 - Sending Tx, 9dc2d33770e957d7732581c78ce374c1a1c66b0b31ca66953a0e64b3ffaa4f3c
2017-09-18 13:38:20 (INFO) -- ArmoryQt.py:5343 - Bitcoins Sent!
Amount: 3.00036 BTC
From: Wallet "Michael 2017" (2WCFZkJXR)
To: 1Lrh3WzuXJhFLKdahccsFtv5j7Fq62qZZa
2017-09-18 13:38:27 (INFO) -- ArmoryQt.py:4944 - New Block! : 485889
2017-09-18 13:38:27 (INFO) -- ArmoryQt.py:4952 - Current block number: 485889
2017-09-18 13:46:52 (ERROR) -- Traceback (most recent call last):
File "ArmoryQt.py", line 3409, in showContextMenuLedger
File "ArmoryQt.py", line 5913, in bumpFee
File "armoryengine\PyBtcWallet.pyc", line 1818, in getCommentForAddress
File "CppBlockUtils.pyc", line 4083, in getScriptHashVectorForIndex
RuntimeError: invalid asset index
|
|
|
|
The shortcut 'target' was: "C:\Program Files (x86)\Armory\ArmoryQt.exe" --datadir="M:\Armory" --satoshi-datadir="C:\Bitcoin\" Having removed all the quotes from the datadirs, its now working And the /blocks was just me trying various options to get it working. It would be nice if on an update, my shortcuts werent replaced. What should I be putting in armoryconfig.txt so that I only need to set --datadir each time? |
|
|
|
|
so any clues on what I should do to get armory working again?
Bitcond is running fine and is in sync.
Armory just refuses to connect, and get stuck at 'preparing databases'.
As I said ive wiped out the old databases folder.
A new databases folder has been created, but is empty.
Bitcoin data is in c:\Bitcoin and has 60Gb free.
Armory data is in M:\Armory and has 1.5Tb free.
|
|
|
|
Yes it is.
Log file opened at 09:59:03.000: M:\Armory/dbLog.txt
-INFO - 09:59:03.000: (..\main.cpp:32) Running on 8 threads
-INFO - 09:59:03.000: (..\main.cpp:33) Ram usage level: 4
-INFO - 09:59:03.015: (c:\users\goat\code\armory3\cppforswig\BDM_Server.h:263) Listening on port 9001
Log file opened at 10:00:21.000: M:\Armory/dbLog.txt
-INFO - 10:00:21.000: (..\main.cpp:32) Running on 8 threads
-INFO - 10:00:21.000: (..\main.cpp:33) Ram usage level: 4
-INFO - 10:00:21.000: (c:\users\goat\code\armory3\cppforswig\BDM_Server.h:263) Listening on port 9001
Log file opened at 10:54:54.000: M:\Armory/dbLog.txt
-INFO - 10:54:54.000: (..\main.cpp:32) Running on 8 threads
-INFO - 10:54:54.000: (..\main.cpp:33) Ram usage level: 4
-INFO - 10:54:54.016: (c:\users\goat\code\armory3\cppforswig\BDM_Server.h:263) Listening on port 9001
Log file opened at 10:57:08.000: M:\Armory/dbLog.txt
-INFO - 10:57:08.000: (..\main.cpp:32) Running on 8 threads
-INFO - 10:57:08.000: (..\main.cpp:33) Ram usage level: 4
-INFO - 10:57:08.000: (c:\users\goat\code\armory3\cppforswig\BDM_Server.h:263) Listening on port 9001
|
|
|
|
edit: fixed the '0.92' typos to 0.96!
Ok, so I've just upgraded from 0.96 beta to 0.96.2 on windows 10 x64.
I run my own bitcoin node with custom datadir, and custom armory db dir, and have updated the armory shortcut to:
"C:\Program Files (x86)\Armory\ArmoryQt.exe" --datadir="M:\Armory" --satoshi-datadir="C:\Bitcoin\blocks\"
Note, have also tried --satoshi-datadir="C:\Bitcoin\" with no difference.
Have also tried running as administrator.
When armory starts, it responds, but just sits there forever on "Preparing Databases".
I have also moved my old M:\Armory\databases folder to databases.old to force it to regenerate.
The logs reveal:
(with --satoshi-datadir="C:\Bitcoin\blocks" )
[code]
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1147 - C++ block utilities loaded successfully
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1264 -
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1265 -
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1266 -
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1267 - ************************************************************
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1268 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe --datadir=M:\Armory --satoshi-datadir=C:\Bitcoin\blocks"
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1269 - ************************************************************
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1270 - Loading Armory Engine:
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1271 - Armory Version : 0.96.2
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1272 - Armory Build: : 95dc55907f
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1273 - PyBtcWallet Version : 1.35
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1274 - Detected Operating system: Windows
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1275 - OS Variant : 8-6.2.9200--Multiprocessor Free
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1276 - User home-directory : C:\Users\james\AppData\Roaming
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1277 - Satoshi BTC directory : C:\Bitcoin\blocks"
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1278 - Armory home dir : M:\Armory
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1279 - Detected System Specs :
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1280 - Total Available RAM : 31.91 GB
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1281 - CPU ID string : Intel64 Family 6 Model 94 Stepping 3, GenuineIntel
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1282 - Number of CPU cores : 8 cores
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1283 - System is 64-bit : True
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1284 - Preferred Encoding : cp1252
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1285 - Machine Arch : amd64
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1286 - Available HDD (ARM) : 1591 GB
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1287 - Available HDD (BTC) : 0 GB
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1288 -
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1289 - Network Name: Main Network
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1290 - Satoshi Port: 8333
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1291 - Do wlt check: True
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1292 - Named options/arguments to armoryengine.py:
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - thread_count : -1
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - rescan : False
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - ignoreAllZC : False
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - rescanBalance : False
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - disableModules : False
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - port : None
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - interport : 8223
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - coverageOutputDir: None
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - forceWalletCheck: False
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - regtest : False
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - rebuild : False
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - nettimeout : 2
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - datadir : M:\Armory
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - clearMempool : False
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - offline : False
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - armoryDBDir : DEFAULT
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - armorydb_port : 9001
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - satoshiPort : DEFAULT
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - useTorSettings : False
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - netlog : False
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - keypool : 100
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - coverageInclude : None
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - forceOnline : False
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - redownload : False
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - rpcBindAddr : 127.0.0.1
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - armorydb_ip : 127.0.0.1
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - multisigFile : DEFAULT
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - ram_usage : -1
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - mtdebug : False
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - logDisable : False
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - settingsPath : M:\Armory\ArmorySettings.txt
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - language : en
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - db_type : DB_FULL
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - doDebug : False
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - enableDetSign : True
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - disableConfPermis: False
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - testnet : False
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - rpcport : DEFAULT
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - satoshiHome : C:\Bitcoin\blocks"
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - satoshiRpcport : DEFAULT
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - logFile : M:\Armory\ArmoryQt.exe.log.txt
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1294 - verbosity : None
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1295 - Other arguments:
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1298 - ************************************************************
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:1701 - C++ block utilities loaded successfully
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:3562 - Using settings file: M:\Armory\ArmorySettings.txt
2017-09-02 10:00:16 (ERROR) -- ArmoryUtils.pyc:3719 - Unsupported language specified. Defaulting to English (en)
2017-09-02 10:00:16 (INFO) -- ArmoryUtils.pyc:3722 - Using Language: en
2017-09-02 10:00:16 (INFO) -- BDM.pyc:355 - Using the asynchronous/multi-threaded BlockDataManager.
2017-09-02 10:00:16 (INFO) -- BDM.pyc:356 - Blockchain operations will happen in the background.
2017-09-02 10:00:16 (INFO) -- BDM.pyc:357 - Devs: check TheBDM.getState() before asking for data.
2017-09-02 10:00:16 (INFO) -- BDM.pyc:358 - Registering addresses during rescans will queue them for
2017-09-02 10:00:16 (INFO) -- BDM.pyc:359 - inclusion after the current scan is completed.
2017-09-02 10:00:17 (INFO) -- ArmoryUtils.pyc:3562 - Using settings file: M:\Armory\ArmorySettings.txt
2017-09-02 10:00:17 (INFO) -- ArmoryQt.py:2061 - loadWalletsAndSettings
2017-09-02 10:00:17 (INFO) -- ArmoryQt.py:2121 - Loading wallets...
2017-09-02 10:00:17 (INFO) -- ArmoryQt.py:2186 - Number of wallets read in: 5
<snip>
2017-09-02 10:00:17 (INFO) -- ArmoryQt.py:2196 - Loading Multisig Lockboxes
2017-09-02 10:00:17 (INFO) -- ArmoryQt.py:1763 - acquiring process mutex...
2017-09-02 10:00:18 (INFO) -- ArmoryQt.py:1395 - setupUriRegistration
2017-09-02 10:00:18 (INFO) -- ArmoryQt.py:1463 - Armory already registered for current user. Done!
2017-09-02 10:00:18 (INFO) -- ArmoryQt.py:566 - Usermode: Expert
2017-09-02 10:00:18 (INFO) -- ArmoryQt.py:1698 - Changing usermode:
2017-09-02 10:00:18 (INFO) -- ArmoryQt.py:1699 - From: Expert
2017-09-02 10:00:18 (INFO) -- ArmoryQt.py:1707 - To: Expert
2017-09-02 10:00:18 (INFO) -- ArmoryQt.py:1836 - startBitcoindIfNecessary
2017-09-02 10:00:21 (INFO) -- ArmoryQt.py:1872 - setSatoshiPaths
2017-09-02 10:00:21 (ERROR) -- BDM.pyc:270 - setSatoshiDir: directory does not exist: C:\Bitcoin\blocks"
2017-09-02 10:00:21 (WARNING) -- SDM.pyc:396 - Spawning DB with command: ./ArmoryDB.exe --db-type="DB_FULL" --cookie --datadir="M:\Armory" --dbdir="M:\Armory\databases"
2017-09-02 10:00:21 (INFO) -- ArmoryUtils.pyc:672 - Executing popen: ['./ArmoryDB.exe', '--db-type="DB_FULL"', '--cookie', '--datadir="M:\\Armory"', u'--dbdir="M:\\Armory\\databases"']
2017-09-02 10:00:22 (INFO) -- ArmoryQt.py:1824 - Connecting on port 9001
2017-09-02 10:00:22 (INFO) -- ArmoryQt.py:1924 - Setting netmode: 1
2017-09-02 10:00:22 (ERROR) -- BDM.pyc:199 - DB error: C:\Users\james\AppData\Roaming/Bitcoin/blocks is not a valid path
2017-09-02 10:00:22 (INFO) -- ArmoryQt.py:1924 - Setting netmode: 0
2017-09-02 10:00:22 (INFO) -- ArmoryQt.py:1906 - loadBlockchainIfNecessary
2017-09-02 10:00:22 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-09-02 10:00:22 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-09-02 10:42:07 (INFO) -- ArmoryQt.py:5447 - BDM is safe for clean shutdown
2017-09-02 10:42:07 (INFO) -- SDM.pyc:459 - Called stopBitcoind
2017-09-02 10:42:07 (INFO) -- SDM.pyc:465 - ...but bitcoind is not running, to be able to stop
2017-09-02 10:42:07 (INFO) -- ArmoryQt.py:5460 - Attempting to close the main window!
(with --satoshi-datadir="C:\Bitcoin" ) 2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1147 - C++ block utilities loaded successfully
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1264 -
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1265 -
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1266 -
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1267 - ************************************************************
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1268 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe --datadir=M:\Armory --satoshi-datadir=C:\Bitcoin"
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1269 - ************************************************************
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1270 - Loading Armory Engine:
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1271 - Armory Version : 0.96.2
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1272 - Armory Build: : 95dc55907f
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1273 - PyBtcWallet Version : 1.35
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1274 - Detected Operating system: Windows
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1275 - OS Variant : 8-6.2.9200--Multiprocessor Free
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1276 - User home-directory : C:\Users\james\AppData\Roaming
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1277 - Satoshi BTC directory : C:\Bitcoin"
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1278 - Armory home dir : M:\Armory
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1279 - Detected System Specs :
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1280 - Total Available RAM : 31.91 GB
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1281 - CPU ID string : Intel64 Family 6 Model 94 Stepping 3, GenuineIntel
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1282 - Number of CPU cores : 8 cores
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1283 - System is 64-bit : True
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1284 - Preferred Encoding : cp1252
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1285 - Machine Arch : amd64
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1286 - Available HDD (ARM) : 1591 GB
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1287 - Available HDD (BTC) : 0 GB
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1288 -
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1289 - Network Name: Main Network
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1290 - Satoshi Port: 8333
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1291 - Do wlt check: True
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1292 - Named options/arguments to armoryengine.py:
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - thread_count : -1
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - rescan : False
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - ignoreAllZC : False
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - rescanBalance : False
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - disableModules : False
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - port : None
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - interport : 8223
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - coverageOutputDir: None
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - forceWalletCheck: False
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - regtest : False
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - rebuild : False
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - nettimeout : 2
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - datadir : M:\Armory
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - clearMempool : False
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - offline : False
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - armoryDBDir : DEFAULT
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - armorydb_port : 9001
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - satoshiPort : DEFAULT
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - useTorSettings : False
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - netlog : False
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - keypool : 100
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - coverageInclude : None
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - forceOnline : False
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - redownload : False
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - rpcBindAddr : 127.0.0.1
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - armorydb_ip : 127.0.0.1
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - multisigFile : DEFAULT
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - ram_usage : -1
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - mtdebug : False
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - logDisable : False
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - settingsPath : M:\Armory\ArmorySettings.txt
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - language : en
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - db_type : DB_FULL
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - doDebug : False
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - enableDetSign : True
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - disableConfPermis: False
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - testnet : False
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - rpcport : DEFAULT
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - satoshiHome : C:\Bitcoin"
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - satoshiRpcport : DEFAULT
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - logFile : M:\Armory\ArmoryQt.exe.log.txt
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1294 - verbosity : None
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1295 - Other arguments:
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1298 - ************************************************************
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:1701 - C++ block utilities loaded successfully
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:3562 - Using settings file: M:\Armory\ArmorySettings.txt
2017-09-02 10:57:02 (ERROR) -- ArmoryUtils.pyc:3719 - Unsupported language specified. Defaulting to English (en)
2017-09-02 10:57:02 (INFO) -- ArmoryUtils.pyc:3722 - Using Language: en
2017-09-02 10:57:02 (INFO) -- BDM.pyc:355 - Using the asynchronous/multi-threaded BlockDataManager.
2017-09-02 10:57:02 (INFO) -- BDM.pyc:356 - Blockchain operations will happen in the background.
2017-09-02 10:57:02 (INFO) -- BDM.pyc:357 - Devs: check TheBDM.getState() before asking for data.
2017-09-02 10:57:02 (INFO) -- BDM.pyc:358 - Registering addresses during rescans will queue them for
2017-09-02 10:57:02 (INFO) -- BDM.pyc:359 - inclusion after the current scan is completed.
2017-09-02 10:57:03 (INFO) -- ArmoryUtils.pyc:3562 - Using settings file: M:\Armory\ArmorySettings.txt
2017-09-02 10:57:03 (INFO) -- ArmoryQt.py:2061 - loadWalletsAndSettings
2017-09-02 10:57:03 (INFO) -- ArmoryQt.py:2121 - Loading wallets...
2017-09-02 10:57:04 (INFO) -- ArmoryQt.py:2186 - Number of wallets read in: 5
<snip>
2017-09-02 10:57:04 (INFO) -- ArmoryQt.py:2196 - Loading Multisig Lockboxes
2017-09-02 10:57:04 (INFO) -- ArmoryQt.py:1763 - acquiring process mutex...
2017-09-02 10:57:05 (INFO) -- ArmoryQt.py:1395 - setupUriRegistration
2017-09-02 10:57:05 (INFO) -- ArmoryQt.py:1463 - Armory already registered for current user. Done!
2017-09-02 10:57:05 (INFO) -- ArmoryQt.py:566 - Usermode: Expert
2017-09-02 10:57:05 (INFO) -- ArmoryQt.py:1698 - Changing usermode:
2017-09-02 10:57:05 (INFO) -- ArmoryQt.py:1699 - From: Expert
2017-09-02 10:57:05 (INFO) -- ArmoryQt.py:1707 - To: Expert
2017-09-02 10:57:05 (INFO) -- ArmoryQt.py:1836 - startBitcoindIfNecessary
2017-09-02 10:57:08 (INFO) -- ArmoryQt.py:1872 - setSatoshiPaths
2017-09-02 10:57:08 (ERROR) -- BDM.pyc:270 - setSatoshiDir: directory does not exist: C:\Bitcoin"
2017-09-02 10:57:08 (WARNING) -- SDM.pyc:396 - Spawning DB with command: ./ArmoryDB.exe --db-type="DB_FULL" --cookie --datadir="M:\Armory" --dbdir="M:\Armory\databases"
2017-09-02 10:57:08 (INFO) -- ArmoryUtils.pyc:672 - Executing popen: ['./ArmoryDB.exe', '--db-type="DB_FULL"', '--cookie', '--datadir="M:\\Armory"', u'--dbdir="M:\\Armory\\databases"']
2017-09-02 10:57:09 (INFO) -- ArmoryQt.py:1824 - Connecting on port 9001
2017-09-02 10:57:09 (INFO) -- ArmoryQt.py:1924 - Setting netmode: 1
2017-09-02 10:57:09 (ERROR) -- BDM.pyc:199 - DB error: C:\Users\james\AppData\Roaming/Bitcoin/blocks is not a valid path
2017-09-02 10:57:09 (INFO) -- ArmoryQt.py:1924 - Setting netmode: 0
2017-09-02 10:57:09 (INFO) -- ArmoryQt.py:1906 - loadBlockchainIfNecessary
2017-09-02 10:57:09 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-09-02 10:57:09 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
Why is armory complaining that c:\Bitcoin[\blocks] doesnt exist? PS C:\WINDOWS\system32> dir c:\bitcoin
Directory: C:\bitcoin
Mode LastWriteTime Length Name
---- ------------- ------ ----
d----- 02/09/2017 08:25 blocks
d----- 02/09/2017 02:17 chainstate
d----- 31/08/2017 01:32 database
-a---- 24/12/2016 00:15 37 banlist.dat
-a---- 24/12/2016 00:05 89 bitcoin.conf
-a---- 24/01/2014 13:03 0 db.log
-a---- 31/08/2017 01:25 2118709 debug.log
-a---- 31/08/2017 01:25 22001 fee_estimates.dat
-a---- 31/08/2017 01:25 44076023 mempool.dat
-a---- 02/09/2017 10:28 4716106 peers.dat
-a---- 02/09/2017 10:32 90112 wallet.dat I also suffer from the issue where after exiting Armory, ArmoryDB.exe continues to run in the background until such time as it is manually killed via task manager. dblog.txt:
Log file opened at 09:59:03.000: M:\Armory/dbLog.txt
-INFO - 09:59:03.000: (..\main.cpp:32) Running on 8 threads
-INFO - 09:59:03.000: (..\main.cpp:33) Ram usage level: 4
-INFO - 09:59:03.015: (c:\users\goat\code\armory3\cppforswig\BDM_Server.h:263) Listening on port 9001
Log file opened at 10:00:21.000: M:\Armory/dbLog.txt
-INFO - 10:00:21.000: (..\main.cpp:32) Running on 8 threads
-INFO - 10:00:21.000: (..\main.cpp:33) Ram usage level: 4
-INFO - 10:00:21.000: (c:\users\goat\code\armory3\cppforswig\BDM_Server.h:263) Listening on port 9001
[/code] |
|
|
|
tried running the primeminer on the beeeeer thread but it crashed on me. Anyone have it working with any of the jhPrimeminer versions?
it crashed because the server was down .. should work ok now servers back up in the op http://www.ppcointalk.org/index.php?topic=485.0 is a .diff file attached to the post. it will fix the getwork protocol for mumus 7.x ... The less technically inclined will have to live with pre compiled win binaries (cough me cough)  I'm in the same boat, i can't code. I tried using the various jhPrimeiners with beeeeer, no luck since they all used getwork. I'm trying out beer bc apparently it's better for smaller (single cpu) miners. and it's always good to support new pools. xolo's miner seems to work about as fast as ypool's, I''m getting ~1.5xpm/day on my 6-core. some ppl said they got 3x more mining at beer, do they have jhprimeminer patched with the diff file? or is it just more stuff that's over my head lol my latest linux build will work on beeeeer, but it has way more invalid shares than their miners which use getworx. Im trying to port getworx over to my miner, unsuccessfully so far, because my c++ isnt that great yet! |
|
|
|
Just put up a new build of my linux miner https://github.com/tandyuk/jhPrimeminerThis version has some heavy changes (although not related to actual mining), so it needs thoroughly testing. I will be working on my web interface over the next few days, and releasing a simplified version for anyone who wants their miners reporting to their own server. Donations welcomed: XPM: AQ5egZqgexBhgF9TCkZ2ZGrXPaB8igkNQA BTC: 185Z63qhVXf9mCxxjAeHaqKYccaw3aFF4P |
|
|
|
TBH, I'd rather pay 1BTC for something that actually worked  |
|
|
|
should tandyuk's code compile on centos-5 - what problems might there be?
I get a lot of warnings (I could post the build log). and when I run the binary it won't submit valid shares.
I havent tried it on 5, but i dont see why it shouldn't, provided you have the dependencies (which may well be named differently compared to centos 6). Expect LOTS of warnings, this is largely due to the code being ported from windows, I am still tidying it up. |
|
|
|
|
