Prohashing Mining Pool Forums

Equihash mining is now available. The website was updated so that the documentation describes how to connect.

There are only two issues right now. The first is that Chris cannot 100% certify that profits are being credited correctly here because there haven't been enough shares in production yet. He'll be able to confirm that after more miners join; it already worked in development. The second is that the profitability at the top of the forums is in MS/s, just as the X11 profitability is in MH/s; both of those will be changed tomorrow.

Good luck! Feel free to offer comments, and I'll check back in a few hours to make sure there are no emergent bugs. If there are none, then Bitcoin Gold will come later this week, and SHA-256 mining after that.

Good work prohashing team, i'm moving my miners across, will see what the profit is like in 24 hours!

I'm getting a lot of rejected shares see below, 2 pages worth now, i'm using smos with dstm 0.5.8

Miner did not respond to difficulty change request quickly; share of diff 10010.8632463 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 10089.0572232 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 10570.9234936 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 12847.7189926 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 13105.3689681 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 13135.3223604 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 13288.9551154 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 13929.9668299 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 13984.3704892 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 15200.3121775 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 8289.73390492 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 9351.54768891 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 9565.04834568 is too easy for assigned difficulty 16384.0 20

Hashrate is also dropping slowly with a 70% efficiancy

I have had a constant 4.7K at another pool for months and it is showing 3K total here

miner log below showing an unknown method for difficulty

# GPU2 GeForce GTX 1060 3GB MB: 3013 PCI: 3:0
# GPU3 GeForce GTX 1060 3GB MB: 3013 PCI: 4:0
# GPU4 GeForce GTX 1060 3GB MB: 3013 PCI: 5:0
# connected to: prohashing.com:3333
unknown method mining.set_difficulty
invalid message received
# server set difficulty to: 000800000000000000000000...
# server supports extranonce

What mining program did you test with?

djliss wrote:Hashrate is also dropping slowly with a 70% efficiancy

I have had a constant 4.7K at another pool for months and it is showing 3K total here

miner log below showing an unknown method for difficulty

# GPU2 GeForce GTX 1060 3GB MB: 3013 PCI: 3:0
# GPU3 GeForce GTX 1060 3GB MB: 3013 PCI: 4:0
# GPU4 GeForce GTX 1060 3GB MB: 3013 PCI: 5:0
# connected to: prohashing.com:3333
unknown method mining.set_difficulty
invalid message received
# server set difficulty to: 000800000000000000000000...
# server supports extranonce

What mining program did you test with?

You can ignore that set_difficulty issue. It will have no effect. We need to send it initially because we don't know what algorithm the miner wants to use until it sends its password arguments.

djliss wrote:I'm getting a lot of rejected shares see below, 2 pages worth now, i'm using smos with dstm 0.5.8

Miner did not respond to difficulty change request quickly; share of diff 10010.8632463 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 10089.0572232 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 10570.9234936 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 12847.7189926 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 13105.3689681 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 13135.3223604 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 13288.9551154 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 13929.9668299 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 13984.3704892 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 15200.3121775 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 8289.73390492 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 9351.54768891 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 9565.04834568 is too easy for assigned difficulty 16384.0 20

Could you try using "d=16384" or some other value to set a static difficulty and see whether that resolves your issue?

Steve Sokolowski wrote:

djliss wrote:I'm getting a lot of rejected shares see below, 2 pages worth now, i'm using smos with dstm 0.5.8

Miner did not respond to difficulty change request quickly; share of diff 10010.8632463 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 10089.0572232 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 10570.9234936 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 12847.7189926 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 13105.3689681 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 13135.3223604 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 13288.9551154 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 13929.9668299 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 13984.3704892 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 15200.3121775 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 8289.73390492 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 9351.54768891 is too easy for assigned difficulty 16384.0 20
Miner did not respond to difficulty change request quickly; share of diff 9565.04834568 is too easy for assigned difficulty 16384.0 20

Could you try using "d=16384" or some other value to set a static difficulty and see whether that resolves your issue?

The only problem is i haven't been able to pass more than 1 password argument with any of the software, the first one i put in is a=equihash and any others are not passed through, i think the space is affecting it and the software is ignoring anything after it, even the n=rigname dosn't work and "a=equihash n=rig" just makes the rigs try mine scrypt because of the a= not being passed through

About 12% of shares are being rejected for that reason you state. That's way too high, so I'm going to disable Equihash mining for now and Steve will fix it when he wakes up in the morning.

I am using awesome miner and it handles the arguments ok when enclosed with quotes. I think someone was having problems on chat with a web-based GUI that sounds like it was encoding the quotes or just stripping them.

I can't get either Claymore Zcash or Optiminer Zcash Windows versions to work on a rig with 1 AMD GPU. Both of them throw errors indicating that pool is sending invalid or wrong data.

Anyone have any command line suggestions for AMD cards that work?