Larry Ruane

Probably not important to fix soon (it's been wrong for a long time). This document refers to the block ingestor and the gRPC server as two separate binaries. They were...

There should be a way, either by command-line option or at runtime, to enable logging of gRPC calls. This idea is inspired by #491 in which it's unclear if the...

Closes #488. Indicate the correct backend process name in error messages. Some error messages occur before we know if our backend is `zcashd` or `zebrad` (for example, when we're attempting...

doc: cmake: prepend "build" to functional/test_runner.py

3

This is a small follow-on to #30741. Also, improve the error message if someone runs the functional tests the old way (outside of the build directory).

This additional logging may help with debugging lightwalletd clients as it may isolate the problem to the client or server (lightwalletd) side. To see entrypoint logging, you must start lightwalletd...

return correct gRPC error codes

5

closes #497

This change is non-functional, just a clean-up, reducing tech debt. I've been meaning to do this almost from when I first started working on lightwalletd in 2019. This codebase manipulates...

add transparent data to compact block serialization

5

This PR includes changing the proto files directly, which is incorrect and is actually being done by https://github.com/zcash/lightwallet-protocol/pull/1, so these changes will have to be removed before merging. There is...

add header to compact block

1

Closes #527 The `walletrpc.CompactBlock` object has always included a `Header` field (type is byte array), but it has never been filled in (until now), so it's easy to set this...

Low-priority bugfix, follow-on to #483 - prevent segmentation fault when `lightwalletd` exits (for example, receives a control-C): ``` {"app":"lightwalletd","level":"info","msg":"Starting gRPC server on 127.0.0.1:9067","time":"2025-08-13T14:19:45-06:00"} ^Cpanic: runtime error: invalid memory address or...