Arjun Hassard

Outstanding questions (@cygnusv @derekpierre): - How is the authority to update a given `conditionset` rolled out to an end-user (i.e. wallet-level granularity) - Potentially create master CRC contract, then revoke...

This is an acceptable design for the narrower question of 'how are conditions updated'. The framework that's missing would answer 'who is allowed to update conditions?', 'how do they they...

I've moved this to v8.0.0 for now. There is useful thinking contained in this issue that will inform the OpenDRM working group, the contract work for which will likely end...

Recent progress with the new underlying cryptosystem finally puts us in a position to develop out the economics of CBD, including the chargeable unit(s) of service, the structure of adopter-facing...

Units of service Unless you assume honest interactions with the network by all potential users (or even just the users on a sponsor-defined whitelist), all subscription models must account for...

Economic impact of _unpredictable_ DKG Rituals We know that DKG rituals are the most constrictive economic chokepoint on the network and service. So let’s consider a generic application, and walk...

- [ ] Use existing RPC conditions to build off-the-shelf condition set for decryptor to control ENS name(s) - [ ] Write up walkthrough tutorial and add to [Advanced Usage...

Until an adopter specifically requests a (more efficient) way to evaluate multiple conditions concurrently, this can be bumped to the next version

From today's 7.0.0 scope-reduction exercise; trust/parameter packages can also incorporate distinct (and transparent) choices between i. semi-decentralized highly reliable long-term cohorts (NuCypher nodes + professionalized stakers + adopters own nodes)...

(Purely illustrative to elicit reaction from adopters; wrt concept as whole, inherent trade-offs, swappable components, etc.)