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

Refinement of cross-contract call policy #188

Open
alexauroradev opened this issue Jul 11, 2022 · 1 comment
Open

Refinement of cross-contract call policy #188

alexauroradev opened this issue Jul 11, 2022 · 1 comment

Comments

@alexauroradev
Copy link

Often DAOs have a technical committee that is responsible for certain contracts and working with them. It would be wise to be able to set up a separate policy for cross-contract calls for specific contracts (and potentially for specific methods of these contracts), so such proposals are not disturbing the rest of the councils.

For example:
The DAO of the project has 20 councils. There is a DeFi committee that is responsible for liquidity of the project token. DeFi committee of the DAO consists of 3 DAO Councils. The vote 2 of 3 of them is enough to access ref.finance contracts on behalf of the DAO.

@starpause
Copy link
Contributor

Thanks for making this report. An immediate work around would be to use multiple DAOs. Following your example, you'd have a project-defi.sputnik-dao.near and project-deploy.sputnik-dao.near. Each DAO would have it's own authorization access keys and whitelist permissions for external contracts like ref.finance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants