lightwalletd-rs 0.2.0
Beta. lightwalletd-rs is a caching proxy between a zebrad full node and Zcash light wallets: gRPC (CompactTxStreamer) toward wallets, JSON-RPC toward the node. All 20 CompactTxStreamer methods are implemented. This release puts limits on requests that 0.1.1 served without any, so the minor version moves. A light wallet syncing normally hits none of them.
Radar summary of the original source
A release published by the tracked source.
This is a source-linked software release record. Follow the original release page for artifacts, compatibility notes, and installation details.
- Status
- Published release
- Source
- Lightwalletd Rs releases
- Source activity
- Confidence
- Discovery still being checked
Lightwalletd Rs
A Rust lightwalletd for Zcash: a caching proxy that serves compact blockchain data to shielded light wallets over gRPC.
Radar summary of the original source
Related activity
- Original source
jpgonzalezra/lightwalletd-rs
A Rust lightwalletd for Zcash: a caching proxy that serves compact blockchain data to shielded light wallets over gRPC.
- Original source
lightwalletd-rs 0.1.1
Beta. lightwalletd-rs is a caching proxy between a zebrad full node and Zcash light wallets: gRPC (CompactTxStreamer) toward wallets, JSON-RPC toward the node. All 20 CompactTxStreamer methods are implemented. Highlights: GetLightdInfo fills in lightwalletProtocolVersion, which 0.1.0 left empty. Clients check that field before requesting non-default pool types, so an empty value pushed them back to shielded-only scanning even though this server serves transparent and Ironwood data inside compact blocks (ADR 0031).
- Original source
lightwalletd-rs 0.1.0
First public release (beta). lightwalletd-rs is a caching proxy between a zebrad full node and Zcash light wallets: gRPC (CompactTxStreamer) toward wallets, JSON-RPC toward the node. All 20 CompactTxStreamer methods are implemented. Highlights: redb-backed compact-block cache with windowed concurrent ingest, reorg rollback and bounded auto-recovery. Served block ranges are verified to be one chain; a detected splice aborts the stream instead of being served (ADR 0027).