joe

I think setting `MAX_MONEY = i64::MAX` and use the range `[-MAX_MONEY, MAX_MONEY]` makes sense. So we should undo any change which removed `MAX_MONEY`. There is no reason why we need...

> Didn't look properly at the PR yet, but it seems there is a typo and `derivate_value_base` should be `derive_value_base` I had to look it up in the dictionary since...

If we ultimately depend on the assumption "Poseidon is a PRF" anyway, then we might be able to simplify the nullifier computation. It may be worth evaluating the Reinforced Concrete...

Each address in Taiga is used in two places, spending: 1. The address is contained in each Note commitment (either as a user, or token, address) which commits to at...

Right now I think the best approach is to special case it. - [ ] Design "default" receive VPs that will be permanently integrated (#2) such as allow-all - [...

I had been assuming the asset type would be ~256 bits long, but in the case of NFTs this might be too short (although the 64 bits allocated for `v`...

We decided output note encryption should go in the VP. Tasks: - [ ] Implement in-circuit output note encryption with ElGamal-type encryption - [ ] Implement in-circuit Poseidon-based note encryption...

Context for this issue: 1. A user VP may, after reviewing the notes spent and created in a transaction, authorize the spending of some notes 2. The transaction builder may...

https://github.com/penumbra-zone/penumbra/issues/4

We should try to implement every single example VP/example userflow to ensure the base protocol supports all of them. There is a lot to do. Signature support: - [ ]...