-
Notifications
You must be signed in to change notification settings - Fork 16
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
For Cycle 25 #849
Comments
Please update the BSQ rate for Cycle 25. #850 |
Approved for growth 👍 |
Approved for ops |
This CR is for contributions delivered in Cycle 24, just missed the deadline last month, so the rate is correct. I will do a separate CR for Cycle 25. |
I didn't know these tasks were meant for last cycle. Still, the rate should be the one for this cycle as I understand from: #818 (comment) As you're benefiting to the DAO by using Cycle 24's rate, I won't fight much about this, but I think it's worth noting it for next cycles. |
No these contributions were done in Cycle 24 so I should use the rate for Cycle 24, I'm only submitting it in Cycle 25 due to missing the proposal phase deadline |
I think all compensation requests should use the current cycle BSQ rate to avoid any gaming of the system, especially since that's the implicit consensus and no other system has been suggested. I can see the case for ops compensation always using the rate for the cycle they pertain to, but consensus for such a change should be sought first in my opinion. Other exceptional cases might arise, such as deferring a CR to avoid the whole cycle failing as seen earlier this year. |
Yeah ops stuff is monthly so no gaming of the system is possible |
Issuance cannot be displayed as there were errors in the comp request |
Close as accepted. |
Summary
1833
Contributions delivered
Check out the new https://bisq.markets/ website
The text was updated successfully, but these errors were encountered: