David Núñez

Food for thought: - If we decide conditions should not updateable, then the last say, _always_, about what's the current condition associated to a given ciphertext is decided at encryption...

Just to add that for the condition smart contract approach, we could provide all the necessary functionalities to make it easy and intuitive for users, including: - Predefined conditions contracts...

@KPrasch asserted a few days ago that we already have support for updatable conditions, and I think this is partially true. A condition set could be as simple as a...

> The framework that's missing would answer 'who is allowed to update conditions?', 'how do they they gain (/lose this right?' and 'how is this authenticated?'. What I was trying...

From current CI (https://github.com/nucypher/nucypher/actions/runs/6508418168/job/17677737409): `Decryption time: 7.473639011383057 seconds`

As for 2024 this question is still open, but we have more insights than before. First, it's worth mentioning that @KPrasch already has a PoC implementation of noise that can...

> In the cryptology of nucypher, we see that '_receiving_', '_delegating'_, '_signing_' belong to respectively, Bob, Alice, and DataSource. (perhaps another case for rethinking DataSource's status as sub-character, but that's...

> Well, what exactly might we do in that scenario? Form an opinion over the signature scheme used by a DataStore? Does that make good sense do you think? We...

This issue has mainly historical value right now, as it's very PRE-centric.

Let's close this. #3372 seems more actionable than mere reporting (and I guess we don't want more logging...https://github.com/nucypher/nucypher/issues/1712)