nsacaddy.blogg.se -

So it has caused considerable problems for all of us - the miners, the operators of the pools and last but not least for me, for which I would like to apologize herewith. Even though the goal was of course to write a software that can handle all current pools and that is a suitable solution for all TON miners, I was surprised how well the software was accepted in the last days - and in the end it therefore became a victim of its own success due to the above mentioned problems. But in real use, this has caused significant problems on some mining pools for TON - effectively a DDOS by mining software. Unfortunately, this was not noticed during testing, as on a small scale there were no problems. For this reason I reused a piece of code that was already used for the DOH code, without considering that a direct copy of this approach will not be able to reuse an existing connection. When I started writing the mining software for TON I was quite aware of how the GPU code should look like, but the system to connect to the pools turned out to be much more difficult, respectively I was still very unfamiliar with the topic https. I would like to start this change log a little unusual, because I think it is only appropriate to apologize at this point. Fixed some general issues where Ton pools did not get connected.

Fixed a bug in statistics causing GPU number not to be right aligned in classical vertical stats.

Fixed a bug in Ton solver back ends, that rarely caused (double) defect shares to appear.

You still can get back to old vision via adding -vstats to your parameter set. Use parameter -mclk to do so, that will be only effective for TON mining at 810 value(requires admin / sudo permissions and Nvidia driver 470 series or newer) (1)

Added ability to lock the memory clock on Nvidia RTX 3000 series.

Also note you need a sufficient internet connection - the amounts of polls to the givers is higher then for a usual pool connection. Note that to solve a challenge per day, at the moment about 300 Gh/s are required. Every submitted share is equal to a submitted challenge solution to the network. During this mode the "Pool hashrate" and the "best share statistics" will show data based on an internal difficulty of about 4.4Th. In this mode the miner will get giver seeds and difficulty from the contracts directly from the public API and submit a found solution directly to the giver to pay you. In case the requests take too long the miner will make the request interval larger internally to ensure enough capacity is left on the line e.g. Additionally the pool connection module will now take statistics about the duration each request takes. This will reduce stales and rejected on pool.

Reduced Ton pool job polling intervals by default.