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

Change GEN to boost calculation #13

Open
EzraWeller opened this issue Oct 27, 2020 · 2 comments
Open

Change GEN to boost calculation #13

EzraWeller opened this issue Oct 27, 2020 · 2 comments
Assignees

Comments

@EzraWeller
Copy link

Is your feature request related to a problem? Please describe.
Screen Shot 2020-10-27 at 7 38 36 PM

This is not a huge problem, but this is a simple proposed fix that may help UX considerably if there are no issues with it.

Describe the solution you'd like
The "GEN required to boost" amount on a regular proposal should count all proposals currently in pending as boosted, to avoid the confusing situation where a proposal goes into pending, the boosting threshold goes up, and the pending proposal no longer meets the threshold and must be moved back to the regular queue.

This may sometimes overestimate the actual cost to boost, but it's probably worth it.

Describe alternatives you've considered
Changing the protocol, which is much harder.

Additional context
Add any other context or screenshots about the feature request here.

@jellegerbrandy jellegerbrandy transferred this issue from daostack/alchemy Feb 11, 2021
@jellegerbrandy
Copy link
Contributor

Ezra, can you confirm that we REALLY want this?

@EzraWeller
Copy link
Author

I think it's definitely worth getting in a test environment and seeing how it feels -- it could be a pretty significant improvement if it works well.

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