Open cbeams opened 6 years ago
Running 2 instances.
/cc bisq-network/compensation#252
I have setup and transferred ownership of the 44mgyoe2b6oqiytt.onion pricenode from @ManfredKarrer (https://github.com/bisq-network/bisq/pull/2769).
For several hours after the transition on April 24/25, my pricenode was reporting slightly higher fees compared to other pricenodes. Once the issue was identified, the cause was determined to be due to an incorrect configuration - the maxblocks parameter was set to 0. After changing it to 2, the fees were then consistent with other pricenodes.
Expenses incurred for the month (USD):
Note: Although the transition did not occur until towards the end of the month, my server was running since the beginning of the month in preparation/anticipation of the transition.
Running 1 instance.
/cc bisq-network/compensation#281
Running 1 pricenode.
No issues to report this month.
No maintenance required this month.
Expenses incurred for the month (USD):
Running 1 price node.
There have been reports of failed trades due to price deviation between maker/taker. At this point I don't know the cause of the discrepancy, perhaps price volatility causing price nodes to report different values at any given instant. I would like to continue monitoring the situation and determine the cause.
No issues encountered this month.
No maintenance performed this month.
Expenses incurred for the month (USD):
Running 1 instance. The prices got stuck, giving stale prices to clients. This incident was investigated, the only errors in the logs were failures to connect to bitcoinaverage and the fee service. This indicates it was a local connection error. Had to restart the server to fix it.
/cc bisq-network/compensation#312
Running 1 instance.
/cc bisq-network/compensation#324
Running 1 price node.
No issues encountered this month.
No maintenance performed this month.
Expenses incurred for the month (USD):
Total: $22
Running 1 instance, no issues.
/cc bisq-network/compensation#331
Running 1 instance, no issues.
Per bisq-network/bisq#3181, I've just removed my pricenode URL. I'm unassigning myself from this issue now, as I'll no longer be running a node. It would be good if someone could step up to be the primary owner of this role going forward. This really just means being the person on point if something is going wrong with pricenodes and/or price data. Note that I'm happy to continue being available for pricenode code issues, as I re-wrote it and probably still know it best.
Running 1 price node.
No issues encountered this month.
No maintenance performed this month.
Expenses incurred for the month (USD):
Total: $22
Running 1 instance.
/cc bisq-network/compensation#355
Running 1 instance, no issues.
/cc bisq-network/compensation#362
Running 1 instance.
/cc bisq-network/compensation#373
Running 1 price node.
No issues encountered this month.
No maintenance performed this month.
Expenses incurred for the month (USD):
Total: $22
Running 1 instance. Nothing to report.
Created new pricenode gztmprecgqjq64zh.onion Started monitoring all pricenodes on my alerts system
Running 1 instance.
/cc bisq-network/compensation#397
Running 1 instance and renewed my bitcoinaverage subscription.
Running 1 price node.
No issues encountered.
No maintenance performed.
Expenses incurred for the month (USD):
Total: $22
Running 1 instance, no issues.
/cc bisq-network/compensation#407
Running 1 instance. Nothing to report.
Running 1 instance. Nothing to report.
/cc bisq-network/compensation#432
Running 1 price node.
None.
None.
Total: 72 USD
Running gztmprecgqjq64zh pricenode with no issues to report.
Running 1 instance. Nothing to report.
Running 1 instance. Nothing to report.
/cc bisq-network/compensation#467
Running 1 instance, no issues. Note: my bitcoinaverage subscription is still valid for 300+ days, others are less lucky so willing to help in solving this problem
/cc bisq-network/compensation#468
Running 1 price node.
I had to renew my BitcoinAverage subscription (developer plan) due to changes with their subscription plans, only to discover that the endpoints that we use are not available in that plan anymore. I ended up having to upgrade to the startup plan, which costs 4 times as much. It took several days to identify and resolve the issue, during which time my pricenode was offline.
None.
Total: 120 USD
Running gztmprecgqjq64zh pricenode. After some issues with BitcoinAverage, upgraded to "startup" plan at $60/month.
Running 1 instance. Nothing to report.
Running 1 instance.
/cc bisq-network/compensation#484
Running 1 instance. Nothing to report.
@bisq-network/pricenode-operators, I've just created stub documentation for this role at https://bisq.wiki/Pricenode_Operator. Please make sure you have a watch on that page.
Running 1 instance.
Had to update to master due to a bug. There were some issues with compilation so @wiz instructed me to create a new VM with Ubuntu on it and install from script, rather than doing it manually. This didn't really work for me, gradle compilation was failing inside a script, so I had to rebuild and finish the installation manually. Luckly it all worked out in the end and node migration was complted successfuly.
Running 1 instance.
/cc bisq-network/compensation#508
Nothing to report in Cycle 10. In Cycle 11 the Coinmarketcap API changed so a new version of was needed. All pricenodes ran fine but when restarting they crashed. Since the last pricenode update (at least 6 months) the repo was moved so I had to rewrite my docker file. This took some time, luckily, because the hotfix crashed all the other pricenodes leaving mine the only one standing. The logs showed a lot of incoming requests, but CPU and RAM were below 5% so it was proven a single pricenode could service the Bisq network. Since then I've updated the docker install method, although I know there is a debian install script. I could use that and make my life a lot easier, but I think it's important that not everyone runs debian with the exact same setup.
/cc bisq-network/compensation#511
Running 1 instance. Updated my node as necessary due to the above mentioned CMC API change.
Running 1 instance sans CMC
/cc bisq-network/compensation#515
Running 1 instance.
Installed collectd and setup setver metrics for monitor.bisq.network.
Running 1 instance. I deployed a fresh instance recently using the new one-click installer and also enabled the collectd, networksize and hsversion metrics (see https://monitor.bisq.network/d/qclhStdWz/server-metrics?orgId=1&var-Server=44mgyoe2b6oqiytt).
Running 1 instance.
/cc bisq-network/compensation#541
Running 1 instance.
/cc bisq-network/compensation#543
Running 1 instance:
Running 1 instance. Updated pricenode from master due to an mempool issue.
Docs: https://bisq.wiki/Pricenode_Operator Team: @bisq-network/pricenode-operators