Read-only forum archive. PROHASHING has closed. Posting, registration, and account access are unavailable. Preserved from the April 3, 2026 server backup.
I am relocating my mining operation and in the meantime I wanted to change my proportions and coin for payout. All miners were shutdown on Nov 11th and there is still a balance that has not been paid out yet. Why is this?
Mastermind007 wrote: I am relocating my mining operation and in the meantime I wanted to change my proportions and coin for payout. All miners were shutdown on Nov 11th and there is still a balance that has not been paid out yet. Why is this?
Did you set the payout threshold to zero, so that the entire balance is paid? Keep in mind that you’ll be charged the network transaction fees, and for ETH in particular, those fees can cost a lot recently
Mastermind007 wrote: I am relocating my mining operation and in the meantime I wanted to change my proportions and coin for payout. All miners were shutdown on Nov 11th and there is still a balance that has not been paid out yet. Why is this?
Did you set the payout threshold to zero, so that the entire balance is paid? Keep in mind that you’ll be charged the network transaction fees, and for ETH in particular, those fees can cost a lot recently
I only have Coinbase payouts which I thought had no threshold.
Even after the turned my Coinbase payout back on it looks like the payout balance is still unpaid. Not sure is this is a sign of a larger issue. Don’t often get the chance to see this as miners usually don’t go offline for days, allowing the balance to drop to zero. It will be a dew days before I am back up and running. Hopefully that is enough time to figure this out. It is not a lot of money but if it is happening a lot it could mess up the accounting books.
Looks like things are processing through. XTZ is the only coin left that has not. May be a good idea to add a payout change to the alert options or something specific to Coinbase if they drop OAuth from time to time. It was just dumb luck I happen to notice it.
Kaffiend wrote: does gminers not work? i still have not tried setting it up for eth
It works great for actual mining but whenever Prohashing’s servers have these issues and just closes the connection, Gminer just endlessly reattempts to connect after the server closes the connection instead of failing over to a backup pool. It seems unique to the "Connection Closed" error as any other connection error triggers failover as expected.
Even more strange is the fact that one rig might failover properly while the other spins its wheels until I force it to run on a different pool. It’s honestly my only gripe with Gminer cuz when the failover code works, it works great. But for whatever reason, it just doesn’t like the way Prohashing handles server issues.
The XTX balance has yet to payout. I thought for certain a day have I reenable the Coinbase connection it would have processed. It is not much, a little over 1 USD but my OSD kicks in whenever something does not work as it should.
I am hoping it is just the status page not updating correctly as it looks like the number of found blocks has dropped to one or two Verge or Callisto instead of the usual blocks flying by quickly. Been busy and have not been monitoring things so forgive me if this has been discussed already.
etchash doesn’t have a low memory. If you mean Eth-low memory, check the dag sizes and set your c value to that coin. It doesn’t seem to pay attention to the l= perameter
Alynn wrote: etchash doesn’t have a low memory. If you mean Eth-low memory, check the dag sizes and set your c value to that coin. It doesn’t seem to pay attention to the l= perameter
’A share has not been submitted for the worker. The current algorithm could be too difficult for the worker. If a CPU or GPU is being used to mine, look at the CPU and GPU quick start guides for recommend algorithms to mine.’
is there a comma between lowmemory and the c in your password? This could also simply be that your machine is a little slow and hasn’t submitted enough shares. If it shows it hashing, that error will go away after some time.
Alynn wrote: is there a comma between lowmemory and the c in your password? This could also simply be that your machine is a little slow and hasn’t submitted enough shares. If it shows it hashing, that error will go away after some time.
There is now, thanks. Ill let it run, see what happens.
something doesnt seem right but ill leave it go for a bit.. i had been mining Expanse just fine for months on same algorithm but can’t get any accepted shares doing static on any of the other coins
Setvin wrote: I have the issue of certain workers disconnecting im not sure if its just because so long between share submits its recognizing as a new device lol
Setvin wrote: I have the issue of certain workers disconnecting im not sure if its just because so long between share submits its recognizing as a new device lol
It happens to me a lot. Sometimes it’s worse than other times. When it gets bad I mine at another pool.
Setvin wrote: ok so its not just me... its been really bad the last week.
We’re not aware of any widespread issues in regards to Internet connectivity right now, but you can feel free to submit a support ticket if you’d like and we’ll be glad to investigate your specific issue.
The reason I think its just the time between shares has increased is because I dont really see a change in profits or shares subbmited, like the total ammount is accurate but it keeps creating new workers as if the connection reset