-
Notifications
You must be signed in to change notification settings - Fork 353
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
Close proposal on membership change #157
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm.
This is becoming complex, but at the same time, more and more useful. It just occurred to me that it would be nice for flex multisigs to request the hook directly to their group, on creation. But, now that I think of it, this has security concerns... I wonder if this is related to the "listeners" functionality... it would require something like a "publish & subscribe" contract / functionality. |
Yeah, I assume an external administrator to set up all contracts. Most of these steps need admin access anyway and it is hard to write robust init scripts as contracts. The "listener", light weight pub-sub solution that runs outside of the TX would open up a lot of doors. But that begs a lot of questions. Notably, who pays the gas and where we enforce limits |
Yes... besides gas, I can think of timeouts, retries, blacklists, whitelists, evictions / purging, priorities, ... |
61216a7
to
9b92138
Compare
Co-authored-by: Mauro Lacy <maurolacy@users.noreply.github.com>
b6c9788
to
e9a2300
Compare
Based on #156 (merge that first)
Addresses #141 (just the simple solution to show hooks, need a second PR to close issue)
We just need to optimize the query (add secondary index to proposals map), otherwise this is ready to review