redshiftzero

Blocked on #1481

Closely related to #4076, which documents the balance commitments on a per-action basis

one last thing to figure out here actually is why we need the getrandom dependency added everywhere, since it's a dev dependency only of `decaf377`

`cargo tree --package penumbra-community-pool` (the failing package [here](https://github.com/penumbra-zone/penumbra/actions/runs/9847865112/job/27188689266)) on a5270922cafea8f89ed895e4376516bc90c82cb0 indicates that getrandom is being pulled in due to `ark-ff`: ``` penumbra-community-pool v0.79.0-alpha.1 ├── anyhow v1.0.86 ├── ark-ff v0.4.2 │...

The status of this is that `poseidon-parameters` is now rewritten to use const generics, and compiles on the target embedded platform. There are individual todos in PR https://github.com/penumbra-zone/poseidon377/pull/53 tracking the...

done in https://github.com/penumbra-zone/poseidon377/pull/53 released in https://crates.io/crates/poseidon377/1.0.0

Flagging that #1507 is very similar, might be the same underlying issue. Not sure how easy it is to write a regression test to cover this case

Suggestion from Discord discussion: 1. check all new note commitments against storage 2. if note commitment already known, write a zero byte into the note payload ciphertext 3. this triggers...

MVP: Add a command or commands to pd that will export and import a JMT snapshot

The zk proof part of this was done in https://github.com/penumbra-zone/penumbra/pull/2610