[ANN] ForgeMiner — Pearl (pearlhash) + QubitCoin (qhash) | NVIDIA

[0xHashRaptor]

ForgeMiner — Multi-Algo NVIDIA Miner — Pearl (pearlhash) + QubitCoin (qhash)

Native. Fast. Works on ANY pool. Windows · Linux · HiveOS · Docker.

ForgeMiner is a lightweight, native multi-algorithm NVIDIA miner — currently
Pearl (pearlhash) and QubitCoin (qhash), with more on the way. Competitive
hashrate, rock-solid stability, and — unlike some miners — it is not locked to a single
pool. Mine where you want.

──────── Supported ────────

• Algorithms: pearlhash (Pearl) · qhash (QubitCoin)
• GPUs: NVIDIA Pascal → Blackwell — P104-100 · RTX 20 / 30 / 40 / 50 · CMP
• OS: Windows · Linux · HiveOS · Docker
• Pools: any standard stratum pool — HeroMiners, Kryptex, Pearlfortune, AlphaPool, LuckyPool, …

──────── Why ForgeMiner ────────

• Hashrate on par with the top miners
• Works on every pool — no pool lock-in
• Multiple coins in one miner (Pearl + QubitCoin), more coming
• Fan control (fixed speed or temperature curve) and VRAM temperature monitoring
• 0-reject stability, fast startup, clean dashboard (24h avg, per-GPU stats)
• Transparent, per-algorithm dev fee (see below) — verifiable on your pool

──────── Benchmarks (TH/s per GPU) ────────
Vary with overclock/power.

Code:

RTX 5080       ~195
RTX 4070 Ti    ~122
RTX 3060 Ti    ~58
P104-100       ~6.5
(more cards — community-verified, post yours below)

──────── Download ────────
Releases (Windows / Linux / HiveOS):
https://github.com/0xHashRaptor/ForgeMiner/releases
Docker: docker pull hashraptor/forge (tags :1.1.12 and :latest)
Feel free to scan it on VirusTotal and post the link — we encourage it.

──────── Quick start ────────

Code:

forge --algorithm pearlhash --pool <host:port> --wallet <ADDR> --worker <name>
forge --algorithm qhash     --pool <host:port> --wallet <ADDR> --worker <name>

HiveOS: custom miner — set FORGE_ALGO=pearlhash (or qhash) in extra args.

──────── Dev fee ────────

• Pearl (pearlhash): 2%
• QubitCoin (qhash): 1%

Interleaved, so both your pool and the miner show a steady hashrate (no graph dips).
Stated openly and verifiable on the pool. No hidden fees, ever.

──────── Roadmap ────────

• KawPow (Ravencoin) — in active development
• More algorithms — built on a multi-algo core

──────── Support & community ────────
Telegram channel: @ForgeMiner  ·  chat: @ForgeMinerChat
Discord: https://discord.gg/4Uby3ZUZ

──────── Changelog ────────

• v1.1.12 — Pascal P104-100 Pearl support (up to ~7 TH/s); fan control; Windows VRAM temperature
• v1.1.11 — dedicated AlphaPool path (share crediting confirmed)
• v1.1.10 — Pearlfortune pool support; compressed-proof connection (lower bandwidth)
• v1.1.9 — fixed share rejects on HeroMiners; HiveOS now passes all settings through; official Docker image
• v1.1.8 — lower dev fee (Pearl 2% / qhash 1%), SSL/TLS, pool failover, ready-made configs
• v1.1.7 — qhash reliability + HiveOS dashboard fixes
• v1.1.5 / v1.1.6 — stability on mixed-GPU rigs; cleaner pool stats
• v1.1.4 — full hashrate on AlphaPool (Pearl)
• v1.1.3 — fewer stale shares on new blocks (Pearl)
• v1.1.2 — faster QubitCoin (qhash)
• v1.1.1 — RTX 40-series speedup
• v1.1.0 — QubitCoin (QTC) support
• v1.0.12 — RTX 30-series speedup
• v1.0.11 — driver-compatibility fix
• v1.0.10 — cleaner dashboard for partial rigs
• v1.0.9 — per-GPU selection on HiveOS
• v1.0.8 — big gains on host-starved rigs
• v1.0.7 — RTX 50-series speedup
• v1.0.6 — 8 GB cards on Windows; cleaner stats
• v1.0.5 — reliable startup on big rigs / older drivers
• v1.0.4 — per-GPU selection and overclock
• v1.0.3 — RTX 20-series on stratum + speedup
• v1.0.2 — HiveOS / Linux startup fix
• v1.0.1 — new pool; per-GPU memory temps
• v1.0.0 — first release

[0xHashRaptor]

ForgeMiner v1.1.8 is out.

• Dev fee lowered — Pearl 2%, qhash 1%
• SSL/TLS connections — ssl:// endpoints, non-blocking
• Pool failover — list multiple pools, auto-switch on disconnect
• stratum+tcp:// / stratum+ssl:// prefixes, plus --help / --version
• 23 ready-to-run per-region config files (.bat) with READMEs

