Jack Grigg

I spent the past day building https://github.com/zcash/zcash-devtool/pull/76 to enable debugging this kind of issue. In a wallet I have access to, I observe a level 1 nil node, indicating that...

> That was on [04478c7](https://github.com/zcash/librustzcash/commit/04478c791acfb4cb1015affd17f12565f88bcc43) This is `zcash_client_sqlite 0.11.2` plus whatever was in `main` after it was merged back, in particular #1524. I don't see any changes between `zcash_client_sqlite 0.11.0`...

@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...

I'm encountering a probably-related issue where `abscissa_tokio::TokioComponent`'s dependents are called in an uncontrollable order, preventing me from async-preparing state in one component that another component requires for its own async...

> I'm encountering a probably-related issue where `abscissa_tokio::TokioComponent`'s dependents are called in an uncontrollable order On further testing, they appear to be called in the order in which the components...

We should also clarify that deployment ZIPs are entirely Deployment sections, and thus automatically satisfy that requirement on the Draft to Proposed transition.