Prohashing Mining Pool Forums

Can no longer solo mine after switching from one coin type to another.

Help section says there are limits to switching coins, but i cant imagine hitting the limit after switching from one solo coin to another over the span of a few days.

Since i can't do much because i don' have the right permissions to private message or chat with other users: I was soloing Digibyte then swapped to BitcoinScrypt and that's when it failed.

Now no matter what I try to solo mine, my antminers show a 'dead' status until i remove the coin arguments.

I suspect this has to do with the fact that my S9's were solo mining coin1 and my L3's were solo mining coin2 and that triggered something on prohashing side to block my connections with coin arguments.

FWIW, I'm fairly confident this is a deliberate block from prohashing, automated or manual.

BitcoinScrypt had an un-announced fork with little to no notice, so it was taking OFFLINE

can read more here:
viewtopic.php?f=13&p=22868#p22868

Until fixed it just wont be minable, after the server upgrades Tuesday when pool is offline for 12 hours.
Maybe a week after that Steve said.

Apexseals wrote:Since i can't do much because i don' have the right permissions to private message or chat with other users: I was soloing Digibyte then swapped to BitcoinScrypt and that's when it failed.

Now no matter what I try to solo mine, my antminers show a 'dead' status until i remove the coin arguments.

I suspect this has to do with the fact that my S9's were solo mining coin1 and my L3's were solo mining coin2 and that triggered something on prohashing side to block my connections with coin arguments.

FWIW, I'm fairly confident this is a deliberate block from prohashing, automated or manual.

This issue is caused by BitcoinScrypt, not by solo mining.

BitcoinScrypt had a fork and the developers provided less than 24 hours' notice, costing the pool hundreds of dollars. It will take about 7 days to get all of its blocks, to reindex its block explorer, and to resume mining.

Steve Sokolowski wrote:

Apexseals wrote:Since i can't do much because i don' have the right permissions to private message or chat with other users: I was soloing Digibyte then swapped to BitcoinScrypt and that's when it failed.

Now no matter what I try to solo mine, my antminers show a 'dead' status until i remove the coin arguments.

I suspect this has to do with the fact that my S9's were solo mining coin1 and my L3's were solo mining coin2 and that triggered something on prohashing side to block my connections with coin arguments.

FWIW, I'm fairly confident this is a deliberate block from prohashing, automated or manual.

This issue is caused by BitcoinScrypt, not by solo mining.

BitcoinScrypt had a fork and the developers provided less than 24 hours' notice, costing the pool hundreds of dollars. It will take about 7 days to get all of its blocks, to reindex its block explorer, and to resume mining.

probably should also mention here that mining bitcoincashSV is not possible to to error "The coinbase address for this daemon is invalid."