Open cbeams opened 6 years ago
As of 20190815 @ 0615Z, I have taken over the jhgcy2won7xnslrb.onion seed node from @devinbileck (bisq-network/bisq#3093).
Running 2 seed nodes on mainnet.
Running 1 seed node on testnet.
No issues encountered.
Expenses incurred for the month (USD):
Total: $130
Running 3 seednode instances hosting: Hetzner VM on my dedicated server and two dedicated servers
/cc bisq-network/compensation#355
Running 1 seednode instance
Both seednodes running stable. Updated one of the seednodes with the new docker collectd process, still testing. Will migrate the other seednode once everything works.
bisq-network/compensation#362
Running 3 seednode instances hosting: Hetzner VM on my dedicated server and two dedicated servers
/cc bisq-network/compensation#373
Running 2 seed nodes on mainnet.
Running 1 seed node on testnet.
On Sept 18, fl3mmribyxgrv63c restarted and began syncing from the genesis transaction.
On Sept 18, I updated all my mainnet seed nodes to the seednode_temporaryfix branch, commit d429e12bf914b3a3861f02884451b341d35f7cd7, which contained V1.1.6 updates for seednodes.
Expenses incurred for the month (USD):
Total: $130
Running 1 seednode Planning to takeover 1 seednode from @emzy soon, so 4 operators will each have 2 seednodes.
Running 3 seednode instances hosting: Hetzner VM on my dedicated server and two dedicated servers
/cc bisq-network/compensation#397
Running 1 instance now, but I just setup a powerful new baremetal server with fast SSDs running FreeBSD to takeover 1 of the seednodes from @emzy in a few days. Bisq on FreeBSD is great.
Running 2 seed nodes on mainnet.
Running 1 seed node on testnet.
No issues encountered.
Updated to latest seednode versions as necessary.
Expenses incurred for the month (USD):
Total: $130
Both seednodes running stable. Various updates performed as needed for the new bisq versions. Updated explanations for backup operator.
bisq-network/compensation#407
As of 20191206 @ 1915Z, I have taken over the ef5qnzx6znifo3df.onion seed node from @emzy https://github.com/bisq-network/bisq/pull/3760
Running 3 seednode instances until 2019-12-06 Running 2 seednode instances after 2019-12-06 hosting: Hetzner VM on my dedicated server and two dedicated servers
/cc bisq-network/compensation#432
Running 2 seed nodes on mainnet.
Running 1 seed node on testnet.
None.
Updated to latest versions as necessary.
Total: 280 USD
Running jhgcy2won7xnslrb and ef5qnzx6znifo3df seednodes.
Running 2 seednode instances hosting: Hetzner VM on my dedicated server and one on a dedicated server
/cc bisq-network/compensation#467
Both seednodes running stable. Various updates performed as needed for the new bisq versions. Added monitoring to my docker builds
bisq-network/compensation#468
Running 2 seed nodes on mainnet.
Running 1 seed node on testnet.
None.
Updated to latest versions as necessary.
Total: 280 USD
Running jhgcy2won7xnslrb and ef5qnzx6znifo3df seednodes:
Running 2 seednode instances hosting: Hetzner VM on my dedicated server and one on a dedicated server
/cc bisq-network/compensation#484
Running 2 instances. Nothing to report this cycle.
Running 2 seednode instances hosting: Hetzner VM on my dedicated server and one on a dedicated server
/cc bisq-network/compensation#508
Both seednodes running stable. Nothing to report.
bisq-network/compensation#511
Running 2 instances. Nothing to report this cycle.
Running 2 instances v1.2.8
/cc bisq-network/compensation#515
Running 2 instances. I deployed brand new instances using the new one-click install script. The instances have beefier specs than the old ones.
Running 2 seednode instances hosting: Hetzner VM on my dedicated server and one on a dedicated server
/cc bisq-network/compensation#541
Both seednodes running stable. Nothing to report.
bisq-network/compensation#543
Running 2 instances. Updated nodes to resolve the DAO majority hash issue https://github.com/bisq-network/bisq/pull/4206.
Both seednodes running stable. Updated for https://github.com/bisq-network/bisq/pull/4206
bisq-network/compensation#562
Running 2 seednode instances
/cc bisq-network/compensation#570
jhgcy2won7xnslrb
seednodeRunning 2 instances. I have recently deployed a third instance on Tor V3 (https://github.com/bisq-network/bisq/pull/4320).
Running 2 seednode instances
I have recently deployed a third instance on Tor V3
/cc bisq-network/compensation#595
Both seednodes running stable. Some false positives with the monitoring, when logging in everything seemed ok and resolved itself afterwards.
bisq-network/compensation#601
Running 4 instances, due to adding 2 new Tor V3 seednodes, wizseed3 and wizseed7 Retired old Tor V2 seednode ef5, but continuing to run for a few months until phase-out period Imported some signed witness data from @sqrrm for Canada users who got unsigned
Both seednodes running stable.
bisq-network/compensation#615
Running 3 seednode instances
/cc bisq-network/compensation#617
Both seednodes running stable.
bisq-network/compensation#638
Running 3 seednode instances
/cc bisq-network/compensation#644
Running 5 instances, 2xV2 and 3xV3. This cycle I added 2 new V3 nodes to replace my V2 nodes which are now pending retirement - see https://github.com/bisq-network/bisq/pull/4408
/cc bisq-network/compensation#650
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.
Running 3 seednode instances
/cc bisq-network/compensation#677
Both seednodes running stable.
bisq-network/compensation#681
There are 2 v2 seednodes: running stable There is 1 v3 seednode: running stable There are 2 new v3 seednodes which will be billed in the next cycle. One of them is not working correctly atm.
bisq-network/compensation#691
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