Keryx prepares for H15: Windows NVIDIA miners need the 0.15.2 fix
Source report: 2026-10-28 · Editorial analysis published: 2026-10-30
The October 28 hotfix repairs model loading on Windows NVIDIA ahead of the H15 gate expected around October 30. Activation depends on mainnet DAA score 140115000, not a wall-clock alarm.
The important deadline is in the mining job
Keryx’s H15 transition is tied to mainnet DAA score 140115000. The project estimated October 30 around 15:00 UTC, or 17:00 in Kyiv, but its release notes explicitly say the mining software switches according to the DAA value in each job, not the computer clock. DAA is a chain-progress score here; the published time is an estimate rather than the activation rule.
The practical update includes keryx-miner-supr 0.15.2, published October 28 at 17:13:09 UTC. It repairs a Windows NVIDIA problem discovered in 0.15.0 and 0.15.1. This is Keryx GPU and Proof-of-Model mining software, not a new Bitcoin ASIC firmware or a universal upgrade for other PoW coins. Our report retains the release date and describes preparation for the gate without claiming an independently observed activation.
A Windows library prevented every model from loading
The author says the Windows NVIDIA package lacked exported H15 trace, replay and context functions in its engine DLLs, dynamic libraries loaded by the program. As a result, no model could load, and the software reported missing H15 symbols. Version 0.15.2 exports the required functions from the two relevant engine libraries and adds a packaging check for them.
The release says Linux, Hive OS, mmpos, SMOS, AMD, macOS and Docker retain the same code as 0.15.1, with a version change only. That statement is about this Windows packaging fix. It does not mean every listed platform can perform post-H15 work: the separate platform notes describe a remaining AMD and Apple Silicon limit.
Old headers can make discovered blocks invalid
Node 1.6.6 removed the H15 block-task root from the block header. Miner 0.15.0 would still include it after the gate, so the author warns every block it finds then would be invalid. Versions 0.15.1 and 0.15.2 use the header format matching the node. This is a compatibility issue affecting useful work, not a small speed difference that can be judged only from a local hashrate display.
Node operators, pools and exchanges are separately told to use keryx-node 1.6.6 before H15. The node release says older versions will not follow the post-H15 chain and older peers will be refused after activation. Updating a GPU client does not update the pool’s node automatically, just as updating the node does not repair the client’s Windows DLLs. Confirm the component you actually operate.
NVIDIA support does not remove the AMD and Metal limitation
The platform notes list full H15 support for NVIDIA packages. AMD OpenCL/Vulkan and Apple Silicon Metal implementations do not yet have the required PoM v5 context pad. The release says they mine normally before the gate and then idle with a warning instead of producing work that cannot become a valid block. The Windows hotfix does not announce that this separate limitation has been resolved.
For an owner, that difference changes the maintenance decision. Selecting an archive labelled AMD or macOS does not prove it will keep mining through H15. Check the platform-specific notes and the work actually accepted after the job’s DAA crosses the gate. No hashrate, wattage saving or daily-profit increase is supplied for this fix, and we did not install or benchmark the miner.
Smaller submissions and memory headroom are separate changes
The release carries forward a supported-pool option to send proofs in base64 rather than hexadecimal, reducing a cited H15 proof from roughly 975 KB to 650 KB. This is about one-third less upload for that submission, not one-third less electricity or a one-third larger reward. Pools without the capability still receive hex; after a refused base64 submission the share is rejected, the connection stays up and subsequent submissions use hex for that pool.
Automatic tier selection also leaves about 2 GiB of video-memory headroom on GPUs shared with other processes. That can avoid choosing a model that barely fits and then fails to load; it does not add physical memory to the card. The update also corrects per-GPU monitoring under CUDA_VISIBLE_DEVICES by matching cards through their PCI bus IDs, helping an operator read the devices actually assigned to the worker.
Before maintenance, keep the working configuration and choose the package matching hardware and driver. Use the release’s matching SHA256SUMS file to check the download; a checksum is a file-integrity check, not a substitute for trusting the source. The release’s automatic gate switch needs no additional restart or pool, wallet or model change once compatible software is running; installing the update itself remains a normal maintenance step.
The clearest post-change observation is a compatible running version, successful model loading and accepted work for the actual chain state. A working user interface or local speed counter alone does not establish all three. Follow the project’s current release notes rather than treating the approximate October 30 time as proof that an old client has already switched correctly.
Source: Keryx / keryx-miner-supr ↗ · Node 1.6.6 mandatory H15 release ↗ · Previous miner 0.15.1 and Windows warning ↗ · Project technical description ↗
Mining calculator ↗
