Open wiz opened 4 years ago
Running the mempool.emzy.de server.
/cc bisq-network/compensation#595
The mempool node backends are off to a very good start, being monitored every 5 minutes in #ops-alerts channel on Keybase, and users seem very happy compared to before. No news is good news.
We might want to add 1 or 2 mode mempool nodes to increase decentralization, but for now it seems not needed.
Thanks everyone for getting the new mempool fee estimation working!
Running the mempool.emzy.de server.
/cc bisq-network/compensation#617
Assigned to @wiz, @Emzy and @devinbileck per @wiz's request.
I've renamed the @bisq-network/bisq-explorer-operators team to @bisq-network/mempool-operators and updated the member list to reflect the assignees here.
Running the mempool.emzy.de server.
This also replaces the old BSQ Explorer.
/cc bisq-network/compensation#677
Running the mempool.emzy.de server.
/cc bisq-network/compensation#697
Running mempool.bisq.services. Perform some maintenance and updated to latest code base.
Running mempool.bisq.services. Performed some maintenance and updated to latest code base.
Running the mempool.emzy.de server.
/cc bisq-network/compensation#719
Running the mempool.emzy.de server.
/cc bisq-network/compensation#742
Running mempool.bisq.services. Updated to latest code base to include support for localization and various locales. I notice that my explorer seems to frequently lag behind others with the most recent TX block height, as noticed in the keybase #ops-status channel. I find that rebooting the server resolves the issue.
Running the mempool.emzy.de server.
/cc bisq-network/compensation#765
Running mempool.bisq.services. I have been frequently updating to latest code base. I notice that my explorer still seems to frequently lag behind others with the most recent TX block height, as noticed in the keybase #ops-status channel. I find that rebooting the server resolves the issue.
Running mempool.bisq.services. I have been frequently updating to latest mempool and Bisq code bases. I notice that my explorer still seems to frequently lag behind others with the most recent TX block height, as noticed in the keybase #ops-status channel. I find that rebooting the server resolves the issue.
Running the mempool.emzy.de server.
/cc bisq-network/compensation#799
Running mempool.bisq.services. I have been frequently updating to latest mempool and Bisq code bases. I notice that my explorer still seems to frequently lag behind others with the most recent Bisq DAO TX block height, as noticed in the keybase #ops-status channel, though the Bitcoin TX block height keeps up just fine. I find that restarting the Bisq service resolves the issue. I believe it is a result of running out of memory. I have played with Java memory settings without luck and am starting to suspect I may need to increase the RAM higher than 16GB. I plan to transition to beefier hardware to hopefully resolve the issue.
Running the mempool.emzy.de server.
/cc bisq-network/compensation#821
Running the mempool.emzy.de server.
/cc bisq-network/compensation#839
Running mempool.bisq.services.
I have been frequently updating to latest mempool and Bisq code bases to keep up to date with latest updates.
I recently switched to a memory optimized instance, which should provide better performance in the hopes of eliminating the issue mentioned previously regarding my node lagging behind others with the most recent Bisq DAO TX block height.
However, in the process of migrating the server to a new instance, my secret key for the onion address seems to have become corrupted. Therefore, I needed to generate a new onion address. Reference: https://github.com/bisq-network/bisq/pull/5453
Running mempool.bisq.services. I have been frequently updating to latest mempool and Bisq code bases to keep up to date with latest updates.
Running the mempool.emzy.de server.
/cc bisq-network/compensation#863
Running the mempool.emzy.de server.
/cc bisq-network/compensation#875
Running mempool.bisq.services. I have been frequently updating to latest mempool and Bisq code bases to keep up to date with latest updates.
Running the mempool.emzy.de server.
/cc bisq-network/compensation#893
Running mempool.bisq.services. I have been frequently updating to latest mempool and Bisq code bases to keep up to date with latest updates.
Running mempool.bisq.services. I have been frequently updating to latest mempool and Bisq code bases to keep up to date with latest updates.
Running the mempool.emzy.de server.
/cc bisq-network/compensation#917
Running the mempool.emzy.de server.
/cc bisq-network/compensation#928
Running mempool.bisq.services. I have been frequently updating to latest mempool and Bisq code bases to keep up to date with latest updates.
Running the mempool.emzy.de server.
/cc bisq-network/compensation#960
Running mempool.bisq.services. I am in the process of updating to the latest version with taproot support.
@Emzy, no big deal, but it looks like you edited https://github.com/bisq-network/roles/issues/107#issuecomment-969050264 (your Cycle 30 report) to make it your Cycle 31 report instead of copying its contents to a new comment and editing.
Running mempool.bisq.services. Updated to latest release 2.3.0.
Running the mempool.emzy.de server.
/cc bisq-network/compensation#985
Running the mempool.emzy.de server.
/cc bisq-network/compensation#1005
Running mempool.bisq.services. Nothing to report.
Running the mempool.emzy.de server.
/cc bisq-network/compensation#1031
Running mempool.bisq.services. Nothing to report.
Running the mempool.emzy.de server.
/cc bisq-network/compensation#1051
Running mempool.bisq.services. As of a day or so ago, my instance is no longer processing Bisq transactions. It seems I have the same issue as described in this issue which was just recently resolved.
Running the mempool.emzy.de server.
/cc bisq-network/compensation#1075
Running mempool.bisq.services. Nothing to report.
Running the mempool.emzy.de server.
Running mempool.bisq.services.
Running mempool.bisq.services. Nothing to report.
Running the mempool.emzy.de server.
/cc bisq-network/compensation#1120
Docs: https://bisq.wiki/Mempool_Explorer_Operator