-
Notifications
You must be signed in to change notification settings - Fork 3
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
Make proposals individual contracts #14
Comments
Cool, so a contract can deploy another contract? |
never done it but yeah, should be possible! |
That's pretty awesome. That way we could adapt the proposal logic all the time and whenever we want it seems. |
yeah! that would be the big benefit. |
I just found an issue with this idea: we established that it would be useful to be able to vote on multiple proposals at once, both for convenience and lowering transaction costs. However, that wouldn't be possible if every single one lived in its own contract. I don't think that's actually necessary, because the metadata about the decision (i.e. why were the kredits issued) should be present in the issuance anyway. And as long as we can easily update the main contract, we can still keep adjusting proposal logic. Does that make sense, or did I miss something? |
For brainstorming:
Right now every proposal has a fixed set of data and the execution logic is implemented in the main kredits contract.
What if we make every proposal its own contract with a simple standard interface to interact with the other contracts.
This could allow more flexible proposals that can be voted on.
Such proposals then could not only issue new Kredits but also send ether, deploy new contracts, etc.
The text was updated successfully, but these errors were encountered: