The following git tags are the current recommended versions for running the stack. Components in the same row of the same repository should be built from the same tag.

Server-side components are listed for completeness; for full deployment guidance, see the Admin Guide.

The thin client libraries do not, by themselves, speak to the mix network. They communicate over a local socket with the kpclientd daemon, which performs all cryptographic and network operations.

git clone https://github.com/katzenpost/katzenpost
cd katzenpost
git checkout v0.0.75
cd cmd/kpclientd
go build

The resulting kpclientd binary is run with a TOML configuration file:

./kpclientd -c /path/to/client.toml

A configuration file is required. For testing, the Docker test mixnet generates one automatically; for joining a public network, you would obtain the configuration from that network’s operators.

The Go thin client is a library, imported as a Go module:

import "github.com/katzenpost/katzenpost/client/thin"

Pin to v0.0.75 in your application’s go.mod. There is no separate build step; the library is compiled with your application.

git clone https://github.com/katzenpost/thin_client
cd thin_client
git checkout 0.0.14
cargo build --release

Or, in another Rust project’s Cargo.toml:

[dependencies]
katzenpost_thin_client = "0.0.14"

The Python thin client is best installed into a virtualenv, both to isolate its dependencies and to avoid any disturbance of the system Python.

git clone https://github.com/katzenpost/thin_client
cd thin_client
git checkout 0.0.14
python3 -m venv .venv
source .venv/bin/activate
pip install --upgrade pip
pip install .

A decentralised group chat client built atop Qt. It depends solely on the Katzenpost mix network and the Pigeonhole storage services. No central server is involved. The underlying design is set out in the Echomix paper.

sudo apt install libxcb-cursor0 libegl1
git clone https://github.com/katzenpost/katzenqt
cd katzenqt
git checkout 0.0.2-rc6
make deps
make run

If make deps run does not produce a running interface, the component-by-component sequence in katzenqt’s README.md is the recommended fallback.

Once kpclientd is running with a valid configuration, a single test from the Python integration suite is sufficient to exercise the full Pigeonhole round trip: Alice writes a message to the storage replicas via the courier, and Bob reads it back.

source thin_client/.venv/bin/activate
cd thin_client
pytest tests/test_new_pigeonhole_api.py::test_alice_sends_bob_complete_workflow

A successful run indicates that kpclientd is connected, the PKI document has been retrieved, the network is producing consensus, and the courier and replicas are reachable. The remainder of the suite (pytest with no arguments) covers tombstones, copy commands, and the various error paths.