SHA-256 Asicboost connection still supported?

Having trouble getting SHA-256 Asicboost to connect and hash, using: stratum+tcp://eu.prohashing.com:3335 & my password arguments are: c=bitcoin,m=pplns

Am I potentially missing anything else? Thanks!

Looks like this might have been an issue with overall rig configuration, but leaving this thread open just in case there are other password arguments required that I didn't set.

The best choice is to use the "i=" password argument, in addition to the others you've already selected, to allow the mining servers to determine the best settings based upon the type of mining rig. You can use the "Worker Configurator" page to select your mining rig type from the list.

Steve Sokolowski wrote: The best choice is to use the "i=" password argument, in addition to the others you've already selected, to allow the mining servers to determine the best settings based upon the type of mining rig. You can use the "Worker Configurator" page to select your mining rig type from the list.

Following up on this, I was experimenting with a high difficulty rig rental from MRR that had a recommended diff of 500k. Rig owner suggests it was a pool work difficulty issue. Does this sound accurate?

azereki wrote:

Steve Sokolowski wrote: The best choice is to use the "i=" password argument, in addition to the others you've already selected, to allow the mining servers to determine the best settings based upon the type of mining rig. You can use the "Worker Configurator" page to select your mining rig type from the list.

Following up on this, I was experimenting with a high difficulty rig rental from MRR that had a recommended diff of 500k. Rig owner suggests it was a pool work difficulty issue. Does this sound accurate?

The system will assign miners to difficulties of 500k or even higher eventually, but starts with a lower difficulty. Just omit the "d=" password argument and you'll be assigned a higher difficulty.

We would love to help you if you connect directly to Prohashing, and you can feel free to create a support ticket if you plan to do that. However, we aren't able to provide support for cloud mining services, as we've found that much of the hashrate on these services is involved with criminality and fraud. While MiningRigRentals is not outright banned like Nicehash, you can eliminate the problem you're having and get support by simply connecting directly to Prohashing.

None of my ASIC's running Sha-256 will connect to the pool if I try to mine with the "c=bitcoin" argument. My miners show that the pool is dead if I use that argument. If I remove the "c=bitcoin" argument then they will all connect to the pool. I'm using Bitmain and Ebit miners. I tried both with and without the "i=" argument, made no difference.

Steve Sokolowski wrote: While MiningRigRentals is not outright banned like Nicehash, you can eliminate the problem you're having and get support by simply connecting directly to Prohashing.

Ah, that's good to know, thanks! I actually discovered them on this ProHashing page and thought they were vetted, so decided to try it out: https://prohashing.com/help/prohashing-charts-statistics#services

azereki wrote:

Steve Sokolowski wrote: While MiningRigRentals is not outright banned like Nicehash, you can eliminate the problem you're having and get support by simply connecting directly to Prohashing.

Ah, that's good to know, thanks! I actually discovered them on this ProHashing page and thought they were vetted, so decided to try it out: https://prohashing.com/help/prohashing-charts-statistics#services

Mining Rig Rentals is not like Nicehash in that Mining Rig Rentals investigates criminal activity and attempts to police its services, while Nicehash simply allows criminals to conduct 51% attacks and connect low-luck miners while turning a blind eye.

However, the cloud mining rentals business model is fundamentally flawed, and Mining Rig Rentals is engaged in a business where one of the major reasons to rent is criminality. It's difficult for them to prevent abuse in advance, which is why we always advise direct connections. Another reason we advise direct connections is that we can't see into cloud mining services' systems to troubleshoot problems, and that's why we don't provide support to non-direct miners.

steve_empire wrote: None of my ASIC's running Sha-256 will connect to the pool if I try to mine with the "c=bitcoin" argument. My miners show that the pool is dead if I use that argument. If I remove the "c=bitcoin" argument then they will all connect to the pool. I'm using Bitmain and Ebit miners. I tried both with and without the "i=" argument, made no difference.

Bitcoin is currently only available for PPLNS and SOLO mining. Attempting to static FPPS mine Bitcoin could cause this issue.

[/quote]Bitcoin is currently only available for PPLNS and SOLO mining. Attempting to static FPPS mine Bitcoin could cause this issue.
[/quote]

Thanks for the info, I'll try it out when I get a chance...