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

Bisq Pricenode Operator #14

Open
cbeams opened this Issue Sep 4, 2017 · 42 comments

Comments

Projects
None yet
6 participants
@cbeams
Member

cbeams commented Sep 4, 2017

Docs:
Team: @bisq-network/pricenode-operators
Primary owner: @cbeams (but all operators should submit monthly reports)

@cbeams

This comment has been minimized.

Member

cbeams commented Nov 15, 2017

@ManfredKarrer, I've assigned you to this role, as I believe you're the only contributor running pricenode(s) at the moment.

@cbeams cbeams changed the title from pricenode operator to Pricenode Operator Jan 2, 2018

@cbeams cbeams added role and removed role:op labels Jan 3, 2018

@cbeams

This comment has been minimized.

@cbeams cbeams self-assigned this Feb 19, 2018

cbeams added a commit to cbeams/bisq that referenced this issue Feb 19, 2018

@cbeams

This comment has been minimized.

Member

cbeams commented Feb 19, 2018

I've just assigned myself to this role, as I have now taken over one of @ManfredKarrer's pricenodes. See the commit / PR above for details.

@cbeams

This comment has been minimized.

Member

cbeams commented Mar 1, 2018

2018.02 report

This is my first report, now that (per the comment above), I've now taken over one of Manfred's pricenode onion addresses.

