ZCL: t1db2oUE7DN9Vg7UZKRQU6E2sCUqY2FL2js

BTCP: b1FMogUzN9dYdxody8T6Ru3zZrYuo7bLtor

Thanks for the updates Oliver!

So to clarify, my 2.693M shares from ZClassic will count as shares for BTCP? Will those shares count and get paid for even if I don't mine on the BTCP pool? I wan't to make sure I'm able to get those shares if possible since its alot of shares.

Thanks

I do appreciate this, I was sad (and kinda expected), that the ZCL pool wouldn't find a block before the fork happened. How will the merge happen? Will the existing miners stop and need to connect to the BTCP pool with a new address?

Thanks for the info!

Yeah just tried again and the zm miner atleast established a connection again..I can't for the life of me figure out these connection issues.

This seems like something on the CoinFoundry end, every machine running the zm miner (bminer wouldn't work) stopped at the same time saying "server closed the connection r:2" and now won't connect to any of the ports...

I know you are busy Oliver but hopefully you can check into this recurring problem. Thanks.

Even after working for me for awhile, it will lose connection with these kind of errors. I just don't wanna risk any of the downtime.

Another update, these are the kind of errors I get from mining.. Ive been mining all day and then it will run errors for awhile then connect itself back to the pool sometimes, and other times it never does. So until I can figure out something more stable, i'll have to wait on moving my hash power back over to this pool.

UPDATE:

As of right now using the bminer, the ports 3122 & 3123 has decided to start working for me... I tested it on 2 of my machines and they both started receiving jobs. I'm going to leave it running on 1 of my smaller machines to test it over night before I apply it to the rest.

Still don't understand why port 3124 still isn't working but this is a start atleast.

For the coinfoundry support, here is what my miners .bat file looks like (I originally connected to port 3124 but the other ports won't connect either):

bminer: 

@echo OFF

REM Change the following address to your Zcash taddr.

SET ADDRESS=t1db2oUE7DN9Vg7UZKRQU6E2sCUqY2FL2js
SET USERNAME=%ADDRESS%.w
SET POOL=zcl.coinfoundry.org:3123
SET SCHEME=stratum

START "Bminer: When Crypto-mining Made Fast" Bminer.exe -uri %SCHEME%://%USERNAME%@%POOL% -api 127.0.0.1:1880

zm_0.5.8_win (downloaded from the setup generator):

zm.exe --server ssl://zcl.coinfoundry.org --port 3123 --user t1db2oUE7DN9Vg7UZKRQU6E2sCUqY2FL2js.RB

@echo off
REM Usage:
REM  zm --server hostname --port port_nr --user user_name
REM     [--pass password] [options]...
REM
REM  Stratum:
REM     --server         Stratum server hostname
REM                      prefix hostname with 'ssl://' for encrypted
REM                      connections - e.g. ssl://mypool.com
REM     --port           Stratum server port number
REM     --user           Username / Workername
REM     --pass           Worker password
REM
REM  Options:
REM     --help           Print this help
REM     --dev            Space separated list of cuda devices
REM     --list-devices   List available cuda devices
REM     --time           Enable output of timestamps
REM     --logfile        [=path] Append logs to the file named by 'path'
REM                      If 'path' is not given append to 'zm.log' in
REM                      current working directory.
REM     --noreconnect    Disable automatic reconnection on network errors.
REM
REM     --temp-target    In C - If set, enables temperature controller.
REM                      The workload of each GPU will be continuously
REM                      adjusted such that the temperature stays around
REM                      this value. It is recommended to set your fan speed
REM                      to 100% when using this setting.
REM
REM     --telemetry      [=ip:port]. Starts telemetry server. Telemetry data
REM                      can be accessed using a web browser(http) or by json-rpc.
REM                      If no arguments are given the server listens on
REM                      127.0.0.1:2222 - Example: --telemetry=0.0.0.0:2222
REM                      Valid port range [1025-65535]
REM  Example:
REM     zm --server servername.com --port 1234 --user username

Hopefully this helps the next time you are able to look at this.

Thank you for your time and efforts.