Daira-Emma Hopwood

Merging #670 into this issue: > There isn't any specification for how mempools should check the lock time. Since mempools are used to create the block template, this can result...

According to http://bitcoin.stackexchange.com/questions/3343/what-is-the-longest-blockchain-fork-that-has-been-orphaned-to-date , Bitcoin hasn't had a fork longer than 4 blocks (other than those due to bugs). Obviously block sizes and the target block interval are different for...

On #3606 I said: > A significant advantage we have in Sapling is that outputs are very cheap; it only takes about 0.2 seconds to make an output proof (I...

Arguing the other side: while output proofs are cheap to create, they are the same cost to verify as spend proofs, and an output description takes 948 bytes on the...

Given the discussion so far and the 2.0.2 schedule, it seems likely to me that we'll be able to agree on a policy in time to implement it for 2.0.2.

These three PRs implemented the current behaviour of librustzcash which is to allow selection between three possible padding rules for each of Sapling and Orchard: * https://github.com/zcash/librustzcash/pull/1065 * https://github.com/zcash/sapling-crypto/pull/109 *...

Is scanning work at the chain tip actually a bottleneck? I would have thought that it's desirable to always scan the chain tip when we see new blocks, and that...

> On desktop I assume we just get the symbols from the C compiler itself, but on Android they came from the NDK which no longer provides them. On a...

> We currently use SQLite via the `rusqlite` crate's `bundled` flag, which automatically compiles and bundles SQLite using whatever C compiler the `cc` toolchain picks up. Technically we shouldn't do...

Ah, the `cc` crate used to build the bundled SQLite will pay attention to `CC` and `CFLAGS` environment variables (which can be configured per-platform): https://github.com/rust-lang/cc-rs#external-configuration-via-environment-variables I verified that `cargo clean;...