nucypher
nucypher copied to clipboard
nucypher
Threshold Access Control (TACo) runtimes for the Threshold Network
**Type of PR:** Feature **Required reviews:** 2 **What this does:** TBD **Issues fixed/closed:** TBD **Why it's needed:** TBD **Notes for reviewers:** TBD
**Type of PR:** Code Removal **Required reviews:** 2 **What this does:** Fully deprecate the `alice`, `bob`, and `contacts` CLI and supporting tests.
Suggestions from @theref Presently, conditions can only be evaluated against contract functions that return integers and strings. Conditions can be more flexible by also evaluating against functions that return structs,...
The idea behind this is to create 'nucypher' docker images automatically using GH actions. The trigger could be a tag like "dev-". This could facilitate deploying these new images using...
In the interest of future protocol changes and managing backwards compatibility let's introduce a version field to conditions using semantic versioning. Ursulas can encounter and handle old condition versions appropriately.
With the advent of nucypher-core-python `f6a6163` (and the upcoming 4.0 stable or whatever), we need to be sure we're casting into and out of our newtypes properly via the python...
Presently, the 'conditional' logic lives in `ConditionLingo` and the classes surrounding it. So what is "Conditions", with respect to: * Transiting the wire * Being represented in other languages (obviously...
**Type of PR:** - [ ] Bugfix - [ ] Feature - [ ] Documentation - [X] Other **Required reviews:** - [ ] 1 - [ ] 2 - [X]...
