Pricenode Operator #14
Comments
|
@ManfredKarrer, I've assigned you to this role, as I believe you're the only contributor running pricenode(s) at the moment. |
|
I've assigned @Emzy and @mrosseel here, as both are also running pricenodes, per https://github.com/bisq-network/exchange/blob/f73395f6f1e578909f81d4f3b5be80211ae3e01a/core/src/main/java/io/bisq/core/provider/ProvidersRepository.java#L37-L41 |
|
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. |
2018.02 reportThis 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 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. |
2018.03 reportAlas, 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. |
2018.04 reportRunning 2 instances. Still running the old version of the price node. |
2018.04 reportMy 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. |
|
@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. |
2018.04 reportRunning one instance. Still running the old version of the price node. |
Cycle 60 reportRunning one instance, available at runbtcpn7gmbj5rgqeyfyvepqokrijem6rbw7o5wgqbguimuoxrmcdyd.onion. |
|
As roles maintainer, I've updated this role's assignees as follows:
these changes reflect the current state of ProvidersRepository.java |
Cycle 61 reportMy node is still running, though will be removed in a subsequent Bisq release, as per bisq-network/bisq#7137. Once sufficient time has elapsed after that has been released, I will decommission the node. |
Cycle 61 reportRunning one instance, available at runbtcpn7gmbj5rgqeyfyvepqokrijem6rbw7o5wgqbguimuoxrmcdyd.onion. |
For Cycle 61Running 1 instance. |
For Cycle 62Running 1 instance. |
Cycle 62 reportMy node is still running, though will be removed in a subsequent Bisq release, as per bisq-network/bisq#7137. Once sufficient time has elapsed after that has been released, I will decommission the node. |
Cycle 62 reportRunning one instance, available at runbtcpn7gmbj5rgqeyfyvepqokrijem6rbw7o5wgqbguimuoxrmcdyd.onion. |
For Cycle 63Running 1 instance. |
Cycle 63 reportRunning one instance, available at runbtcpn7gmbj5rgqeyfyvepqokrijem6rbw7o5wgqbguimuoxrmcdyd.onion. |
Cycle 63 reportMy node is still running, though will be removed in a subsequent Bisq release, as per bisq-network/bisq#7137. Once sufficient time has elapsed after that has been released, I will decommission the node. |
Cycle 64 reportMy node is still running, though will be removed in a subsequent Bisq release, as per bisq-network/bisq#7137. Once sufficient time has elapsed after that has been released, I will decommission the node. |
Cycle 64 reportRunning one instance, available at runbtcpn7gmbj5rgqeyfyvepqokrijem6rbw7o5wgqbguimuoxrmcdyd.onion. |
and others
Docs: https://bisq.wiki/Pricenode_Operator
Team: @bisq-network/pricenode-operators
The text was updated successfully, but these errors were encountered: