Considering removal of "a=" password argument

As part of my effort to simplify the codebase and eliminate edge case bugs that could cause lower profitability, I was considering removing the "a=" password argument. Customers would instead be required to connect to an algorithm-specific port. Additionally, the port 443 proxy server would be discontinued, since the "a=" password argument is required for its use.

Prohashing primarily used the "a=" password argument until 2017, when algorithm-specific ports were introduced because some algorithms don't follow the stratum protocol specification.

Would you be affected by this change?

It was always confusing for me, should I use password or something else, seems like it made creating .bat for miner more complicated and unlike on other mining pools. Simplifying it is a +

I don't use the "a=" argument so my miners would not be affected by this change.

bMeister1 wrote: I don't use the "a=" argument so my miners would not be affected by this change.

Banished_Privateer wrote: It was always confusing for me, should I use password or something else, seems like it made creating .bat for miner more complicated and unlike on other mining pools. Simplifying it is a +

How do you feel about the 443 proxy server?

I don't think it would impact me.

Same here. I have never used the proxy server; I just use the algorithm-specific ports. I should also amend my statement about using the "a=" argument as it appears the bat files I have to run equihash-144_5, KAWPOW, and Ethash-LowMemory use it but also while using their respective algorithm-specific ports. But if I understand how this change would work, the "a=" argument becomes unnecessary because it knows what algorithm to use based on the port the miner is connected to, correct? That would then mean that I use it but I don't actually need it for anything.

bMeister1 wrote: Same here. I have never used the proxy server; I just use the algorithm-specific ports. I should also amend my statement about using the "a=" argument as it appears the bat files I have to run equihash-144_5, KAWPOW, and Ethash-LowMemory use it but also while using their respective algorithm-specific ports. But if I understand how this change would work, the "a=" argument becomes unnecessary because it knows what algorithm to use based on the port the miner is connected to, correct? That would then mean that I use it but I don't actually need it for anything.

Correct. The algorithm specific port eliminates the need for the a= argument.