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 #66

Closed
sqrrm opened this issue May 1, 2018 · 2 comments
Closed

For April 2018 #66

sqrrm opened this issue May 1, 2018 · 2 comments
Assignees

Comments

@sqrrm
Copy link
Member

sqrrm 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: 112
  • BSQ address: B1EFcs4HsAijnxFwZB8QudD5wNTRwTUnNGJ

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 2 bitcoin nodes x 50 and one subscription to bitcoinaverage at USD12, price node run by Manfred.

This month I tried moving over price node and seed node to my control but the service I used is not the most reputable (at least I would not consider them after this incident). They shut down my VPS quoting cryptocurrency mining when I was only running one seed node and nothing else on that particular instance. I couldn't get an answer to why they actually shut it down but I would have to find a more solid solution to be able to take seed and price node back.

@cbeams
Copy link
Member

cbeams commented May 8, 2018

Thanks, @sqrrm. Per bisq-network/proposals#13, in future compensation requests, please add monthly report comments on your respective roles' issues, e.g.

And be sure to backreference your compensation requests in those comments, e.g. with a /cc bisq-network/compensation#66 so that bi-directional links exist on both the compensation request and role issue sides.

See also the more detailed comments and rationales I left about doing this on @mrosseel's and @Emzy's compensation requests:

@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