Open cbeams opened 7 years ago
Temporary running 5 seednode instances There are 2 tor onion v2 seednodes (they will retire in a few months) There are 3 tor onion v3 seednodes
/cc bisq-network/compensation#697
Running 5 instances, 2xV2 and 3xV3. My V2 nodes are pending retirement in November after 3 month retirement period as per https://github.com/bisq-network/ops/issues/4. Reduced max connections on all my seeds to 20.
Running 3 instances. My V2 nodes were retired at the beginning of this cycle, so I am now only running V3 nodes. Updates to my nodes were made several times this cycle with fixes from @chimp1984.
Temporary running 5 seednode instances There are 2 tor onion v2 seednodes (they will retire in a few months) There are 3 tor onion v3 seednodes
/cc bisq-network/compensation#719
Temporary running 5 seednode instances There are 2 tor onion v2 seednodes (they will retire in a few months) There are 3 tor onion v3 seednodes
/cc bisq-network/compensation#742
Running 3 instances. @chimp1984 has been maintaining my nodes applying updates as necessary with fixes/improvements.
Temporary running 4 seednode instances There are 1 tor onion v2 seednode (as a backup because of V3 onion issues) There are 3 tor onion v3 seednodes
/cc bisq-network/compensation#765
Running 4 instances. I re-deployed a previously decommissioned V2 seed node as a result of the recent network attack/issues affecting V3 nodes.
Running 4 instances; 3 Tor v3; 1 Tor v2. Performed updates as required.
running 4 seednode instances Running 1 tor onion v2 seednode Running 3 tor onion v3 seednodes
/cc bisq-network/compensation#799
Running 4 instances; 3 Tor v3; 1 Tor v2. Performed updates as required.
running 4 seednode instances Running 1 tor onion v2 seednode Running 3 tor onion v3 seednodes
/cc bisq-network/compensation#821
running 4 seednode instances Running 1 tor onion v2 seednode Running 3 tor onion v3 seednodes
/cc bisq-network/compensation#839
Running 4 instances; 3 Tor v3; 1 Tor v2. Performed updates as required.
Running 4 instances; 3 Tor v3; 1 Tor v2. Performed updates as required.
running 4 seednode instances Running 1 tor onion v2 seednode Running 3 tor onion v3 seednodes
/cc bisq-network/compensation#863
running 4 seednode instances Running 1 tor onion v2 seednode Running 3 tor onion v3 seednodes
/cc bisq-network/compensation#875
Running 4 instances; 3 Tor v3; 1 Tor v2. Performed updates as required.
running 4 seednode instances Running 1 tor onion v2 seednode Running 3 tor onion v3 seednodes
/cc bisq-network/compensation#893
Running 4 instances; 3 Tor v3; 1 Tor v2. Performed updates as required.
Running 4 instances; 3 Tor v3; 1 Tor v2. Nothing to report.
running 4 seednode instances Running 1 tor onion v2 seednode Running 3 tor onion v3 seednodes
/cc bisq-network/compensation#917
running 4 seednode instances Running 1 tor onion v2 seednode Running 3 tor onion v3 seednodes
/cc bisq-network/compensation#928
Running 4 instances; 3 Tor v3; 1 Tor v2. Nothing to report.
running 4 seednode instances Running 1 tor onion v2 seednode Running 3 tor onion v3 seednodes
/cc bisq-network/compensation#940
Cycle 40 report
running 4 seednode instances Running 1 tor onion v2 seednode Running 3 tor onion v3 seednodes
- nothing to report
You are little bit ahead of time with Cycle 40 :wink:
Cycle 40 report
running 4 seednode instances Running 1 tor onion v2 seednode Running 3 tor onion v3 seednodes
- nothing to report
You are little bit ahead of time with Cycle 40 😉
Fixed the typo from 40 to 30.
Running 4 instances; 3 Tor v3; 1 Tor v2. Updated all instances to latest master to support BSQ swaps.
Cycle 19-25 report
Running 5 instances; 3 Tor v3; 2 Tor v2
For the future I think it would be great to do the report on a cycle by cycle basis, as otherwise some incident reports are lost on the way I guess.
Running 4 instances; 3 Tor v3; 1 Tor v2. Updated all nodes to v1.8.0.
Running 4 instances; 3 Tor v3; 1 Tor v2. Updated all nodes to v1.8.0.
/cc bisq-network/compensation#960
Running 5 instances; 3 Tor v3; 2 Tor v2 which were retired in October
Running 3 instances. This cycle I shut down my Tor v2 seednode, so now only have 3 Tor v3 seednodes running. Occasionally encountering Tor reliability issues as my seednodes are sometimes unreachable by our network monitor. Sometimes the issue resolves itself, other times I have to reset the service or clear Tor caches - and even then, sometimes it does not resolve the issue but resolves itself after a period of time. I have confirmed I am able to connect to my seednodes with a Bisq app even though the network monitor is unable to connect.
Running 3 Tor v3 seednodes
/cc bisq-network/compensation#985
Running 3 Tor v3 seednodes
/cc bisq-network/compensation#1005
This role is responsible for operating one or more Bisq seednodes.
Docs: none, other than the above Team: @bisq-network/seednode-operators
Hello. I bought a bitcoin from a exchange and the exchang sent me the bitcoins on a payment gateway. How do I transfer them to my wallet? He does not answer me. I do not know why he sent me on the payment gateway. He did not send it to my wallet. Now I'm not at all confused. I have to work with a programming team. They do not know either. The exchange said you should use Bitcoin Mixer. please help
Running 3 Tor v3 seednodes
/cc bisq-network/compensation#1031
Cycle 31 report
Running 3 Tor v3 seednodes
- nothing to report
I guess this is a type that should be Cycle 34 😄
Running 3 Tor v3 seednodes
/cc bisq-network/compensation#1051
Running 3 instances. Nothing to report.
/cc bisq-network/compensation#1075
Running 3 instances.
/cc bisq-network/compensation#1099
Running 3 instances.
This role is responsible for operating one or more Bisq seednodes.
See: btc_mainnet.seednodes
Docs: none, other than the above Team: @bisq-network/seednode-operators