I have switched, as requested, but am unsure of the fate of my remaining Bitcoin balance.

No change with d=256 In Help I see: "One of the limitations of the protocol is that while it can receive work from many miners on a single connection, it cannot direct work to those miners individually. When work is sent to a single Stratum connection, all mining rigs and all users authorized o...

Only arguments - n=workername a=x11

The worker connected successfully.

We changed antminer-configured password - reset the box using software reset. Will not reconnect.

First D3 plugged in alongside L3+ that have been mining well. Connected successfully, reset to change password configuration, now getting only socket connect refused.

Is there some issue with X11 pool connectivity that is known? Is there some reset/reboot procedure I need to adhere to for this pool?

Notifications that can be set based on worker parameters instead of account - accepted hashrate/idle notifications per-worker.

Detailed account/transactions page with earnings/payouts/fees paid for the account - sortable/filterable by algorithm (or even per-worker would work). If that page could also include a per-coin USD/EUR/etc value on the line items for the coin payout - would help in documenting cost basis for income ...

Steve,

Any idea on the timeframe to have acceptable reserves?

We'll have S9s delivered in JAN to supplement L3/D3 machines already running so we're trying to plan where they will point to.

Team,

I read a bit about possible SHA support and just wanted to understand if this was something simply slated for the future or if it was under active pursuit.

Thanks!

Essentially it sounds like that is calculating 'effective hashrate' vs 'working hashrate'.

Thanks for your help!

Cool, thanks.

I've been leaving difficulty dynamic, but know I need to assign X11 algo setting on the D3s.

Maybe support doc warning was outdated...?