Comment
Author: Admin | 2025-04-28
A bug that caused the miner to enter re-connect routine when one endpoint of a Ton - pool did not work, although other endpoints did connect well (That in combination with the previous one was root cause for most Ton errors in Windows we recently had).Fixed a bug with icemining.ca Ton stratum not sending correct job id when dual mining on AMD cards.Fixed a bug with json style configuration not working with dual mining in 1.43 release version.Temporarily disabled the ZIL cache function on AMD GPUs, because it sometimes did not swap clearly. We will bring this back as soon as possible.Example for --dualdevices and --maxdualimpactConsider a 6 card rig with --dualdevices 4,5 --maxdualimpact 0,0,*,*,*,*This rig will mine:Eth only on GPUs 0 & 1 (ton dual mining disabled by maxdualimpact)Eth + Ton on GPUs 2 & 3Ton only on GPUs 4 & 5 (eth mining disabled by dualdevices)lolMiner 1.38ChangesAdded DNS over HTTPS name resolving for establishing your pool connection. This has advantages when your normal DNS resolving might be blocked or modified by a firewall. You can control its behavior with the parameter --dns-over-https value with the values 0: turns DNS over HTTPS off; 1: DNS over HTTPS is enabled, fallback to normal DNS resolving is possible (default); 2: enforcing DNS over HTTPS, normal DNS is completely disables (1)Updated internal libraries for TLS connection handlingMoved more fee pools to use TLS connection. When mining Ethash, Etchash (both +ZIL), Ergo and Beam the fee connection is now always encrypted (TLS 1.2)
Add Comment