Mining software BzMiner v100.70, released November 5, 2026, adds automatic proof-of-work algorithm switching controlled by MoneroOcean, an exchangeable-coin mining pool that pays participants in Monero (XMR). Instead of manually reconfiguring graphics cards whenever relative mining rewards change, participating rigs can tell the pool which algorithms they support and accept new work selected by the pool. The mechanism is documented in the signed official GitHub release and the developer’s project website.

GPU mining and Bitcoin ASIC mining are distinct operations. Graphics cards can run several programmable hash or proof-generation workloads; modern Bitcoin SHA-256 mining is dominated by dedicated ASICs. Switching a GPU among supported altcoin algorithms does not mean BzMiner has found a competitive way to mine Bitcoin on a consumer graphics card.

The pool chooses the active workload

The update uses -a mo to establish a MoneroOcean pool connection. BzMiner first advertises the algorithms its devices can run, together with their measured hashrates. Each mining job then identifies the algorithm MoneroOcean currently considers most rewarding, and the software changes workloads accordingly. The selection is pool-directed; no local electricity-price optimization is built into the new decision.

The default candidate set includes KawPow, Ergo, Etchash, CryptoNight-GPU, Pearl and C29. RandomX is omitted by default because allocating its large dataset can leave GPUs idle. The user may opt it in, but a separate CPU-only pool connection is generally more appropriate for RandomX. To let a CPU and GPUs work independently, the developer’s examples use two mo connections, with different device and algorithm lists.

The distinction matters: algorithm switching is not simultaneous dual mining. BzMiner also has a separate Pearl-plus-C29 mode that can run workloads together. One MoneroOcean connection picks one algorithm at a time for its assigned devices. The separate Quantus GPU-pool expansion covered by BitcoinVersus.Tech illustrates a fixed-algorithm alternative.

Benchmark caching aims to limit interruptions

The first run measures algorithms lacking recorded rates and saves results to mo-perf.json, indexed by each card’s PCI identifier. Subsequent launches reuse a matching benchmark if the relevant overclock settings are unchanged. Changing a selected profile triggers a fresh measurement for the affected hardware and algorithm. Users can also disable new measurements and offer only previously cached values.

Actual profitability still depends on power draw, cooling, pool fees, developer fees, rejected shares, market liquidity and exchange rates. BitcoinVersus.Tech’s Bitcoin-versus-Monero efficiency analysis examines why different proof-of-work systems cannot be compared merely by hashrate units. A pool-estimated higher reward can still yield lower net revenue after electricity.

New Pearl optimizations still need independent tests

The same release claims improved Pearl mining performance and efficiency on NVIDIA Ampere, Ada and Blackwell cards and AMD RDNA 4 hardware, plus a fix for GPU hashrate not appearing in some MMPOS dashboards. The maintainers publish no standardized, independently reproduced before-and-after wattage table for the update. An increased share rate alone does not prove improved joules per accepted share.

BzMiner offers Windows, Linux and Apple Silicon archives and publishes SHA-256 download checksums. Operators should obtain binaries from the maintainer’s verified release page, check their matching digest and preserve existing profiles before changing fleet-wide configurations. BitcoinVersus.Tech’s guide to mining-pool communication protocols explains why a healthy link and accepted shares matter independently of the displayed local speed.

For pool earnings, payout rules also matter. The PPLNS pool-reward explainer shows why short test windows can misrepresent actual rewards. MoneroOcean’s XMR-denominated payments and switching choices require their own accounting. Miner operators should compare wall-power consumption and real credited XMR over consistent intervals before accepting any profitability claim.

The verifiable development is the November 5 software release and its documented switching protocol. Neither live earnings improvements nor fleet-wide stability gains were independently demonstrated. The practical question is whether a particular rig’s measured net results improve after the pool begins choosing its work.

Editor’s Note: Primary verification used the BzMiner v100.70 GitHub release dated November 5, 2026, the BzMiner project website, and MoneroOcean’s pool homepage. The release specifies the candidate algorithms, mo-perf.json caching, separate CPU/GPU connections and claimed Pearl optimizations. The description does not constitute independent mining, energy or profitability testing. The BzMiner GitHub project graphic and a separately credited MoneroOcean directory image identify the services; neither depicts a measured November 2026 mining run. The December 2021 Rabid Mining video is background on an older CPU workflow and does not demonstrate v100.70. Saved video embedding, live playback and device-level desktop/mobile rendering are separate verification stages.

To donate 5,000 sats, display the original Bitcoin QR on another screen and scan it with a compatible wallet. On mobile, use a second display or the wallet’s supported saved-image scanning option. Confirm the receiving address 3C9o19EH5HSiwEPyCTmEKzxhNCbo2X6TTb before transferring Bitcoin.

We volunteer daily to ensure the information on this platform is Verifiably True. If you would like to support the research, please scan QR code.

BitcoinVersus.Tech is not a financial advisor. Mining software, algorithm switching and cryptocurrencies involve hardware, operational, financial and security risks. Coverage is informational, not investment advice.