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

[DAO] Cfund proposal acceptance order not following the timestamp order of when the proposal is accepted #739

Open
chasingkirkjufell opened this issue Jul 31, 2020 · 0 comments

Comments

@chasingkirkjufell
Copy link
Contributor

Currently:
If a proposal is passed through voting but the funding in the pool is not enough, the proposal will be in the "accepted waiting for funding" state as expected. But when later on proposals are also accepted requesting for less funding, the later proposals will be locked in first and take away the available funding.

Expectation:
Even when a proposal with less funding is accepted, the previously accepted proposal should have priority in funding from the pool and no proposals after it should be able to lock away the funding before it does.

An idea for rare scenario, if 2 proposals are accepted at the same block or block cycle, only in this case should the proposal with less funding be locked in first.

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

No branches or pull requests

1 participant