Download: https://github.com/0xHashRaptor/ForgeMiner/releases

[0xHashRaptor]

ForgeMiner v1.1.9 is out.

• Fixed share rejects on HeroMiners (unique submit IDs)
• HiveOS — all FORGE_* settings now pass through correctly (fixes algo/OC selection)
• Official Docker image: hashraptor/forge:1.1.9 and :latest

Download: https://github.com/0xHashRaptor/ForgeMiner/releases
Docker: docker pull hashraptor/forge

[0xHashRaptor]

ForgeMiner v1.1.10 is out.

• Pearlfortune pool support — ready-made SSL config (ssl://global.pearlfortune.org:8888)
• Compressed-proof connection — lower bandwidth / less network traffic

Download: https://github.com/0xHashRaptor/ForgeMiner/releases
Docker: docker pull hashraptor/forge

[0xHashRaptor]

ForgeMiner v1.1.11 is out.

• Dedicated AlphaPool path — share crediting confirmed on the pool dashboard

Download: https://github.com/0xHashRaptor/ForgeMiner/releases

[xandry]

Feel free to scan it on VirusTotal and post the link — we encourage it.

Well, if you don't mind 

https://www.virustotal.com/gui/file/6a649529fb64509c7377173224c7543480dbd306913068248e3de6d95cb9a3cf

It is recognized as a "Popular threat label hacktool.
And the alarm is raised, for example:
Bkav Pro - W32.Malware.F13484B9
CrowdStrike Falcon - Win/malicious_confidence_70% (D)
Huorong - HackTool/CoinMiner.p
SecureAge - Malicious
SentinelOne (Static ML) - Static AI - Suspicious PE"

Special attention should be paid to github, since there is no open source code there, anyone who opens github can check it: https://github.com/0xHashRaptor/ForgeMiner

Moreover, with the help of github tools, we can check what you are constantly updating there. And this is... just the version number:
https://github.com/0xHashRaptor/ForgeMiner/compare/v1.1.11...v1.1.12
Probably in order to simply raise this topic on the forums.

Let's face it: you use github simply as a place to store your files, which gives them a certain kind of legitimacy, but the source code has never been there.

And finally... find ten differences with [ANN] Mining Control Free PORTABLE Panel Auto-Switch ZANO BEAM EPIC NEOX NEXA
Even the structure and files are almost the same in the archives.

[0xHashRaptor]

Feel free to scan it on VirusTotal and post the link — we encourage it.

Well, if you don't mind  

https://www.virustotal.com/gui/file/6a649529fb64509c7377173224c7543480dbd306913068248e3de6d95cb9a3cf

It is recognized as a "Popular threat label hacktool.
And the alarm is raised, for example:
Bkav Pro - W32.Malware.F13484B9
CrowdStrike Falcon - Win/malicious_confidence_70% (D)
Huorong - HackTool/CoinMiner.p
SecureAge - Malicious
SentinelOne (Static ML) - Static AI - Suspicious PE"

Special attention should be paid to github, since there is no open source code there, anyone who opens github can check it: https://github.com/0xHashRaptor/ForgeMiner

Moreover, with the help of github tools, we can check what you are constantly updating there. And this is... just the version number:
https://github.com/0xHashRaptor/ForgeMiner/compare/v1.1.11...v1.1.12
Probably in order to simply raise this topic on the forums.

Let's face it: you use github simply as a place to store your files, which gives them a certain kind of legitimacy, but the source code has never been there.

And finally... find ten differences with [ANN] Mining Control Free PORTABLE Panel Auto-Switch ZANO BEAM EPIC NEOX NEXA
Even the structure and files are almost the same in the archives.

Fair questions — let me answer each directly, no hand-waving.

VirusTotal. Those are exactly the detections every closed-source GPU miner shows, for the same reason. Scan T-Rex, SRBMiner, GMiner, lolMiner or NBMiner on VirusTotal right now and you'll get the same picture. Two things matter: (1) "CoinMiner / HackTool" is a CATEGORY label meaning "this binary is a cryptocurrency miner" — which ForgeMiner openly is — not a finding of malicious code. (2) Look at which engines flagged it: Bkav, CrowdStrike (confidence 70%), SentinelOne (Static AI / Suspicious PE), SecureAge, Huorong. Five engines out of ~70, and every one of them is a heuristic / machine-learning / PE-reputation engine that fires on any packed, unsigned, resource-heavy binary. There is no signature match to a known threat in that list, and the ~65 signature-based engines pass it. This is the well-documented miner false-positive problem, not something specific to us. (And yes — I'm the one who said "feel free to scan it," so I'm not going to complain that someone did.)

Closed source. ForgeMiner is closed-source and we say so on the first line of the README. So is T-Rex. So is SRBMiner, GMiner, lolMiner, NBMiner. For a competitive GPU miner the per-architecture kernels ARE the product; none of the top miners ship them open. GitHub is where we publish releases, release notes, pool presets and the HiveOS integration — the same way T-Rex and lolMiner use their repos. We have never claimed the source is there, so "the source has never been there" isn't a gotcha — it's by design, and stated.

The v1.1.11 to v1.1.12 diff being "just a version number." Of course the public git tree only shows a README change — the source is closed, so what's tracked in git is the README, the batch presets and the release pointers. The actual work in 1.1.12 (first-class Pascal P104 Pearl support, fan control, Windows VRAM-temperature monitoring) ships in the release binaries and is listed in the release notes. That's exactly how a closed project on GitHub looks.

The "ten differences" comparison. That link is a mining CONTROL PANEL / auto-switcher for ZANO/BEAM/EPIC/etc. ForgeMiner is a native CUDA kernel miner for Pearl, QubitCoin and (soon) KawPow — a different category of software. The only thing two miner archives share is the layout every miner uses: an executable, a few .bat presets, a README and HiveOS h-* scripts. That's packaging convention, not shared code.

How to actually verify us instead of guessing: run it on any of the listed pools and watch it submit accepted shares live; the dev fee is stated openly and is checkable on-pool; and compare our VT result side-by-side with T-Rex/SRBMiner. The miner is real and it works — closed, like its competitors, and honest about being so.


ForgeMiner v1.1.12 is out.

• Pascal P104-100 — Pearl support (up to ~7 TH/s per card)
• Fan control — fixed speed (--fan N) or temperature curve (--fan-curve)
• Windows VRAM temperature monitoring

Download: https://github.com/0xHashRaptor/ForgeMiner/releases
Docker: docker pull hashraptor/forge

[JeromeTash]

Out of curiosity, I did a static analysis of the files in the zipped folder using Claude AI, and I am going to share its response. I know static analysis could miss a thing or two, but I think this is a good start.

When I look at the flags raised by the few antiviruses, I would say it's because they detected the "crypto miner" component

This is the response I got

Here's what I found after extracting and analyzing the package:

Package Contents

The ZIP contains forge.exe (16.6 MB), along with 23 .bat launcher scripts and a README (English/Russian).

This is ForgeMiner, an NVIDIA GPU miner for two coins — Pearl (pearlhash) and QubitCoin (qhash). This is corroborated by Kryptex's own pool documentation, which lists:

Code:

forge.exe --algorithm pearlhash --pool ...

as one of their officially supported third-party miners alongside SRBMiner, ARC-miner, and lpminer.

This is strong evidence that ForgeMiner is a recognized mining application within the mining ecosystem rather than a one-off or unknown executable.

Executable Analysis (forge.exe)

• Type: PE32+ x86-64 console application compiled with Rust.
  Visible crate paths include:
  

Code:

rayon
blake3
rustls
ring
chrono

This is consistent with a legitimate modern mining application rather than a typical malware toolkit.

• SHA-256:
  
  Code:

  6a649529fb64509c7377173224c7543480dbd306913068248e3de6d95cb9a3cf
  

  
  
• Digital Signature:
  Not signed. While unsigned binaries deserve additional scrutiny, this is fairly common among smaller independent mining software.
  
  
• Imports:
  Only standard Windows, CUDA, and NVIDIA Management Library components were observed, including:
  
  Code:

  KERNEL32
  WS2_32
  bcrypt
  nvcuda.dll
  nvml.dll
  

  
  There are no imports associated with process injection, credential theft, or other suspicious Windows APIs.
  
  
• Sections:
  The .rdata section is unusually large (approximately 14.3 MB) and has near-maximum entropy (7.998/8).
  
  Further inspection shows this is fully explained by embedded CUDA .cubin kernels supporting multiple NVIDIA GPU architectures ranging from:
  
  
  Code:

  sm_61 (Pascal)
  ...
  sm_120a (Blackwell)
  

  
  This is exactly what would be expected from a genuine multi-generation GPU miner and does not resemble a packed or encrypted malware payload.
  

Malware Indicators

I found no evidence of the behaviors typically associated with malicious cryptocurrency miners, including:

• No process injection APIs (
  Code:

  CreateRemoteThread

  ,
  Code:

  WriteProcessMemory

  , etc.)
  
  • No registry-based persistence
  • No scheduled-task persistence
  • No keylogging functionality
  • No anti-debugging techniques
  • No hidden command-and-control (C2) infrastructure
  
  All network endpoints extracted from the executable match the mining pools referenced in the README and launcher scripts, including:
  
  
  • AlphaPool
  • Kryptex
  • HeroMiners
  • Baikal
  • LuckyPool
  • k1pool
  
  

[0xHashRaptor]

Thanks for taking the time to analyze it independently, JeromeTash — much appreciated. Your read is spot on: the AV flags are just the generic "crypto-miner" heuristic that hits every closed-source miner, nothing more.