0 % devfee, enforced in code
DEVFEE_PERCENT = 0 is a plain constant in the public core. No devfee window means no nonce reset, no duplicate shares, no hidden pool switch. Ever.
In development. No release yet: everything on this page describes the first public version, v0.1.Get notified →
Phase 0 · RandomX on CPU · GPU next
Nothing hidden.
Nothing to fear.
FearMiner is an open-core proof-of-work miner. 0 % devfee. One static binary. A terminal UI you will want to keep open. And a startup banner that shows exactly where your hashes go.
Apache-2.0 core · 0 % devfee · no telemetry · signed releases · never runs as root
$ fearminer 4A1bK…9fQz fearminer 0.1.0 linux-x86_64 static binary sha256 3e9c…b1d7 ✓ matches SHA256SUMS wallet 4A1bK…9fQz ✓ checksum ok never rewritten pool stratum+ssl://pool.example.org:443 TLS pinned · custody: pool · worker rig-01 devfee 0 % a constant in the source, not a promise network never contacts our servers · outbound: your pool privs user, not root · huge pages 100 % · MSR via helper cpu 16C/32T · rx/0 · 30 threads · 2 left to the OS ready job received · share accepted · ctrl-c exits 0
Illustrative output · every line above is a real field of the banner
00 · Before the first release
One email when v0.1 ships. Nothing else.
FearMiner is being built in the open, but the first binaries are not out yet. Leave an address and you will get exactly one message on release day, with the download links and the hashes.
- ✓ One email at launch. No newsletter, no updates, no partners.
- ✓ Never shared, never sold, deleted after the launch email.
- ✓ No account, no tracking, no third party involved. The form talks to this site only.
01 · Install
One binary. One command. Verify it first.
No installer, no runtime, no account. Download the archive for your platform, check the hash, run it with your wallet. That is the whole onboarding.
Available at the v0.1 release. Shown here so you know what to expect.
curl -LO https://github.com/fearminer/fearminer/releases/latest/download/fearminer-linux-x86_64.tar.gz curl -LO https://github.com/fearminer/fearminer/releases/latest/download/SHA256SUMS sha256sum -c SHA256SUMS --ignore-missing tar xzf fearminer-linux-x86_64.tar.gz ./fearminer YOUR_WALLET
Static musl binary, x86-64 and ARM64, no glibc requirement. Works on HiveOS images with old libraries.
Invoke-WebRequest https://github.com/fearminer/fearminer/releases/latest/download/fearminer-windows-x86_64.zip -OutFile fearminer.zip (Get-FileHash fearminer.zip -Algorithm SHA256).Hash # compare with SHA256SUMS Expand-Archive fearminer.zip -DestinationPath fearminer .\fearminer\fearminer.exe YOUR_WALLET
No UPX packing, readable version symbols, signed executable: built to keep Defender quiet, and documented if it is not.
curl -LO https://github.com/fearminer/fearminer/releases/latest/download/fearminer-macos-arm64.tar.gz curl -LO https://github.com/fearminer/fearminer/releases/latest/download/SHA256SUMS shasum -a 256 -c SHA256SUMS --ignore-missing tar xzf fearminer-macos-arm64.tar.gz ./fearminer YOUR_WALLET
Apple Silicon, CPU mining. A JIT that respects W^X, so no "allow" dialogs to click through.
cargo install fearminer fearminer YOUR_WALLET
Builds from the published source. Reproducible builds let you compare your binary's hash with ours.
SHA256SUMS signed with minisign · key
RWQ… printed in the README, in DNS and inside the binary
All releases →
02 · What the banner guarantees
Every promise is a line of code you can read.
Most miners ask you to trust a README. FearMiner puts the guarantees in the source, in the CI, and on your screen at every start.
Your wallet, checked before the first hash
The address is validated for its chain, checksum included, and shown in the banner. A typo stops the miner instead of paying a stranger for a week.
0 of 16 closed miners do this →Never phones home
No licence check, no telemetry, no update ping, no devfee pool. The only outbound socket is the pool or node you configured. A CI test runs the miner with every host blocked except the pool.
what we can never break →Never runs as root
Huge pages and MSR tweaks go through a tiny, audited helper. The privilege is taken, used, and dropped before the first network packet.
fearminer-helper →Honest hashrate
Local hashrate next to what the pool actually credits you for, with the gap explained: stale, rejected, or a card that computes garbage. The number that pays you is the one on screen.
see the TUI →Recovers, then tells you
A separate supervisor restarts a stuck device, distinguishes an overclock crash from a bug, and sends a Telegram or webhook alert with the reason. Not "GPU 3 hung" at 3 am, but what to do about it.
alerts without a mining OS →03 · The terminal UI
A dashboard that costs half a percent of one core.
Four colours that mean four things: ok, warning, error, info. Rendered by diff in its own thread, never on the mining path. Falls back to plain text when there is no terminal.
hashrate
14.1 kH/s
credited13.9 kH/s · −1.4 %
60 s / 15 m14.0 / 13.8
shares
accepted1 284
stale3
rejected0
latency41 ms
effort96 %
source
poolconnected
last job4 s ago
diff120 001
custodypool · payout ≥ 0.1
devfee0 %
energy
wall118 W
efficiency8.4 J/kH
temp78 °C
presetbalanced
solarsurplus 0 W · idle
Illustrative rendering of the v0.1 layout · h help · p pause · l logs · q quit
04 · We ran 16 closed miners in a sandbox
Then we built the opposite.
Isolated network, fake pool, wrong wallet on purpose, Ctrl-C, no terminal. The protocol and every capture are published. Here is what the market does today.
0/16
validate the wallet address before mining. All sixteen sent MAUVAISWALLET to the pool and started hashing.
1/16
exits cleanly with code 0 on Ctrl-C. Eleven die by signal; one ignores Ctrl-C while waiting for a pool.
12/14
spray colour codes into logs when there is no terminal. Only two switch to plain text on their own.
2/16
refuse to mine at all when their devfee pool is unreachable. Your rig stops because their server did.
- ✓ FearMiner refuses a malformed address, and shows the one it will pay to.
- ✓ Ctrl-C stops every thread, restores what it changed, and exits 0. Under a second.
- ✓ No terminal,
NO_COLOR,TERM=dumb: plain timestamped lines, or JSON. - ✓ There is no devfee pool to be unreachable. Structural immunity, tested in CI with the network cut.
Bench of 14 September 2026, sixteen binaries, bubblewrap sandbox, fake multi-dialect pool. Miners are not named here on purpose; the full per-miner reports are published with the protocol.
05 · Open core, without the fine print
What is open. What is not. Why.
Everything you run is Apache-2.0: the host, the network layer, the TUI, the API, the reference kernels, the devfee constant, the helper. It builds reproducibly, ships an SBOM, and is never packed. Read it, build it, compare hashes.
What is not open: a set of optimised GPU kernels for a few algorithms, the part that takes months of tuning per card generation. They ship as signed plugins you can load, verify and remove. The public reference kernel for every algorithm is always there and always works.
Nothing about your monitoring is ever gated: TUI, API, Prometheus, alerts, dashboards stay open for good. The value is in the maths, never in what you see of your own machine.
host, scheduler, nonce logicApache-2.0
stratum, node, P2PoolApache-2.0
TUI, web GUI, API, exportersApache-2.0
devfee constant (= 0)Apache-2.0
reference kernels, RandomX engineApache-2.0 · BSD-3
privileged helperApache-2.0
optimised GPU kernelssigned plugin
reproducible build · SBOM · minisignevery release
obfuscation in the public treeCI fails
06 · Chains
Today RandomX. Then the chains nobody optimises.
Phase 0 · CPU
rx/0 · rx/2 · variants
Monero, Zephyr, Salvium and every RandomX chain, pool, P2Pool or solo against your own node.
Phase 1 · GPU + solo
ProgPoW family
The 100 % GPU chains served only by closed miners today. One parametrised kernel opens a whole family.
Then
the 2026 wave
New algorithms enter through a public gate: an open reference implementation, a stable consensus, no ASIC. Announced in the news feed, never bolted on in 48 hours.
Performance claims come with a protocol: hardware, versions, duration, date. Until a number is measured, it is not on this page.
07 · Questions
Fair questions, plain answers.
Why 0 %? How is this paid for?
The public miner is a product in itself, and it earns nothing per hash. The company behind it runs mining infrastructure and sells optimised kernels and fleet tooling to those who want them. The public miner never becomes the place where that money is taken.
Why call it FearMiner?
Because the only one who should be afraid is the miner you use today. FearMiner shows everything: where your hashes go, what it touches on your machine, what it will never do. Fear is for the ones that hide.
What exactly is in the private kernels?
GPU compute code for a few algorithms, tuned per card generation. Nothing else: no networking, no configuration, no telemetry. They run inside the same contract as the public reference kernels, and the miner self-tests every kernel against a public oracle before the first share.
How do I verify the binary?
Every release ships SHA256SUMS, a minisign signature, a cosign attestation and an SBOM. The public key is in the README, in a DNS TXT record and compiled into the binary. fearminer verify checks a downloaded archive for you. Builds are reproducible: compile it yourself and compare.
My antivirus flags it.
Miners are flagged as a category, not because of what this one does. FearMiner is not packed, keeps its version symbols, signs its executables and lists every network destination. We publish the false-positive status per vendor and the reports we filed. Any miner that promises "no detection" is doing something you do not want.
Which pools? Solo? P2Pool?
Any Stratum pool. P2Pool with a single line. Solo mining directly against your node, with the block you found visible on screen. The custody model of your current source is printed in the banner.
Can it follow my solar surplus?
Yes. It exposes itself to Home Assistant as a device with a power target, reads a surplus or price signal over MQTT, and ramps the rig up and down with hysteresis and a battery floor. Efficiency is shown in joules per hash from the actual energy counter.
Does it run in Docker, on HiveOS, in a VM?
Everywhere it can be observed. It never refuses an environment. A HiveOS custom package and an official Docker image ship with each release; a Kubernetes manifest is in the box.
08 · Official channels
These are the only ones.
No admin will ever message you first. There is no airdrop, no presale, no token. If someone asks for money in our name, it is not us.