Jack Grigg

Rebased on master to fix merge conflicts caused by parts of this PR being merged in other PRs. I think this PR is finally small enough that it could be...

I'm starting to think that we might want to relax the Rust parser to have an "unknown consensus branch ID" case, which allows parsing but causes a consensus failure (as...

> I'm starting to think that we might want to relax the Rust parser to have an "unknown consensus branch ID" case I've opened https://github.com/zcash/librustzcash/issues/572 for this.

This fell through the cracks. It's still a well-identified set of changes we want, but there is still work to be done, and now various merge conflicts that need resolving....

Given that there is no shutdown message and no apparent crash, the most likely cause is running out of memory. Could you run `dmesg` and check whether the log output...

@imichaelmiers and I were discussing PQ-privacy of note ciphertexts in the Zcash block chain, and came up with the following proposal for a scheme that requires no modification to the...

The above scheme is insecure because it re-uses keys. The current Zcash note encryption scheme (libsodium's `aead_chacha20poly1305_ietf`) uses a zero nonce because keys are never re-used: the ephemeral nature of...

@daira could you elaborate on the shared-secret address you are thinking of? I can imagine two different strategies consistent with that name; one of them is the proposal I outlined...

[Rebased on 5.2.0](https://github.com/zcash/zcash/compare/025ca8fb5ce54db448534fec155b818be8836b0f..681e77569e0b8c0142d4e4dc7682f64a49533c13). No change to the PR.

[Rebased on `master`](https://github.com/zcash/zcash/compare/a30655137ca18d6dcc6b02942bc1a60bd10acd47..5caeab9f44c667a2514c3f1b66ce5308c172bb89) to fix a linker error.