redshiftzero

I wrote a CLI tool in Golang that does the above (using go `libexif` bindings) https://github.com/redshiftzero/scrubber minus the sandboxing part - reads in an image file, outputs it and also...

There is not, but that is a good idea!

> The general suggestion is to have separate table to handle backup code logic. Is that okay to add? If we need to add a table (which it sounds like...

For each address/row, we allocate: * "1_000__000_000","upenumbra" * "100","gm" * "1","cube"

# SpendN Costs in size per Spend: * 1 proof (iirc Groth16 proofs are constant size, and I believe are 3 group elements so let’s say 192 bytes) * 1...

ah true! I've updated the calculations above to only use a single balance commitment per ActionN and corrected the size of a Groth16 proof (each proof is two G1 elements...

seems like this exists now (https://github.com/penumbra-zone/penumbra/blob/main/scripts/docker_compose_freshstart.sh), closing

ahh ok, thanks for clarifying

Next step here is to use the go buf build process

Based on synchronous discussion 02/15/2024, the plan here is to: - Set the initial false positive rate at mainnet launch to that which corresponds to a target detection rate of...