The highest tagged major version is v4.

replicate

command

v1.10.2 Latest Latest Go to latest Published: Jul 7, 2026 License: Apache-2.0 Imports: 19 Imported by: 0

Details

Valid go.mod file
Redistributable license
Tagged version
Stable version
Learn more about best practices

Repository

github.com/luxfi/zapdb

Links

Open Source Insights

Documentation ¶

Overview ¶

Command zapdb-replicate is the sidecar + init-container binary for streaming-replicating Lux ZapDB chain state to S3 (or any hanzoai/vfs-supported backend) with per-block age encryption.

Subcommands:

replicate        — daemon: ticks at --interval, publishes a manifest
                    per tick, advances HEAD.json.
restore          — one-shot: reads HEAD, applies full + increments
                    into an empty --path. Intended for init containers.
prune            — garbage-collect manifests + blocks older than the
                    Nth-most-recent full snapshot.
version          — print build version.

Both daemon and one-shot modes read the same YAML config file (default: /etc/zapdb-replicate/config.yaml). Flags override.

Source Files ¶

View all Source files

main.go

Directories ¶

Path	Synopsis
internal
manifest Package manifest defines the JSON metadata blobs that describe each snapshot of a ZapDB and the HEAD pointer that names the current chain of full + incremental manifests.	Package manifest defines the JSON metadata blobs that describe each snapshot of a ZapDB and the HEAD pointer that names the current chain of full + incremental manifests.
replica Package replica owns the backup-side wiring: open a ZapDB read-only, take a snapshot, stream the badger Backup bytes through hanzoai/vfs (4 KiB content-addressed age-encrypted blocks), and publish a manifest naming the produced block list.	Package replica owns the backup-side wiring: open a ZapDB read-only, take a snapshot, stream the badger Backup bytes through hanzoai/vfs (4 KiB content-addressed age-encrypted blocks), and publish a manifest naming the produced block list.
restore Package restore is the init-container side: read HEAD.json from the backend, walk the manifest chain (full + increments in order), stream each one through hanzoai/vfs into db.Load(r).	Package restore is the init-container side: read HEAD.json from the backend, walk the manifest chain (full + increments in order), stream each one through hanzoai/vfs into db.Load(r).
state Package state owns the replicator's local watermark file.	Package state owns the replicator's local watermark file.

?	: This menu
/	: Search site
f or F	: Jump to
y or Y	: Canonical URL