Jack Grigg

#6069 significantly improves rescan performance for wallets with many historic shielded transactions. To benefit, those wallets need to run a `-rescan`.

https://github.com/zcash/zcash/issues/6052#issuecomment-1177966544: > So a multi-threading or batching approach to trial decryption would help mitigate the rescan performance hit from both full blocks (as we currently have) and wallets with more...

#6069 (EDIT: which has now been merged, so the `master` branch can also be tested.)

No, the disconnects shouldn't be related. The 100% loaded thread should be `zc-txnotify`, which is the wallet notification thread; it's running at 100% because currently scanning runs on a single...

@freebeego That log snippet is not enough to figure out what is going on. - What revision did you build / run? - What hardware are you running it on?...

In Halo Study Club today, we discussed this, and I made the following notes to clarifying things for myself: Assume we have a circuit that verifies some earlier proof P1....

Having talked with @ebfull again I now have a much better understanding of what he meant for the endoscalar usage. In my notes, below, treat `Fr == Fp` (i.e. I'm...

[Clarification: the discussion below assumes that 160-bit challenges can be proven secure, which had not been done at the time and still hasn't.] In Halo Study Club today, we had...

Note that the `librustzcash` crate was not written to be a public C FFI; it is only intended as an internal API for `zcashd`, and includes assumptions about how either...

Looking at `contrib/debian/copyright`, we currently only add copyright entries for files that are either actually part of our git history (e.g. the M4 build scripts), or files that become part...