This pricenode is now backed by code at the HEAD of my cbeams/bisq-pricenode:refactor branch, which will be merged asap (see bisq-network/bisq-pricenode#7). See my comment in Pricenode Maintainer (#5) for more details on that.

In any case, I'm servicing between 25 and 40 clients with this pricenode at any given time, and it looks like it's going to run me around $7 / month on Heroku to keep it running.

/cc bisq-network/compensation#40

@cbeams cbeams referenced this issue Mar 1, 2018

Closed

For February 2018 #40

1 of 1 task complete
@cbeams

This comment has been minimized.

Member

cbeams commented Apr 4, 2018

2018.03 report

Alas, I have still not finished the review and merge of bisq-network/bisq-pricenode#7, and therefore other pricenode operators have not yet upgraded to it. In the meantime, however, my pricenode instance, which is built from that PR branch, has been up and running without issue for a couple months. So I think we can call it a well-tested change at this point ;)

Note that @sqrrm attempted to start running his own pricenode this month, but ran into issues with his hosting provider. This instance was being built from the PR branch above as well, and that all seemed to work out fine for him. Good luck, @sqrrm, on getting your pricenode up and running elsewhere soon.

/cc bisq-network/compensation#57

@ManfredKarrer

This comment has been minimized.

Member

ManfredKarrer commented May 1, 2018

2018.04 report

Running 2 instances. Still running the old version of the price node.
No issues occurred that month.

@cbeams

This comment has been minimized.

Member

cbeams commented May 3, 2018

2018.04 report

My instance ran without any issues on Heroku this month at a cost of $7.00. I'm running v0.7.1-SNAPSHOT from commit bisq-network/bisq-pricenode@545887c.

/cc bisq-network/compensation#68

@cbeams

This comment has been minimized.

Member

cbeams commented May 3, 2018

@Emzy and @mrosseel, could you please report here on this issue about the pricenode instances you're operating in the same way that @ManfredKarrer and I have done above? Thanks.

@cbeams cbeams referenced this issue May 3, 2018

Closed

For April 2018 #68

1 of 6 tasks complete
@Emzy

This comment has been minimized.

Emzy commented May 3, 2018

2018.04 report

Running one instance. Still running the old version of the price node.
No issues occurred that month.

@cbeams cbeams removed the a:role label May 4, 2018

@cbeams cbeams referenced this issue May 8, 2018

Closed

For April 2018 #63

@ManfredKarrer

This comment has been minimized.

Member

ManfredKarrer commented Aug 30, 2018

2018.08 report

Nothing to report.

/cc bisq-network/compensation#112

@cbeams

This comment has been minimized.

Member

cbeams commented Aug 31, 2018

2018.08 report

Nothing to report.

Hosting: Heroku
Cost: $7.00
Version: v0.7.1-SNAPSHOT (from commit bisq-network/bisq-pricenode@545887c)

BSQ requested: 7+25 = 32

/cc bisq-network/compensation#114

@mrosseel

This comment has been minimized.

Member

mrosseel commented Aug 31, 2018

2018.08 report

  • 1 bitcoinaverage subscription
  • 1 pricenode running

nothing to report

bisq-network/compensation#116

@ManfredKarrer

This comment has been minimized.

Member

ManfredKarrer commented Sep 27, 2018

2018.09 report

Nothing to report.

/cc bisq-network/compensation#125

@Emzy Emzy referenced this issue Sep 29, 2018

Closed

For September #136

@Emzy

This comment has been minimized.

Emzy commented Sep 29, 2018

2018.09 report

Update to new version

/cc bisq-network/compensation#136

@cbeams

This comment has been minimized.

Member

cbeams commented Sep 30, 2018

2018.09 report

The pricenode repository has been consolidated into the main bisq-network/bisq repository, but no code has changed, so I have not updated my instance yet.

Hosting: Heroku
Cost: $7.00
Version: v0.7.1-SNAPSHOT (from commit bisq-network/bisq-pricenode@545887c)

BSQ requested: 7+25 = 32

/cc bisq-network/compensation#139

@mrosseel

This comment has been minimized.

Member

mrosseel commented Sep 30, 2018

2018.09 report

  • 1 bitcoinaverage subscription
  • 1 pricenode running

nothing to report.
Anticipating docker file rework for the next release, due to the move to the mono repo

bisq-network/compensation#141

@ManfredKarrer

This comment has been minimized.

Member

ManfredKarrer commented Oct 31, 2018

2018.10 report

Running 2 instances

/cc bisq-network/compensation#155

@mrosseel

This comment has been minimized.

Member

mrosseel commented Oct 31, 2018

2018.10 report

  • 1 bitcoinaverage subscription
  • 1 pricenode running

nothing to report.
Anticipating docker file rework for the next release, due to the move to the mono repo

bisq-network/compensation#157

@cbeams

This comment has been minimized.

Member

cbeams commented Oct 31, 2018

2018.10 report

Nothing to report

Hosting: Heroku
Cost: $7.00
Version: v0.7.1-SNAPSHOT (from commit bisq-network/bisq-pricenode@545887c)

BSQ requested: 7+25 = 32

/cc bisq-network/compensation#160

@cbeams cbeams referenced this issue Oct 31, 2018

Closed

For October 2018 #160

@Emzy Emzy referenced this issue Oct 31, 2018

Closed

For October 2018 #163

@Emzy

This comment has been minimized.

Emzy commented Oct 31, 2018

2018.11 report

  • 1 bitcoinaverage subscription
  • 1 pricenode running

/cc bisq-network/compensation#163

@Emzy Emzy referenced this issue Nov 29, 2018

Closed

For November 2018 #175

@Emzy

This comment has been minimized.

Emzy commented Nov 29, 2018

2018.11 report

  • 1 bitcoinaverage subscription
  • 1 pricenode running

/cc bisq-network/compensation#175

@cbeams

This comment has been minimized.

Member

cbeams commented Nov 30, 2018

2018.11 report

We shifted around the maxBlocks parameter a couple times this month to adjust to mining fee spikes on the Bitcoin network. Otherwise, nothing to report.

Hosting: Heroku
Cost: $7.00
Version: v0.7.1-SNAPSHOT (from commit bisq-network/bisq-pricenode@545887c)

BSQ requested: 7+25 = 32

/cc bisq-network/compensation#179

@ManfredKarrer

This comment has been minimized.

Member

ManfredKarrer commented Nov 30, 2018

2018.11 report

Running 2 instances.
There have been a few issues with fee estimation being too low. Coordinated updates of the fee services with the other operators.

/cc bisq-network/compensation#180

@mrosseel

This comment has been minimized.

Member

mrosseel commented Nov 30, 2018

2018.11 report

  • 1 bitcoinaverage subscription
  • 1 pricenode running

nothing to report.

bisq-network/compensation#181

@cbeams

This comment has been minimized.

Member

cbeams commented Dec 6, 2018

Per #1 (comment), I'll be away for the next ~2 months, but I will leave my pricenode up and running, and should be able to respond within 24-48 hours to any requests to upgrade, etc. I will not issue any monthly updates while I'm away.

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