1. Request your personal fishnet key: https://lichess.org/get-fishnet

2. Install and run the fishnet client.

   Download standalone binary

   Select the binary for your platform from the latest release and run it.

   # After download:
   chmod +x fishnet-x86_64-unknown-linux-gnu
   ./fishnet-x86_64-unknown-linux-gnu --auto-update

   Other useful commands:

   ./fishnet-x86_64-unknown-linux-gnu configure              # Rerun config dialog
   ./fishnet-x86_64-unknown-linux-gnu systemd --auto-update  # Print a .service file
   ./fishnet-x86_64-unknown-linux-gnu --help                 # List commands and options

   From source

   Assuming you have a recent Rust toolchain installed:

   git clone --recursive https://github.com/niklasf/fishnet.git
   cd fishnet
   cargo run --release --

   Docker

   docker run -it -e KEY=abcdef niklasf/fishnet:2

3. Pick an update strategy.

   Automatic updates

   Run with --auto-update as recommended above (will currently still require manual restarts on Windows due to #151).

   Subscribe to release announcements

   With a GitHub account, you can watch this repository (can be set to only release announcements). See the top right corner on this page.

Watch @arex explain fishnet.

fishnet uses Stockfish 12 (hence the name) and a fork of Stockfish with multi-variant support.

Precompiled builds for various CPU models come bundled with fishnet. To get another architecture included, all we need is a reproducible build process (so everyone can verify that the compiled binary matches the source).

• Needs an operating system from around 2016 or later
• Will max out the configured number of CPU cores
• Uses about 64 MiB RAM per CPU core
• A small amount of disk space
• Low-bandwidth network communication with Lichess servers (only outgoing HTTP requests, so probably no firewall configuration required)

Almost all processors will be able to meet the requirement of ~2 meganodes in 6 seconds. Clients on the faster end will automatically be assigned analysis jobs that have humans waiting for the result (the user queue, as opposed to the system queue for slower clients).

Feel free to turn your client on and off at any time. By default, the client will try to finish any batches it has already started. On immediate shutdown, the client tries to inform Lichess that batches should be reassigned. If even that fails, Lichess will reassign the batches after a timeout.

No, Stockfish is a classical alpha-beta engine. The neural network evaluation of Stockfish NNUE works efficiently on CPUs.

To the best of our knowledge. However you implicitly trust the authors and the GitHub infrastructure when running with --auto-update.

You can mitigate this by running fishnet as an unprivileged user.

Stockfish builds are reproducible, so you can verify that the distributed binaries match the source.

cargo-crev is used to review the trustworthiness of dependencies.

No, sorry, not publically. It would incentivize gaming the metrics.

There is currently no ready-made solution, but an API for monitoring the job queue status is provided.

See protocol.md for details. Also supports SSLKEYLOGFILE for inspection at runtime.

fishnet is licensed under the GPLv3+. See LICENSE.txt for the full license text.