David Núñez

The use case that made me think of this was that we use constant sorrow to define the possible contract deployment modes (`BARE`, `IDLE`, `FULL`) and in the CLI there's...

This depends on how are shares combined. In Umbral, ciphertext shares can be combined in the end of the workflow by Bob, so it was OK to protect shares' indices...

I think that's fine. Initially they were separated, if I recall correctly. There's even a flag `provide_proof` for the reencryption function, so it makes sense.

What's the motivation for using hex encoding for stuff under 33 bytes?

Hey @fjarri, this is a very cool idea :) This is basically a Schnorr signature of the metadata by Enrico. I need to think more about it, but it doesn't...

I've been thinking a bit about this, and although I don't see anything incorrect in your original approach, I think we can achieve the same thing following a more common...

> ...but what advantage are we gaining by using a Schnorr sig over a digest (HMAC-ish)? Just that Enrico can optionally reuse the private key as a branding mechanism? The...

> ...but what advantage are we gaining by using a Schnorr sig Umbral is already using a Schnorr signature internally, so reusing the same cryptographic material to also associated metadata...

Hi @Himan000, when we designed the APIs for Umbral, we decided that both correctness keys and cfrags were just attached to the capsule on running time, and not when serialized....

Hi @Himan000, We currently have something similar to that. When Alice creates the policy public key, she provides a label (which is very similar to a condition) and the kfrags...