Open cbeams opened 7 years ago
Running 1 instance. Updated to address the mempool fee estimation issue https://github.com/bisq-network/bisq/pull/4235.
Running 1 instance.
/cc bisq-network/compensation#562
Running 1 instance.
/cc bisq-network/compensation#570
Running 1 instance but temporarily removed from Bisq network due to BitcoinAverage API key issues, so not charging compensation this month
Running 1 instance. Nothing to report.
Running 1 instance. Upgraded to master in order to utilize emzy's node for fee estimation as well.
Running 1 instance.
/cc bisq-network/compensation#595
Running 1 instance.
/cc bisq-network/compensation#601
My pricenode instance is temporarily offline, will re-add after Bitcoin Average support is no longer required
Running 1 instance. Nothing to report.
Running 1 instance. Nothing to report.
/cc bisq-network/compensation#615
Running 1 instance.
/cc bisq-network/compensation#617
My instance is still offline, and soon will be brought online from a new server sans Bitcoin Average, once https://github.com/bisq-network/bisq/pull/4315 is merged.
Running 1 instance. Nothing to report.
Temporarily running 2 instances Switchover happened successfully
/cc bisq-network/compensation#638
Temporarily running 2 instances Switchover happened successfully
/cc bisq-network/compensation#644
Temporarily running 2 instances. My old node is being retired and replaced with a new node that is running the new Bisq Price Indices and accessible at both my old V2 address as well as new V3 address.
Temporarily running 2 instances. Migrated to v3 onion addresses, decentralized price feeds and had a good time.
Running 1 instance that is running the new Bisq Price Indices and accessible at both my old V2 address as well as new V3 address. I granted @freimair access to my pricenode to debug networksize metric issues with the pricenodes.
Running 1 instance
/cc bisq-network/compensation#677
Running 1 instance
/cc bisq-network/compensation#681
Running one instance. We had some regular updates, but no issues.
Running 1 instance Nothing to report
/cc bisq-network/compensation#691
Running 1 instance
/cc bisq-network/compensation#697
Running one instance. Nothing to report.
Running 1 instance. This cycle I updated my pricenode to remove HitBTC as a pricenode data provider. See https://github.com/bisq-network/bisq/pull/4756.
Running 1 instance
/cc bisq-network/compensation#719
Running 1 instance
/cc bisq-network/compensation#742
Running 1 instance. I have noticed my pricenode generating alerts occassionally in the keybase #ops-alerts channel, I find that rebooting the server usually resolves the issue, but not always. Sometimes it may require the monitoring server to be restarted. I suspect it is a Tor networking issue.
Running one instance. Nothing to report.
/cc https://github.com/bisq-network/compensation/issues/754#issue-777476665
Running 1 instance
/cc bisq-network/compensation#765
Running one instance. Nothing to report.
Running 1 instance. I recently upgraded to master to include a hotfix which relays the minimum mempool fee.
Running 1 instance
/cc bisq-network/compensation#799
Running one instance. Updated pricenode once this cycle.
Running 1 instance
/cc bisq-network/compensation#821
Running 1 instance. Nothing to report.
Running 1 instance
/cc bisq-network/compensation#839
Running 1 instance. Increased mempool fee suggestion from medium to high priority as per https://github.com/bisq-network/bisq/pull/5426, but later reverted as per https://github.com/bisq-network/bisq/pull/5441.
Running 1 instance. Updated the node.
Running 1 instance. Updated to v1.6.5 to enable users to make 2 sat withdrawals instead of 10 when the mempool is empty.
Running 1 instance
/cc bisq-network/compensation#863
Running 1 instance. We updated nodes this cycle.
Running 1 instance. Nothing to report.
Running 1 instance
/cc bisq-network/compensation#875
Docs: https://bisq.wiki/Pricenode_Operator Team: @bisq-network/pricenode-operators