← All insights
RELEASEZcash Forum · gustavovalverde

Zinder: an indexer built on its own protocol

Zinder, a Zcash indexer that offers a lightwalletd-compatible runtime while letting ingest, wallet and explorer components be deployed separately, has been released.

Zinder is a Zcash indexer with its own query protocol that provides a lightwalletd-compatible runtime as a module and lets the ingest, wallet and explorer components be deployed separately. The author explains that they built it because existing indexers got in the way of getting a Zcash product working end to end. The problem was that existing indexers imitate lightwalletd or are shaped around a specific wallet SDK, so the consumer-side protocol becomes the internal architecture.

The design centers on its own gRPC contract, WalletQuery, the zinder-query runtime that serves it, and the Rust SDK zinder-client on top. It offers typed errors with stable reason codes, explicit capability discovery and resumable chain events, and reads are pinned to a single ChainEpoch so results from different tips are never mixed in one response. lightwalletd compatibility is handled by a separate runtime, zinder-compat-lightwalletd, and CI compares its responses against the reference implementation, Go lightwalletd.

The components separate who writes. Only zinder-ingest writes canonical chain state, only zinder-projector writes wallet projection state, and the serving runtime never writes to storage. The optional explorer layer includes a CipherScan-compatible REST adapter. Each store has exactly one primary writer, and read processes open a RocksDB secondary separately, so heavy reads cannot block writes. The currently supported topology is the single-host rocksdb-single-host.

Zinder reads data from Zebra over JSON-RPC and, where possible, the indexer gRPC stream, and has verified Ironwood (NU6.3) decoding and regtest and lightwalletd compatibility against Zebra 6.2.2. On testnet, Zallet connected to the same deployment through native WalletQuery and ZODL through the compatible endpoint, and restore, sync, send and mempool behavior were checked. The native Zallet backend is in progress as PR zcash/zallet#701, and bugs found during real wallet integration were merged into librustzcash and incrementalmerkletree.

On the operations side, it provides environment-variable configuration, health, readiness and metrics endpoints, a RocksDB memory cap, amd64 and arm64 container images, SLSA provenance attestations and an SBOM. It aims for a PostgreSQL topology to go beyond the single-host limit, but there is no deployable backend yet. The author is seeking feedback from wallet teams, operators and explorer developers, and warns that it is at the alpha stage and needs caution for production use. The Zcash Foundation currently sponsors its development.

This summary is based on the original; check the original for exact details.