snider 69376b886f feat: Rebrand xmrig to miner and vendor XMRig ecosystem

Complete rebranding of all components:
- Core miner: xmrig -> miner (binary, version.h, CMakeLists.txt)
- Proxy: xmrig-proxy -> miner-proxy
- CUDA plugin: xmrig-cuda -> miner-cuda
- Heatmap: xmrig-nonces-heatmap -> miner-nonces-heatmap
- Go CLI wrapper: miner-cli -> miner-ctrl

Vendored XMRig ecosystem into miner/ directory:
- miner/core - XMRig CPU/GPU miner
- miner/proxy - Stratum proxy
- miner/cuda - NVIDIA CUDA plugin
- miner/heatmap - Nonce visualization tool
- miner/config - Configuration UI
- miner/deps - Pre-built dependencies

Updated dev fee to use project wallet with opt-out (kMinimumDonateLevel=0)
Updated branding to Lethean (domain, copyright, version 0.1.0)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2025-12-30 19:43:02 +00:00

834 B

Raw Blame History

Maximum CPU usage

Please read this document carefully, max-threads-hint (was known as max-cpu-usage) option is most confusing option in the miner with many myth and legends. This option is just hint for automatic configuration and can't precise define CPU usage.

Option definition

Config file:

{
    ...
    "cpu": {
        "max-threads-hint": 100,
        ...
    },
    ...
}

Command line

--cpu-max-threads-hint 100

Known issues and usage

This option has no effect if miner already generated CPU configuration, to prevent config generation use "autosave":false,.
Only threads count can be changed, for 1 core CPU this option has no effect, for 2 core CPU only 2 values possible 50% and 100%, for 4 cores: 25%, 50%, 75%, 100%. etc.
You CPU may limited by other factors, eg cache.

834 B Raw Blame History