str4d

Migrate to `group::coordinates`

1

Depends on https://github.com/zkcrypto/group/pull/49.

Migrate to `group::CurveAffine`

1

Depends on https://github.com/zkcrypto/group/pull/48.

Reduce code duplication in field implementations

3

Currently this library has two field implementations, the Pallas field and the Vesta field. They only differ in their prime modulus, and are otherwise almost identically implemented. This makes the...

replace double with bit shift

2

Extracted from https://github.com/zcash/pasta_curves/pull/44.

These were helper traits that we created to provide additional methods needed for `halo2_proofs` that the `group` crate traits didn't have, while we figured out what those needed additional methods...

We want to be able to leverage GPUs in `halo2`, via the [`ec-gpu` crate](https://github.com/filecoin-project/ec-gpu). This requires two changes: - The curve implementation needs to support producing the GPU kernel for...

Implement ZIP 244 txid logic for v5 transactions

3

Support for parsing v5 transactions (as specified in ZIP 225) was added in #367. However, the txid computation for v5 transactions (as specified in ZIP 244) was not implemented. This...

Size assumptions in parsing code don't hold for regtest blocks

3

The code below will write an incorrect block if the Equihash parameters are different from mainnet (e.g. for regtest blocks): https://github.com/zcash-hackworks/lightwalletd/blob/3071b5759ae5b7651d5d13c664e5eb2f5bf503f3/parser/block_header.go#L75-L77 The read side does correctly handle the length: https://github.com/zcash-hackworks/lightwalletd/blob/3071b5759ae5b7651d5d13c664e5eb2f5bf503f3/parser/block_header.go#L124-L126

Create key structure / capability diagram

3

It will be useful to have a diagram that conveys "who knows what" for Orchard's key structure, similar to diagrams we have for Sapling.

We want to ensure that we can create proofs on mobile phones, so we should be measuring and tracking memory usage of the Orchard circuit proving.