tux

I'm not against refactoring policy, tbh. Is it possible that Policy is evolving to be something more minimal and combinatoric of multiple things?

I was thinking that this could potentially raise an exception rather than return `False`. I don't like the pattern of `starting_doing_thing` returning `False`. Maybe `AlreadyLearningError`?

The deliverable that I immediately envision for minimum-viable condition programming is attaching Alice-supplied metadata to the policy (perhaps via JSON) with "re-encryption constraint variables" that allow exceptionally limited evaluation. Consider...

Would much prefer discord over Zulip personally. All my chats are in Discord these days. :) On Thu, May 20, 2021 at 19:49 str4d ***@***.***> wrote: > +1 on a...

If we know the "partial" public key of the distributed fragments, we are able to prove correctness of a signature by simply verifying the "partial" BLS signature. I believe that...

There isn't much in attack surface in those functions. It would also be pretty trivial to prevent this attack too (some simple bounds checking).

It would have to be within a specific amount of time when the arrangement was first made. Otherwise, Alice would be able to get a refund after any arbitrary time.

I absolutely agree. https://www.youtube.com/watch?v=O3lAPZHnlhM

Do you mean that you want to compute the logic gate on the plaintext and have the output be the result before you decide to compute on the ciphertext?

I'm not sure this would be that useful. I'd imagine that WebGL is far slower than what OpenCL or CUDA can achieve.