Skip to content
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

Seednode Operator #15

Open
cbeams opened this issue Sep 4, 2017 · 108 comments
Open

Seednode Operator #15

cbeams opened this issue Sep 4, 2017 · 108 comments
Assignees
Labels

Comments

@cbeams
Copy link
Member

@cbeams cbeams commented Sep 4, 2017

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

@cbeams cbeams added the role:op label Sep 4, 2017
@cbeams cbeams changed the title seednode operator Seednode Operator Jan 2, 2018
@cbeams cbeams added role and removed role:op labels Jan 3, 2018
@ManfredKarrer
Copy link
Member

@ManfredKarrer ManfredKarrer commented May 1, 2018

2018.04 report

Running 6 Bitcoin and 2 LTC instances. Digital ocean updates their servers frequently with security patches and that causes restarts which kills the seed node (no crone job for autostart). I am following the old email notifications and got alerted soon to start the seed node in such cases.

@ManfredKarrer
Copy link
Member

@ManfredKarrer ManfredKarrer commented May 30, 2018

2018.05 report

Running 6 Bitcoin and 2 LTC instances.

@Emzy
Copy link

@Emzy Emzy commented May 30, 2018

2018.05 report

Running 1 Bitcoin instance.

bisq-network/compensation#76

@mrosseel
Copy link
Member

@mrosseel mrosseel commented Jun 1, 2018

2018.05 report

Running 1 Bitcoin instance
hosting: Linode in docker container

bisq-network/compensation#80

@mrosseel
Copy link
Member

@mrosseel mrosseel commented Jun 29, 2018

2018.06 report

Running 1 seednode instance
hosting: Linode in docker container

  • fixed a docker bug where the linux had no language setup which crashed the container.
  • Manfred found a restart bug, this was not noticed on my node because the docker container restarts automatically so it seems this is not relevant for my node.

bisq-network/compensation#83

@Emzy
Copy link

@Emzy Emzy commented Jun 30, 2018

2018.06 report

Running 1 Bitcoin instance

  • Update to new Version

bisq-network/compensation#88

@ManfredKarrer
Copy link
Member

@ManfredKarrer ManfredKarrer commented Jun 30, 2018

2018.06 report

Running 6 seednode instance
Updated to new Version
bisq-network/compensation#92

@ManfredKarrer
Copy link
Member

@ManfredKarrer ManfredKarrer commented Jun 30, 2018

@Emzy @mrosseel You mixed that role up with the bitcoin operator role...

@cbeams
Copy link
Member Author

@cbeams cbeams commented Jul 9, 2018

I've updated the description of this role issue and updated the @bisq-network/seednode-operators team to reflect current status.

@ManfredKarrer
Copy link
Member

@ManfredKarrer ManfredKarrer commented Jul 26, 2018

2018.07 report

Running 6 seednode instance.

/cc bisq-network/compensation#93

@wiz
Copy link
Member

@wiz wiz commented Aug 25, 2020

Cycle 16 report

  • Shutdown ef5 seednode after 3 month retirement period as per bisq-network/ops#4
  • Was running 4 instances, now down to running 3 instances

/cc bisq-network/compensation#650

@devinbileck
Copy link
Member

@devinbileck devinbileck commented Sep 22, 2020

Cycle 17 report

Running 5 instances, 2xV2 and 3xV3.
My V2 nodes are pending retirement in November after 3 month retirement period as per bisq-network/ops#4.

/cc bisq-network/compensation#665

@Emzy
Copy link

@Emzy Emzy commented Sep 23, 2020

Cycle 17 report

Running 3 seednode instances

/cc bisq-network/compensation#677

@mrosseel
Copy link
Member

@mrosseel mrosseel commented Sep 26, 2020

Cycle 17 report

Both seednodes running stable.

bisq-network/compensation#681

@mrosseel
Copy link
Member

@mrosseel mrosseel commented Oct 23, 2020

Cycle 18 report

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

@Emzy
Copy link

@Emzy Emzy commented Oct 23, 2020

Cycle 18 report

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

@devinbileck
Copy link
Member

@devinbileck devinbileck commented Oct 23, 2020

Cycle 18 report

Running 5 instances, 2xV2 and 3xV3.
My V2 nodes are pending retirement in November after 3 month retirement period as per bisq-network/ops#4.
Reduced max connections on all my seeds to 20.

/cc bisq-network/compensation#699

@devinbileck
Copy link
Member

@devinbileck devinbileck commented Nov 26, 2020

Cycle 19 report

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.

/cc bisq-network/compensation#718

@Emzy
Copy link

@Emzy Emzy commented Nov 27, 2020

Cycle 19 report

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

  • several updates

/cc bisq-network/compensation#719

@Emzy
Copy link

@Emzy Emzy commented Dec 26, 2020

Cycle 20 report

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

  • several updates

/cc bisq-network/compensation#742

@devinbileck
Copy link
Member

@devinbileck devinbileck commented Dec 28, 2020

Cycle 20 report

Running 3 instances.
@chimp1984 has been maintaining my nodes applying updates as necessary with fixes/improvements.

/cc bisq-network/compensation#748

@Emzy
Copy link

@Emzy Emzy commented Jan 26, 2021

Cycle 21 report

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

  • several updates

/cc bisq-network/compensation#765

@devinbileck
Copy link
Member

@devinbileck devinbileck commented Jan 27, 2021

Cycle 21 report

Running 4 instances.
I re-deployed a previously decommissioned V2 seed node as a result of the recent network attack/issues affecting V3 nodes.

/cc bisq-network/compensation#772

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
9 participants