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

Increase all compensations for OPS by 30% #401

Closed
Emzy opened this issue Dec 21, 2022 · 3 comments
Closed

Increase all compensations for OPS by 30% #401

Emzy opened this issue Dec 21, 2022 · 3 comments
Assignees
Labels

Comments

@Emzy
Copy link

Emzy commented Dec 21, 2022

Proposal:

This proposal is to increase all compensations for OPS by 30% for the Cycle 44.
Cycle 43 will be the DAO voting.

Reasoning:

  1. There is inflation compensation needed for a few years.
  2. The requirements for disk space (bitcoin blockchain) have increased.
  3. Over all the work is more than initially anticipated. (exchange rate problems, tor problems)

Outcome:

Better coverage of operating costs and stronger financial incentive to run the OPS services.

Solution:

Increase every OPS role by 30%.
List:

  • $50 -> $65 Bitcoin node operator
  • $100 -> $130 Seed node operator
  • $100 -> $130 Pricenode operator
  • $100 -> $130 Relay operator for mobile notifications
  • $200 -> $260 Mempool Explorer Operator
  • $100 -> $130 Monero Explorer Operator
  • $100 -> $130 Monitoring Operator
  • $25 -> $33 GitHub Admin
  • $100 -> $130 Forum operator

Risks:

None.

@pazza83 pazza83 added a:proposal https://bisq.wiki/Proposals re:compensation labels Dec 21, 2022
@pazza83
Copy link

pazza83 commented Jan 2, 2023

Hi @Emzy closing this as approved

@pazza83 pazza83 closed this as completed Jan 2, 2023
@Emzy
Copy link
Author

Emzy commented Jan 8, 2023

TXID: 2926fac4405fe54f71a0eaf7899ea2c53e0f751913be54a0305b259a0bda9341

@MwithM
Copy link

MwithM commented Jan 9, 2023

This proposal was already accepted, voting is unnecessary. Anyways, better leave it open because I think I remember that removing offers could cause issues.

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

No branches or pull requests

3 participants