Hi, Doc!
I have a few questions that I would like to clarify:
1. If I use config file, where I specify gpu-only parameters (intensity, threads, worksize), then parameters rebootscriptgpuwatchdog and rebootscriptminrigspeed, which specified via cmd, not working. But if these parameters specify in config file, they are working. So, is it possible to give priority to cmd input over config file?
2. Is it possible to add support for variables for pools file? If you have many rigs you must specify worker name, in pools.txt, on each of them, and it's not comfortable. But worker name can be taken from variable %computername%.

Hi, Doc!
1. In the last version there is a bug with watchdog, which cause random restart:

[2019-03-04 20:10:23] json_send[234]: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"96b65627-09c7-416c-b714-b9b7b0db8e27","job_id":"spBTylKdrhgNUGztZDhpBNKzxe/+","nonce":"a9090080","result":"478c71f8d734ba5d3f6d3fdc007ac0ef71f2a461f71ae8cfabb0f820c6120000"}}
[2019-03-04 20:10:23] json_receive[62]: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"OK"}}
[2019-03-04 20:10:23] miner_result: Pool accepted result 0x000012C6 [39ms]
[2019-03-04 20:10:44] hashrate: GPU0: 524 H/s [T:50c][BUS:1]
[2019-03-04 20:10:44] hashrate: GPU1: 524 H/s [T:50c][BUS:2]
[2019-03-04 20:10:44] hashrate: GPU2: 524 H/s [T:50c][BUS:3]
[2019-03-04 20:10:44] hashrate: GPU3: 524 H/s [T:52c][BUS:4]
[2019-03-04 20:10:44] hashrate: GPU4: 524 H/s [T:50c][BUS:5]
[2019-03-04 20:10:44] hashrate: Total: 2620 H/s
[2019-03-04 20:10:50] miner_result: Sending user result to pool
[2019-03-04 20:10:50] json_send[234]: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"96b65627-09c7-416c-b714-b9b7b0db8e27","job_id":"spBTylKdrhgNUGztZDhpBNKzxe/+","nonce":"8f5733b3","result":"80dfc0bacfcf0e18a6c7ca971e003b8b11548d6145f771b4ecc847cb6fa10000"}}
[2019-03-04 20:10:50] json_receive[62]: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"OK"}}
[2019-03-04 20:10:50] miner_result: Pool accepted result 0x0000A16F [39ms]
[2019-03-04 20:10:48] watchdog: No share sent for more than 71582788 minutes! Miner will restart
[2019-03-04 20:10:48] Restarting miner process

2. And what about to add feature to set up password for api and http access?

Hi, Doc!
Could you add feature to set up password for api and http access?

Hi, Doktor!
In new version (1.5.5) there is some bug:
Sometimes I get errors (invalid job id)
https://drive.google.com/file/d/1to6uThqMp075p1E5Zn0WEe784GIW00vy/view
https://drive.google.com/file/d/1AGkC5GfAXUAzn6tV4K4Occ7fN0Hx-Com/view
I get this on diffrent pools and algos.

Same situation.
I have couple 10-11 days old chunks but wallet says: "you don't have mature coins"

Looks like there is problem with blockchain. Last block 1310273 (4,5 hours ago).

Yes, staking is working now after I do these manipulations. Thanks!

I have about 6.8k CBX (in 4 chunks) in my wallet. I didn't mine any PoSP block since 1st January. Tell me please what I do wrong?
Wallet (2.1.1) is unlocked, 14 connections, block height is matching with block explorer.

Maybe I should divide my coins to more chunks?

Yes, I could not fully synced yesterday, but today it's all OK.

Looks like both block explorers and Banx wallet (https://www.banx.io/systemstatus) are on fork (1252695). Current block number 1251892.

Problem with Cryptsy? Okay. But we also have a trading pair on Poloniex:
https://www.poloniex.com/exchange#btc_flt
Why not trade there?

Cryptsy's wallet is in maintenance mode.

Upd: Back online.

During August, average trading volume on Cryptsy is a little bit higher than 100k HBN per week.

Already works.

I don't see your buy order on Cryptsy

Selling 2MS at 0.12 btc/m

Selling 2MS at 0.12btc/m

Selling 3ms at 0.135btc/ms

Selling 2m at 0.135btc/m

Selling few millions at 0.15btc/m