penumbra

penumbra copied to clipboard

We will need to check the validity of nullifiers in circuit. We derive nullifiers using rate 3 poseidon so we need #714 to be implemented first.

redshiftzero

This is a placeholder ticket for implementing a zk `VoteProof`. Currently we do not have a transparent proof for voting (or governance support yet), so part of this work is...

redshiftzero

This is a placeholder ticket for implementing a zk `SwapProof`. There is a transparent `SwapProof` added in #1052 but note it's just a placeholder. Since it is very similar to...

redshiftzero

This is a placeholder ticket for implementing a zk `SwapClaimProof`. Currently we do not have a transparent proof for swap claims, so part of this work is writing down what...

redshiftzero

This ticket is for implementing a zk version of the `OutputProof`. It requires #711 such that `OutputProof`s can be generated in `pcli` and verified in `pd`. Status so far: *...

redshiftzero

For both the `SpendProof` and `OutputProof` we'll need to check the integrity of note commitments in circuit. Requires: Poseidon circuit implementation https://github.com/penumbra-zone/penumbra/issues/714

redshiftzero

This is a placeholder ticket for implementing a zk `UndelegateProof`. Currently we do not have a transparent proof for undelegations, so part of this work is writing down what the...

redshiftzero

This is a placeholder ticket for implementing a zk `DelegateProof`. Currently we do not have a transparent proof for delegations, so part of this work is writing down what the...

redshiftzero

In #1087 we will provide a way for clients to set their `Clue` precision based on network conditions. We should check the precision of `Clue`s (included in transactions as of...

redshiftzero

FMD: initial `Clue` parameter selection

4

Write some code to, based on current network conditions - i.e. rate of transactions per epoch - provide a reasonable choice of `Clue` parameters, i.e. as a user if we...

redshiftzero