Jack Grigg

One possible mechanism for this is a `CODEOWNERS` file, which can be used to [inform GitHub about code ownership](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners). This would however be contingent on those code owners all having...

For now we will consider "maintainers" separately from "PR reviewers", and use the `CODEOWNERS` approach to define the maintainers. This is sufficient for now, because whole-codebase maintainers need permissions equivalent...

The simplest solution is to just pick an anchor N blocks before the current chain tip. There is a community consensus in Bitcoin of waiting 6 blocks (about an hour)...

Per #6679 it would be useful for this RPC to also indicate somewhere the "locked" balances that are unspendable as of the time of the RPC call (similarly to how...

In ZIP Sync today, we decided that: - We would specify the multi-TLV format using prefix byte 0xF7. - Concatenated TLV tuples. - Type code 0x00 is an optional "no...

I've replaced the old contents of this PR (which just reverted the prior content that was removed from the original ZIP 302 PR) with an initial draft following what was...

`librustzcash` pins all its dependencies, so all the Rust crates need to be updated in https://github.com/zcash/librustzcash first.

We now expose this as: - `zcash_client_backend::data_api::wallet::create_pczt_from_proposal` - `pczt::roles::prover::Prover` - `pczt::roles::signer::Signer` - `pczt::roles::combiner::Combiner` - `zcash_client_backend::data_api::wallet::extract_and_store_transaction_from_pczt`