str4d

Improve UX for Poseidon chip

1

One of the 0xPARC participants found the Poseidon chip interface tricky to work with. We should have a look over the API, as well as the wrapper they created around...

Show how to actually create and verify proofs in the user guide

3

We currently use `simple-example.rs` to show how to write circuits, but that file only uses the `MockProver` to test itself. We should have a page showing how to implement keygen,...

Design a way to "pin" the result of floor planning

2

Circuits need to specify the floor planner that they use, because the floor planner has explicit power to alter the structure of the circuit (and thus the verifying key). Once...

Once #195 is implemented, floor planners will be able to reason about and control the horizontal aspects of the circuit. The selector combining optimisation is currently baked into the proving...

Add an API to construct a Halo 2 circuit from a set of constraints

4

At RWC I was chatting with [Wei Dai](https://twitter.com/_weidai), who mentioned (I think? I talked to a lot of people) that Anoma (was it?) are working on a specification called Vampir...

Improve error reporting

2

Things I've noticed: - ~~[ ] Error types should implement `PartialEq` (so they can be checked in tests).~~ - Not doing any more (because `plonk::Error` now has a case that...

Remove `Self::default()` usage in `Circuit::without_witnesses` for examples

1

Imagine the following circut that has two fields: a value, and a structural parameter. ```rust struct MyCircuit { value: Value, width: usize, } ``` when implementing the `Circuit` trait, it...

Consider adding an API that enables application circuits to be built across both fields

1

The user-facing API in #251 focuses on a single-field circuit, which is much easier for crate users to reason about (as they don't need to handle deferreds, or the way...

Add sections to the user guide explaining witness optionality

2

One of the design choices we made in `halo2_proofs` is that we want circuit synthesis and witness generation logic to be closely-coupled, to reduce chances for error (a design choice...

Implement the recursive proof verifier

1

This will be the equivalent of `halo2_proofs::plonk::verifier`, but for the recursive proofs generated by `halo2`.