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

Pricenode Operator #14

Open
cbeams opened this issue Sep 4, 2017 · 220 comments
Open

Pricenode Operator #14

cbeams opened this issue Sep 4, 2017 · 220 comments
Assignees
Labels
team:ops https://bisq.wiki/Ops_Team

Comments

@cbeams
Copy link
Member

cbeams commented Sep 4, 2017

Docs: https://bisq.wiki/Pricenode_Operator
Team: @bisq-network/pricenode-operators

@cbeams
Copy link
Member Author

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 pricenode operator Pricenode Operator Jan 2, 2018
@cbeams cbeams added role and removed role:op labels Jan 3, 2018
@cbeams
Copy link
Member Author

cbeams commented Feb 16, 2018

@cbeams
Copy link
Member Author

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
Copy link
Member Author

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-deprecated#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
Copy link
Member Author

cbeams commented Apr 4, 2018

2018.03 report

Alas, I have still not finished the review and merge of bisq-network/bisq-pricenode-deprecated#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
Copy link
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
Copy link
Member Author

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
Copy link
Member Author

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.

@Emzy
Copy link

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.

@Emzy
Copy link

Emzy commented Dec 5, 2022

Cycle 42 report

Running 1 instance

  • Removed Qouine price provider

/cc bisq-network/compensation#1199

@devinbileck
Copy link
Member

Cycle 42 report

Running 1 instance.

  • Removed Qouine price provider

/cc bisq-network/compensation#1202

@mrosseel
Copy link
Member

mrosseel commented Dec 8, 2022

Cycle 42 report

Running 1 instance.

  • Removed Qouine price provider

/cc bisq-network/compensation#1204

@alexej996
Copy link
Member

alexej996 commented Dec 21, 2022

Cycle 43 report

Running 1 instance.

/cc bisq-network/compensation#1210

@devinbileck
Copy link
Member

Cycle 43 report

Running 1 instance.
Nothing to report.

/cc bisq-network/compensation#1213

@Emzy
Copy link

Emzy commented Jan 7, 2023

Cycle 43 report

Running 1 instance

  • Nothing to report.

/cc bisq-network/compensation#1214

@mrosseel
Copy link
Member

Cycle 43 report

Running 1 instance.

/cc bisq-network/compensation#1226

@alexej996
Copy link
Member

alexej996 commented Jan 22, 2023

Cycle 44 report

Running 1 instance.
Nothing to report.

/cc bisq-network/compensation#1230

@Emzy
Copy link

Emzy commented Feb 6, 2023

Cycle 44 report

Running 1 instance

  • Nothing to report.

/cc bisq-network/compensation#1232

@devinbileck
Copy link
Member

Cycle 44 report

Running 1 instance.
Nothing to report.

/cc bisq-network/compensation#1234

@mrosseel
Copy link
Member

Cycle 44 report

Running 1 instance.

/cc bisq-network/compensation#1242

@alexej996
Copy link
Member

alexej996 commented Feb 21, 2023

Cycle 45 report

Running 1 instance.
Nothing to report.

/cc bisq-network/compensation#1248

@Emzy
Copy link

Emzy commented Mar 8, 2023

Cycle 45 report

Running 1 instance

  • Nothing to report.

/cc bisq-network/compensation#1252

@devinbileck
Copy link
Member

Cycle 45 report

Running 1 instance.
Nothing to report.

/cc bisq-network/compensation#1253

@alexej996
Copy link
Member

Cycle 46 report

Running 1 instance.
Nothing to report.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team:ops https://bisq.wiki/Ops_Team
Projects
None yet
Development

No branches or pull requests

9 participants