

Please note that in both cases the miner should give you higher pool-side hashrate in the long run compared to previous versions. If you prefer to keep your power consumption constant, you can still set the power limit, however, in that case you'll notice a slight hashrate drop after each block. To take the full advantage of this mode it's recommended not to set power limit but instead limit power consumption with -lock-cclock - this will allow the miner to draw more power during dataset rebuild and not lose hashrate. If there is not enough memory on the GPU for two datasets, the miner will fall back to running in single buffer mode. Memory requirements are doubled in this mode as the GPU has to hold two memory buffers. The miner now generates the dataset for the next ERGO block before it arrives with a small penalty to reported hashrate, and when the next block does arrive, it immediately starts hashing without losing 1-4 seconds on creating the dataset. ( autolykos2) Increase pool-side hashrate by 1-4%.Temporary solution is to delete browser cookies. Known issues: WebUI shows a blank page if you had 15M or 2H graph views selected on the previous version. (WebUI) Log file retrieved through WebUI has trailing zeros.(Linux) Log file contains ANSI escape sequences.

Veriblock mining is broken since 0.24.2.( ethash) RTX 3060 GA104 is not recognised as an LHR card.Auto-propagation of the miner node list to all nodes.Ability to reorder/hide GPU table columns.Recompute average hashrate/power when zooming in the graph.

Ability to hide individual charts (power, avg hashrate etc.) on the graph.New -temperature-color-mem parameter to control memory temperature highlighting in console and WebUI.Add SOCKS5 proxy support (see -proxy parameter).( autolykos2) New -dataset-mode parameter to enable/disable double buffer mode: 1 - single buffer mode, 2 - double buffer mode (default).( ethash, firopow) Add ETH+FIRO dual mining (use the same OC settings as ETH+RVN).( ethash, autolykos2) New -lhr-autotune-step-size and -lhr-autotune-interval parameters for finer control of LHR unlock behaviour.

(in other words, for the first run, remove -lhr-autotune-mode and -lhr-tune parameters from your bat file if they are set) The new LHR tune scale is somewhat different, so it's recommended to let autotune find the optimal parameters
