A volunteer GPU worker for decrypt. Run it on a machine with an NVIDIA GPU and it quietly does distributed compute jobs in the background: it asks the coordinator for a chunk of work, runs it on your GPU, sends the result back, and repeats — forever, until you stop it. Run and forget.
- A CUDA-capable NVIDIA GPU.
- An up-to-date NVIDIA driver. That's all — no CUDA toolkit, no extra runtime, nothing else to install.
- Linux or Windows (64-bit).
Download the latest archive from the Releases page and unpack it:
- Linux:
decryptd-linux-x86_64.tar.gz→tar -xzf decryptd-linux-x86_64.tar.gz - Windows:
decryptd-windows-x86_64.zip→ extract it (right-click → Extract All)
Each archive contains a single decryptd executable.
Just run it — no configuration needed:
./decryptd # Linux
decryptd.exe # WindowsIt loops forever: claiming work, running it on the GPU, submitting results. When
there's no work available it waits a minute and checks again. Stop it any time
with Ctrl-C.
To keep it going after you log out:
# Linux — quick and dirty
nohup ./decryptd >decryptd.log 2>&1 &For an always-on contributor, run it under a service manager (systemd on Linux, a scheduled task / service on Windows) so it restarts on boot.
You normally don't need any of these.
| Option | Default | What it does |
|---|---|---|
--once |
off | Do a single chunk of work, then exit (handy for testing). |
--idle-secs <N> |
60 |
How long to wait before re-checking when there's no work. |
--jobs <N> |
1 |
How many chunks to run on the GPU at once. |
--workdir <DIR> |
decryptd-data |
Where to keep the download cache and scratch files. |
Downloading the next chunk and uploading finished results always happen in the
background while the GPU works, so the card stays busy. --jobs only raises how
many run on the GPU simultaneously — most setups are fine with the default.
Run decryptd --help for the full list.
You need a Rust toolchain and a CUDA toolkit (only to link against the driver library at build time — the binary still just needs the driver to run):
cargo build --releaseThe binary lands in target/release/decryptd (.exe on Windows).
Proprietary. See Cargo.toml.