-
Notifications
You must be signed in to change notification settings - Fork 16
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
Monero Explorer Operator #109
Comments
Initial Report
https://node77.monero.wiz.biz/
|
Initial Report
https://xmrblocks.monero.emzy.de/
|
Initial Report
https://xmrblocks.bisq.services/
|
Cycle 17 reportRunning xmrblocks.bisq.services. |
Cycle 17 and 18 reportRunning xmrblocks.monero.emzy.de |
Cycle 18 reportRunning xmrblocks.bisq.services. |
Cycle 19 reportRunning xmrblocks.bisq.services. |
Cycle 19 reportRunning xmrblocks.monero.emzy.de
|
Cycle 20 reportRunning xmrblocks.monero.emzy.de
|
Cycle 20 reportRunning xmrblocks.bisq.services. |
Cycle 19 and 20 report
|
Cycle 21 reportRunning xmrblocks.monero.emzy.de
|
Cycle 21 reportRunning xmrblocks.bisq.services. |
Cycle 22 reportRunning xmrblocks.bisq.services. |
Cycle 60 reportRunning xmrexplrthytnunr4jasr3vnjc6jo5idsyxzv74a7ep7dy7lwcv2eoyd.onion |
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 xmrexplrthytnunr4jasr3vnjc6jo5idsyxzv74a7ep7dy7lwcv2eoyd.onion |
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 xmrexplrthytnunr4jasr3vnjc6jo5idsyxzv74a7ep7dy7lwcv2eoyd.onion |
Cycle 63 reportRunning xmrexplrthytnunr4jasr3vnjc6jo5idsyxzv74a7ep7dy7lwcv2eoyd.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 63 reportBeen running nklwsomtuok6dhqqecp3a26xzgokfgmeuaplcdkaxehncg57yzarvbad.onion since a few cycles ago, only realized that I had to merge it last cycle, and forgot to include it in my CR for this cycle... will be added to Cycle 64 CR. |
Cycle 64Running nklwsomtuok6dhqqecp3a26xzgokfgmeuaplcdkaxehncg57yzarvbad.onion |
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 xmrexplrthytnunr4jasr3vnjc6jo5idsyxzv74a7ep7dy7lwcv2eoyd.onion |
Cycle 65Running nklwsomtuok6dhqqecp3a26xzgokfgmeuaplcdkaxehncg57yzarvbad.onion |
Cycle 65 reportMy node is still running, though will be decommissioned soon since it has been removed in the recent 1.9.18 release, as per bisq-network/bisq#7137. Once sufficient time has elapsed, I will decommission the node. |
Cycle 65 reportRunning xmrexplrthytnunr4jasr3vnjc6jo5idsyxzv74a7ep7dy7lwcv2eoyd.onion |
Proposal: bisq-network/proposals#257
Docs: https://bisq.wiki/Monero_Explorer_Operator
Team: @bisq-network/monero-explorer-operators
The text was updated successfully, but these errors were encountered: