Jack Grigg
Jack Grigg
The question I have is primarily how we connect things like Android coroutines into the Rust async ecosystem, and whether that is an effective way to manage the necessary work...
Currently the `utxo` table has columns for storing the transaction ID, and the mined block height. These are almost always duplicative of entries in the `transaction` table, and having them...
For v4 and below transactions, any change to the authorizing data would produce a new transaction ID. From the perspective of `zcash_client_backend`-based wallets (currently only `zcash_client_sqlite` that we know of),...
```suggestion /// The set of domains in which $PRF^\mathsf{expand}$ is defined. /// This currently only includes domains used in Orchard. /// TODO: refactor calls of $PRF^\mathsf{expand}$ for Sapling /// to...
Once we've ensured that the full API is documented, we can enable this to ensure we don't merge undocumented APIs in future.
Once we've ensured that the full API is documented, we can enable this to ensure we don't merge undocumented APIs in future.
We likely won't publish this until we are ready to publish `zcash_client_sqlite 0.4.0`, in case the latter requires changes to this crate.
We pass the `recipient` type to `Domain::note_plaintext_bytes` in order to make `d` available, because the `note` type we have for our Sapling impl only contains `g_d`. Once #454 is resolved,...
The `sapling::Note` type was originally a circuit-specific type in the `sapling-crypto` crate. As such, it only stored `g_d` because that's what a note was defined to contain inside the circuit....