Quote from: Doftorul on March 25, 2018, 09:01:45 PM

Great to see a new OSS project and a brave dev making it open source.

Thanks. Not sure I'll be considered the brightest dev for making it open source, but I'll take 'brave' for now. 🤔

Quote from: Doftorul on March 25, 2018, 09:01:45 PM

In order to get more traction it would be useful to handle worker names transparently, that is presenting to the upstream pool each and every worker name behind the proxy. Sometimes, when you have 20 workers, you'd need to somehow check their hash stats with the pool.

Good news! Let's get ready for traction! Although not currently documented (my bad, sorry), it already is able to do this. It just requires a minor change in the config. This line of code extracts the worker name from the miner's authorization and appends it to the config file's pool account name, but ONLY IF the config's pool account name doesn't already have a worker name set.

My examples in the original post have ".rig1" in the account_name settings (see the following):

Code:

proxies:
- worker_class: aiostratum_proxy.protocols.equihash.EquihashWorkerProtocol
  pool_class: aiostratum_proxy.protocols.equihash.EquihashPoolProtocol

  listen:
  - host: ''
   port: 10666

  pools:
  - host: pool2.btcprivate.org
   port: 3032
   account_name: b1CACK65UTwzmHGw2VvyozdPsRLMb8utGLg.rig1
   account_password: x

If ".rig1" is removed from that line, aiostratum-proxy will pull the worker name from the miner's authorization - so, like this instead:

Code:

proxies:
- worker_class: aiostratum_proxy.protocols.equihash.EquihashWorkerProtocol
  pool_class: aiostratum_proxy.protocols.equihash.EquihashPoolProtocol

  listen:
  - host: ''
   port: 10666

  pools:
  - host: pool2.btcprivate.org
   port: 3032
   account_name: b1CACK65UTwzmHGw2VvyozdPsRLMb8utGLg
   account_password: x

At least, it should!

~~I will update the original post to describe this~~ Updated! Thank you for pointing it out.