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

For April 2018 #64

Closed
Emzy opened this issue May 1, 2018 · 3 comments
Closed

For April 2018 #64

Emzy opened this issue May 1, 2018 · 3 comments
Assignees

Comments

@Emzy
Copy link

Emzy commented May 1, 2018

Basic information

Specify the amount of BSQ you are requesting, and the BSQ address that amount should be paid to:

  • BSQ amount requested: 400
  • BSQ address: B16X76GXZ3hDTkDRiRtb1bYN1bAuDpP7nSE

Details

Provide links to the work you are requesting compensation for, along with any comments or explanations that will help stakeholders understand its value.

Running of 3 Bitcoin Fullnodes.
3 onion address
3 clearnet address
3 VPS servers and one dedicated server.
See: bisq-network/roles#67

Running one Pricenode and one Seednode server.
Paying for a $12 USD / Mounth bitcoinaverage.com Subscription (for the Pricenode)

Events on one Fullnode: Hard disk failure that left the sever without the blockchain, needed a complete resync.

Running the bisq-contrib mailing list server. Approving and rejecting mails.
Setup of the GitHub mailing list.
See: bisq-network/lists#5

Compensation calculation:

no Setup, only maintenance

Monthly costs nodes: 5* VPS (50 / node) -> 250
Monthly costs dedicated node 100
Monthly costs mailinglist server: 50
=400

@cbeams
Copy link
Member

cbeams commented May 8, 2018

Thanks, @Emzy. Some feedback:

Per bisq-network/proposals#13, please write up your comments about each role you play as a comment on the respective role issue. I just wrote very similar feedback to @mrosseel in #63 (comment), so I'll just quote it below (with some slight modifications):

Rather than grouping stuff into a single section directly within your compensation request, please post a monthly update comment on each of the respective roles, e.g.:

Doing things this way maximizes the usefulness of these reports over time. Mostly, people will not go digging through individual compensation requests to see who has been hosting what, or how much they paid to host those things on various hosting providers. But if all operators consistently post monthly report comments on their respective operator role issues, it becomes very easy for operators new and old alike to see who is hosting what where, which hosting providers are overused from a a censorship resistance / network resiliency perspective, which contributors are overloaded / operating too much stuff, to evaluate which hosting providers are delivering the best "bang for the buck", etc.

Many thanks in any case for all the operations work you're doing here. I think no one outside of Manfred is hosting more nodes than you. Hopefully the changes described above can help in our efforts to decentralize this work further.

@cbeams
Copy link
Member

cbeams commented May 8, 2018

@Emzy, I noticed after the fact that you did actually do a monthly Pricenode Operator report at bisq-network/roles#14 (comment). Thanks. If in the future, you backreference your compensation requests from your role report comments, e.g. with a /cc bisq-network/compensation#64, it'll ensure that everything is discoverable in a bi-directional way. You can see this in effect in my compensation requests, e.g. this month's at #68. Scroll to the bottom and you'll see the back-references in the issue timeline coming in from the individual role report comments.

@cbeams cbeams mentioned this issue May 8, 2018
@cbeams
Copy link
Member

cbeams commented May 8, 2018

Closing as complete, see #58 (comment).

@cbeams cbeams closed this as completed May 8, 2018
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