Status as of Friday, January 11, 2019

Discussion of development releases of Prohashing.
User avatar
Steve Sokolowski
Posts: 3377
Joined: Wed Aug 27, 2014 3:27 pm
Location: State College, PA
Contact:

Status as of Friday, January 11, 2019

Postby Steve Sokolowski » Fri Jan 11, 2019 11:09 am

Good morning! This past week's work has again focused on reliability and stability.

  • I discovered another memory leak that, unfortunately, is not the cause of the servers crashing every five days, but which will help. There are a lot of miners who connect to the system and never submit any shares, for an unknown reason. These miners would hold old data they were mining in memory indefinitely. Now, after 4 hours of not submitting any shares, the mining data will be deleted and these miners' next share will be rejected and cause a work restart to be sent so they can resume mining.
  • The Lyra2REv2 version of Verge uses scrypt hashes to identify its blocks, unlike most other coins. This limitation was causing all Verge Lyra2REv2 blocks to be identified as "Lost," despite that these blocks were actually found, and the pool excluded Verge from mining. Now, the system will automatically determine the algorithm these blocks use for their block has. The automatic detection will also correct mistakes previously made by Chris in incorrectly identifying block hash algorithms.
  • There were a few website bugfixes. One involves spacing between boxes. Constance is working on more bugfixes and corrections to be released this weekend.
  • Vance is finishing up with support for USDC and Tether. He expects them to be available early next week.
User avatar
dnprod
Posts: 69
Joined: Tue Feb 21, 2017 3:19 pm
Location: Ontario, Canada

Re: Status as of Friday, January 11, 2019

Postby dnprod » Fri Jan 11, 2019 7:54 pm

i know my miners connect without share submissions sometimes, depending on my priorities that day :)

cgminer program allowes for 'quota' style mining, you can set a pool with zero quota to behave as a 'fallback' instead.
but it appears cgminer connects right away and holds the connection just in case it ever needs to switch to it.

even without quotas, cgminer probably does this for 'fallback' pools, been too long since i've used cgminer without quotas
so i dont recall.
it wouldn't even suprise me if most mining software does this sort of thing for 'fallback' pools.

bitmain's asics use cgminer, and i adjusted the web configuration scripts to allow me to set quotas. when mining an obscure very low diffiulty altcoin directly it is necessary to avoid too much horsepower or you'll just end up soft forking on that coin. i sometimes have my miners doing all kinds of things at the same time :) sub optimal for profit, but fun to support coin names that amuse me.

Who is online

Users browsing this forum: No registered users and 2 guests