v0.5.1
What's Changed Add support for the zakura backend by @emersonian in https://github.com/zcash/lightwalletd/pull/573 Release v0.5.1: bound oversized client input (GHSA-q2c2, GHSA-6ppp, GHSA-4hp3) by @LarryRuane in https://github.com/zcash/lightwalletd/pull/574 Full Changelog: https://github.com/zcash/lightwalletd/compare/v0.5.0...v0.5.1
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 releases
- Source activity
- Confidence
- Source-linked record
Lightwalletd
Lightwalletd is a backend service that provides a bandwidth-efficient interface to the Zcash blockchain
Radar summary of the original source
Related activity
- Original source
v0.5.5
Changed The block ingestor no longer exits when getbestblockhash fails. A single failed call (for example HTTP 429 "Too many connections" from a loaded zebrad or zakura backend) used to call Log.Fatal, dropping every in-flight client stream; replicas sharing one backend then exited and reconnected together, adding to the overload. It now logs a warning and retries with a capped exponential backoff (1s to 30s), raises the log to Error after 5 minutes of continuous failures, and logs once when the RPC recovers. Malformed replies stay fatal.
- Original source
zcash/lightwalletd
Lightwalletd is a backend service that provides a bandwidth-efficient interface to the Zcash blockchain
- Original source
v0.5.4
Changed GetAddressUtxos and GetAddressUtxosStream now pass startHeight and maxEntries to the backend getaddressutxos RPC, instead of only applying them to the reply. No backend implements the arguments yet, and a backend that doesn't implement them ignores the extra JSON keys, so on its own this changes nothing: the client-side filter stays, and correctness never depends on the backend honoring them.