# tachyon-payments > Private-retrieval (PIR) services for the Tachyon payment protocol on Zcash, built by Zcash Labs. ## Docs - [Architecture](/architecture): `tachyon-payments` implements the server-side Private Information Retrieval (PIR) layer of the Tachyon payment protocol on Zcash, as outlined in the Tachyon Book's *Payment Protocol* design. - [Local Regtest Quickstart](/quickstart): This guide runs the full PIR stack — a local `NuTachyon` Zakura node, `tachyon-pir-publisher`, an HTTPS edge, `tachyon-pir-query-server`, and `tachyon-pir-cli` — on your machine. - [Shared Table & Wire Protocol](/reference/shared): All four PIR products share one bucket-row table format, one PIR cryptographic profile, and one HTTP serving protocol. The normative contract is [`spec-tachyon-payment-pir.md`](https://github.com/zcashlabs/tachyon-payments/blob/master/docs/spec/spec-tachyon-payment-pir.md). - [Tachygram](/products/tachygram): The **tachygram** database lets a wallet privately verify two things per epoch: **inclusion** of a note commitment (returning the block height and stamp ordinal needed to fetch its creation stamp) and **exclusion** of a nullifier (proving a note remains unspent over the covered heights). - [Registry](/products/registry): The **registry** is an off-chain address directory (`H(addr) => pk || ek`) that lets a sender expand a recipient's short address `(chunk_id, digest)` into a full Tachyon payment address privately over PIR. - [Memo](/products/memo): The **memo** database lets a wallet privately fetch follow-up payment memos (`tag => ciphertext`) for an established sender–recipient pair, scoped per Tachyon epoch. - [First-contact](/products/first-contact): The **first-contact** database lets a wallet privately discover initial payments from new senders (`tag => KEM.c || ciphertext`), carrying the ML-KEM-768 encapsulation ciphertext alongside the encrypted note opening. - [Building & Testing](/operator/building): **Rust**: toolchain pinned in `rust-toolchain.toml` (`1.97.1`, with `rustfmt` and `clippy`) - [Probe Client (CLI)](/operator/cli): `tachyon-pir-cli` is a diagnostic probe client for inspecting maps and executing real encrypted PIR lookups against a query host. It prints one JSON document to stdout and exits `0` on success or `1` on error (also formatted as JSON). - [Observability & Alerts](/operator/observability): Both hosts expose operational endpoints on their loopback `management_listen` addresses and never log or label metrics with client-supplied bytes. - [Publisher Configuration](/operator/publisher): `tachyon-pir-publisher` is a single process that follows one Zakura node, builds deterministic PIR tables for every enabled product, and serves content-addressed publications on per-product private listeners. - [Query Server Configuration](/operator/query-server): `tachyon-pir-query-server` pulls published PIR tables from the publisher over HTTPS, verifies digests and scope bindings, holds resident tables in memory, and answers encrypted wallet queries on a single `public_listen` address. - [TLS Edge & Routing](/operator/tls-edge): Both `tachyon-pir-publisher` and `tachyon-pir-query-server` bind plaintext HTTP on loopback or private interfaces and expect a TLS-terminating reverse proxy (Caddy, Nginx, Envoy, or a cloud load balancer) in front of them.