sohkai
commented
4 years ago For the token-oracle , the user would select any entity, then select an instance of the token oracle (each instance corresponds to a token) and that app would then expose additional configuration fields (in this case just the balance requirement) to the user.
In these cases, we would also have to deploy this oracle contract for the organization before creating the permission (at least two transaction steps).
We'd probably want to standardize a factory API for these oracles. Although in the case of the TokenOracle, it's interesting that it's an AragonApp; I had never considered "installing" oracles like this and may subvert the need for a factory API.
Is your feature request related to a problem? Please describe. ACL Oracles (and more broadly acl parameterization) offer ways to customize basic permissions, but currently there is no way to display ( #821 ) or create/modify these parameters.
Describe the solution you'd like It would be nice to have ACL Oracles that are installed in the org to detected by the Permissions app, and provide a prompt for the user when granting permissions to add the oracle. If there is a standard for this it may be possible for the ACL Oracle to provide frontend code to inject into the signer panel in permissions.
For the token-oracle , the user would select any entity, then select an instance of the token oracle (each instance corresponds to a token) and that app would then expose additional configuration fields (in this case just the balance requirement) to the user.
Describe alternatives you've considered None
Additional context