-
Notifications
You must be signed in to change notification settings - Fork 42
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 conditions for finalizing a proposal more robust #28
Comments
what does it mean for it to be consistent?
I feel like the exit mechanism is the conditional-on-pass market - you can dump your META in the conditional-on-pass market so that you're guaranteed that you will have sold if it passes |
consistent definition: twap differences between conditional markets matches some 'live price' difference between conditional markets (essentially making the price check more robust) 'live price' could mean something strict like mid price for both markets for example in strict case, lets say pass twap > fail twap but current fail mid > pass mid in less strict case, lets consider the following example:
with the new consistent check rule, other users must buy that sell wall before the proposal can end. if no one is willing to buy it up, then the proposal end time is essentially ended and the fail market still has a chance to win. |
Replaced with #59 |
currently only twaps need to be higher by threshold for proposal to pass. just relying on the twaps as currently implemented might be too easy to game.
i wonder if its better to also ensure that
this consistency check wouldn't change whether a proposal passes or not, but just delays finalizing. this gives ample time to for those who really disagree with a proposal to exit before it's allowed to pass.
https://github.com/metaDAOproject/meta-dao/blob/c88a8605cdc0d2ece4dcb25d6a0c3a89bbf7c79b/programs/autocrat_v0/src/lib.rs#L328
The text was updated successfully, but these errors were encountered: