Timelock authorizer: adaptor support #2557
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Add the notion of an entrypoint for
schedule
for actions behind the authorizer adaptor.Timelocked actions behind the authorizer adaptor (e.g. those in the LM system) cannot be called directly by the executor. Therefore, the notion of
where
is not enough forschedule
:where
is the actual action (e.g. a function in theGaugeController
),schedule
will work for timelocked actions, butexecute
will revert as themsg.sender
won't match the authorizer adaptor.where
isperformAction
in the adaptor entrypoint,schedule
will fail asperformAction
should not be timelocked.TODO:
performAction
shouldn't be able to be scheduled and used directly. Otherwise everything behind the adaptor can be executed in that delay.Type of change
Checklist:
master
, or there's a description of how to mergeIssue Resolution
N/A