Proof of Work · MLRTHash v1
Mining Malairte
Malairte uses a double-SHA3-256 (Keccak) proof-of-work designed with quantum resistance in mind. Everything is in-house: one installer, zero third-party mining software, CPU and NVIDIA GPU support side by side.
In-House Stack
No external miners. No custom configs. No pools.
The node binary malairted mines directly. CPU threads and the CUDA GPU worker run inside the same process — pointed at the same chain, sharing a single reward address. You don't install XMRig, BzMiner, or anything else: the installer drops everything you need and you're hashing within seconds.
Your Options
CPU vs GPU Mining
CPU Mining
DefaultEvery installation starts with CPU mining enabled. One thread per logical core by default. Works on any 64-bit Windows, Linux, or macOS machine with no extra drivers.
- + Zero setup — included with the node
- + Runs anywhere: Windows, Linux, macOS, ARM
- + No GPU driver or toolkit needed
- ~ Lower absolute hashrate than a modern GPU
GPU Mining (NVIDIA)
OptionalA dedicated CUDA worker runs alongside CPU threads, dispatching millions of nonces per kernel launch. Every GPU hit is re-verified on the CPU before submission, so a faulty kernel can never produce an invalid block.
- + Orders of magnitude higher hashrate
- + Self-contained — CUDA runtime bundled
- + Runs concurrently with CPU threads
- ~ NVIDIA only; requires current driver
Requirements
Hardware Requirements
- Any 64-bit CPU (2016+)
- 2 GB free RAM
- 5 GB free disk
- Any broadband connection
- Outbound TCP 9333 open
- 8+ core CPU (Ryzen 7 / Core i7)
- 16 GB RAM
- 50 GB SSD
- NVIDIA GPU (optional) — RTX 30xx+
- Current NVIDIA driver
- Compute capability 7.5+ (RTX 20xx or later, Turing+)
- NVIDIA driver 525+ (or 570+ for Blackwell/RTX 50xx)
- 1 GB+ VRAM (kernel is lightweight)
- Windows 10/11 x64 or Linux x86_64
- macOS: CPU only (Apple dropped CUDA)
CUDA Toolkit not required on end-user machines — the runtime is statically linked into the node binary.
Setup Guide
Getting Started
Generate a miner key
Visit explorer.malairtebitcoin.com/onboarding and generate a 64-character hex private key. This key both receives your mining rewards and identifies your wallet — keep a backup somewhere safe.
Run the installer
Download the platform installer from the Downloads page. Windows users get a signed GUI (malairt-installer.exe); Linux and macOS users get a shell script. Paste your key, tick Use GPU for mining if you have a supported NVIDIA card, and click Install.
The installer auto-configures
Binaries are placed under %LOCALAPPDATA%\Malairte on Windows or /usr/local/bin on Linux/macOS. A Windows service (NSSM) or systemd / launchd unit is registered so the node starts on boot. If a GPU was detected, mlrt_gpu.dll is deployed alongside the node.
Check your balance
Open explorer.malairtebitcoin.com and search your miner address. Every block your node mines credits 50 MLRT to that address, with 6 confirmations recommended before treating rewards as settled.
Deep Dive
How GPU Mining Works
When --gpu is enabled, malairted spawns an extra goroutine that drives a CUDA kernel. Each kernel launch tries 16 million nonces in a single batch — on an RTX 5090 that completes in ~30 ms, giving roughly 500 MH/s of double-SHA3-256 hashrate.
The kernel implements Keccak-f[1600] permutation directly on the GPU (no library dependency), specialized for 96-byte and 32-byte inputs. When any thread finds a hash that satisfies the difficulty target, an atomic exchange claims the first winner and the nonce is returned to the host.
Every GPU hit is re-verified on the CPU before the block is broadcast — if the kernel ever produces a bad hash, the block is rejected locally with a [miner/gpu] BUG log line and the GPU worker shuts down safely. You can't mint an invalid block with a buggy kernel.
CPU threads continue mining in parallel with GPU worker. They search different extraNonce ranges so the two paths never collide. If the GPU fails to initialize (no driver, unsupported card), the node logs a warning and keeps mining on CPU — the --gpu flag never hurts you.
Quantum Resistance
Why double-SHA3-256?
SHA-3 (Keccak) was selected by NIST in 2012 as a sponge-construction alternative to SHA-2. Unlike SHA-256, Keccak resists length-extension attacks and — unlike hash functions based on discrete-log or factoring assumptions — has no known quantum speedup beyond the generic Grover bound of √N. For a 256-bit preimage, that means quantum attacks still face 2128 operations.
Applying SHA-3-256 twice adds a second irreversibility layer and protects against theoretical weaknesses in the single-pass construction. The full quantum-security argument lives on our Quantum Security page.
Companion App
Malairte Wallet for Mobile
View your balance, send and receive MLRT, and watch live network activity from your phone. Built with .NET MAUI, signed with the Malairte project keys, fully self-custodial — your private key never leaves the device.
Google Play and App Store listings are in store review — links will appear here once approved.
Ready?
Start mining in minutes
Grab the installer, paste your miner key, tick the GPU box if you've got one — the node takes care of the rest.
Download the node