🐓 Mouillay GPU Miner — 1.0.2

A standalone NVIDIA GPU miner for PEARL on Windows, Linux and Docker. Automatic GPU detection selects the SM86 or SM89 kernel. PEARL + NOCK merge mining is available on compatible pools. 🚀

📦 Downloads — 1.0.2

Platform	Download	Start mining
🪟 Windows x64	EXE + BAT ZIP	Edit START_MINER.bat with your pool and wallet.worker
🐧 Linux x86_64	Standalone binary + launcher	Ubuntu 24.04+; edit START_MINER.sh
🐳 Docker linux/amd64	Binary-only image archive · Instructions	Docker + NVIDIA Container Toolkit

🚀 Tested performance

GPU	Hashrate	Efficiency
RTX 3070	94 TH/s	2.33 W/TH
RTX 4060 Mobile	65.5 TH/s	1.52 W/TH
RTX 4060 Ti	92.5 TH/s	1.72 W/TH

Feel free to share your stats on discord

📦 Get started

1. Download MouillayMiner.exe and START_MINER.bat into the same folder, or download the ZIP from Release 1.0.2.
2. Right-click START_MINER.bat and choose Edit.
3. Set your pool and your own wallet.worker. Choose a mode:

💎 PEARL only

set "POOL=poolmouillay.com:3360"
set "WALLET_WORKER=YOUR_PEARL_ADDRESS.rig1"

🐓➕🟡 PEARL + NOCK merge mining

Use a compatible pool such as poolmouillay.com:3360, and provide both payout addresses:

set "POOL=poolmouillay.com:3360"
set "WALLET_WORKER=YOUR_PEARL_ADDRESS+YOUR_NOCK_ADDRESS.rig1"

Keep the plus between the addresses and the dot before the worker. Both addresses must belong to you. To return to PEARL-only mode, remove +YOUR_NOCK_ADDRESS.

The miner supplies the PEARL proof to the pool with your two payout identities. The compatible pool performs NOCK verification, accounting and any eligible block submission. A successful PEARL share does not guarantee a NOCK block or an immediate NOCK reward; each chain has its own validation and target. The terminal labels the combined mode as requested because an accepted login alone cannot certify the pool's NOCK backend.

4. Save the file and double-click START_MINER.bat. Happy hashing! 🐣

The supplied Windows launcher is prefilled with the maintainer's public wallet. Replace it with your wallet before mining. Each GPU gets a -gpuN worker suffix automatically.

No Python or CUDA Toolkit installation is needed. You still need a compatible NVIDIA driver. On Windows, only the EXE and BAT are needed to start; runtime resources are extracted temporarily and normal shutdown removes them. The executable creates a logs folder beside itself, containing the shared miner-session.jsonl. Keep the miner in a folder where you have write permission.

🐧 Linux

Extract the Linux archive, make MouillayMiner and START_MINER.sh executable, edit the launcher with your pool and wallet.worker, then run ./START_MINER.sh. The archive contains a native standalone executable.

🐳 Docker

docker load -i Mouillay-GPU-Miner-1.0.2-docker-linux-amd64.tar.gz
docker run --rm --gpus all -v mouillay-logs:/opt/mouillay/logs mouillay-gpu-miner:1.0.2 --pool poolmouillay.com:3360 --user YOUR_PEARL_ADDRESS.rig1

For merge mining, use YOUR_PEARL_ADDRESS+YOUR_NOCK_ADDRESS.rig1. The image contains the compiled miner and its runtime dependencies. Logs remain in the mouillay-logs volume. Use docker stop or Ctrl+C to stop mining.

🍰 Developer fee: a small slice for development

Your mining pool	Miner developer fee
🏡 poolmouillay.com	0.5%
🌍 Any other pool	1.0%

🐓 Home-pool perk: the exact hostname poolmouillay.com receives the lower rate. Other domains, including lookalike names, use 1.0%. Port numbers do not change the rate.

⏱️ Active work counts: the fee is measured against completed active scan time. About 5 seconds per 1,000 active seconds are allocated to development at 0.5%, or 10 seconds at 1.0%. Pool operator fees may apply separately.

