Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discussion: Sequential condition resolution #3494

Open
cygnusv opened this issue Apr 30, 2024 · 2 comments
Open

Discussion: Sequential condition resolution #3494

cygnusv opened this issue Apr 30, 2024 · 2 comments
Assignees
Labels
Scoping Closed by decision making, not code

Comments

@cygnusv
Copy link
Member

cygnusv commented Apr 30, 2024

Study supporting sequential resolution of conditions to support multistep condition resolution. For example, a condition may involve returning the result of a function call and feeding the result to a second function call (this becomes more interesting when the function calls are in different chains)

@cygnusv cygnusv added the Scoping Closed by decision making, not code label Apr 30, 2024
@derekpierre
Copy link
Member

derekpierre commented May 1, 2024

A couple thoughts here:

  1. The functionality could be specific to CompoundAccessControlConditions, and can perhaps be done with some tweaking here - https://github.com/nucypher/nucypher/blob/main/nucypher/policy/conditions/lingo.py#L169, and perhaps the use of specific context variables for compound conditions...just an initial thought
  2. There is a potential downstream effect on the use of multicall (Use multicalls when evaluating two or more CBD conditions #3051), since conditions that depend on other condition results probably can't be executed together in the same multi-call. It is something that can probably be worked around with some execution grouping logic when the time comes, but it is something interesting nonetheless.

@jdbertron
Copy link

jdbertron commented May 2, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Scoping Closed by decision making, not code
Projects
None yet
Development

No branches or pull requests

5 participants