⏸️ Take a break: pauses, connection waits and new-job setup do not add developer-fee debt.

🔄 Small mining rounds: developer time is collected in roughly 3-second bursts. The first burst starts after about 600 active seconds on PoolMouillay, or 300 seconds elsewhere. The miner then returns to your worker. Whole-scan rounding means a short session may show a slightly different realized percentage. Counters reset when the miner restarts.

🔎 Accounting: the terminal displays your share counters. Developer share counters remain in diagnostic logs and are hidden from the terminal. The fee rate stays visible. Developer rounds replace both the payout identity and worker: the worker is always devfee, without your original worker name. Delayed proofs stay attached to their original wallet, connection and job.

Developer payout address:

prl1pt8t3tffncrwlfgp28mfh2kljgk29g480e8fzw49k0q7rc9lwc06s79c60j

In merge mode, developer rounds use the developer's own NOCK payout identity as well:

7VH3xXvaFLecVZZaK5kga7hx2LeMRDx6sNckpf5fnAHb5kSQYPJRjKR

Your NOCK address is never substituted into the developer login. PEARL-only sessions keep PEARL-only developer rounds. The time-based developer fee rate above is unchanged; pool fees on either chain are separate.

🎯 Custom share difficulty

Edit the launcher to request a difficulty from a compatible pool:

set "DIFFICULTY=8388608"

Use 0 for the pool default, or pass --difficulty 8388608 on the command line. A positive value is sent as password: "d=8388608" in mining.authorize; 0 sends an empty password.

The setting applies to each GPU worker and its developer rounds. It is a request: the pool may ignore or clamp it, and the miner always uses the actual target provided by the pool. Higher difficulty generally means fewer, harder shares; it does not increase GPU hashrate or change the developer fee.

📡 Automatic proof compression

The miner requests Pearl gzip v2 when connecting. If the pool explicitly confirms v2, proofs are sent as gzip-compressed binary data encoded in base64. Otherwise, the original uncompressed proof format is preserved automatically. User and developer connections negotiate independently.

Compression reduces proof upload size; it does not change GPU hashing, proof validation, or the developer fee. Diagnostic logs record the selected transport, payload sizes, and compression time.

⚡ Power efficiency

The dashboard shows GPU power and efficiency per GPU and in total:

Power      : 180.00 W (GPU total)
Efficiency : 2.25 W/(TH/s) (lower is better)

This example is 180 W ÷ 80 TH/s = 2.25 W/(TH/s), equivalent to 2.25 J/TH. The denominator is the miner's effective 10-second hashrate, not a pool estimate. Total efficiency is total selected-GPU watts ÷ total effective hashrate.

Power comes from NVIDIA GPU telemetry; it excludes the CPU and the rest of the computer. Sensor readings and the hashrate window are sampled separately, so the ratio is an estimate. Missing or stale sensors, zero hashrate and paused cards show N/A instead of an invented value.

🖥️ GPU selection and controls

• Automatic per-GPU selection, including the SM86 RTX 3000 and SM89 RTX 4000 paths.
• RTX 4000 kernels are unchanged in this release.
• This Windows bundle was exercised on an RTX 3070; other GPUs still perform their startup self-test.
• P: pause/resume all GPUs.
• 0–9: pause/resume the corresponding GPU.
• Ctrl+C: stop the miner.

Useful commands:

MouillayMiner.exe --version
MouillayMiner.exe --list-devices
MouillayMiner.exe --mode validate
MouillayMiner.exe --mode benchmark
MouillayMiner.exe --notice
START_MINER.bat --devices 0

🔐 Distribution notice

Copyright © 2026 PoolMouillay. Interdit de décompiler / Decompilation prohibited for original proprietary components, subject to applicable law and the exceptions in NOTICE.txt. Third-party components retain their own licenses and rights.

The executable includes this notice in its Windows metadata and embedded notice file. Most application source resources are shipped as bytecode; some source resources remain necessary for runtime proof validation and CUDA compilation. This is modest packaging hardening, not a guarantee against reverse engineering or automated analysis.