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

Bitcoin Node Operator #67

Open
cbeams opened this issue Jan 9, 2018 · 334 comments
Open

Bitcoin Node Operator #67

cbeams opened this issue Jan 9, 2018 · 334 comments
Assignees
Labels
team:ops https://bisq.wiki/Ops_Team

Comments

@cbeams
Copy link
Member

cbeams commented Jan 9, 2018

See https://github.com/bisq-network/bisq/blob/master/core/src/main/java/bisq/core/btc/nodes/BtcNodes.java

@ManfredKarrer
Copy link
Member

ManfredKarrer commented May 1, 2018

2018.04 report

Running 2 instances both onion and clear net. No issues occurred that month.

@ManfredKarrer
Copy link
Member

2018.05 report

Running 2 instances both onion and clear net. No issues occurred that month.

@Emzy
Copy link

Emzy commented May 30, 2018

2018.05 report

Running of 3 Bitcoin Fullnodes.
3 onion address
3 clearnet address
3 VPS servers and one dedicated server.

Events:

One SSD died (only the Bockchain was missing) and I had to sync the node again.

bisq-network/compensation#76

@sqrrm
Copy link
Member

sqrrm commented May 30, 2018

May 2018 report

Ran two full instances, both onion and clearnet with no issues.

Compensation request at bisq-network/compensation#77

@ripcurlx
Copy link
Contributor

2018.05 report

Running one instance both onion and clear net. No issues occurred that month.

Events

The instance wasn't reachable for a couple of hours as connection timeouts occurred. Instance was up and running and no obvious issue was causing this problem on DigitalOcean. After a restart everything was up and running again.

/cc bisq-network/compensation#71

@mrosseel
Copy link
Member

mrosseel commented Jun 1, 2018

2018.05 report

Running 2 instancens both onion and clear not. No issues this month.

bisq-network/compensation#80

@Emzy
Copy link

Emzy commented Mar 26, 2024

Cycle 57 report

Running 4 instances.

  • nothing to report

/cc bisq-network/compensation#1504

@sqrrm
Copy link
Member

sqrrm commented Mar 26, 2024

Cycle 57 report

Running 2 nodes.

bisq-network/compensation#1505

@devinbileck
Copy link
Member

devinbileck commented Mar 26, 2024

Cycle 57 report

Running 3 instances.
Nothing to report.

/cc bisq-network/compensation#1507

@sqrrm
Copy link
Member

sqrrm commented Apr 24, 2024

Cycle 58 report

Running 2 nodes.

bisq-network/compensation#1531

@Emzy
Copy link

Emzy commented Apr 28, 2024

Cycle 58 report

Running 4 instances.

  • nothing to report

/cc bisq-network/compensation#1537

@sqrrm
Copy link
Member

sqrrm commented Jun 1, 2024

Cycle 59 report

Running 2 nodes.

bisq-network/compensation#1562

@suddenwhipvapor
Copy link

Cycle 60

Ran first node for most of cycle 60, added a second one towards the end of the cycle, this CR will be for one node.

@jester4042
Copy link

Cycle 60


Running 3 bitcoin core nodes. 2 at 27.0.1 and 1 at 27.0.0. Started mid-cycle. No issues to report.

@runbtc
Copy link

runbtc commented Jul 3, 2024

Cycle 60 report

Running 1 instance.
Nothing to report.

/cc bisq-network/compensation#1575

@sqrrm
Copy link
Member

sqrrm commented Jul 6, 2024

I was unable to keep my bitcoin nodes stable. Since they're no longer used I will retire as Node Operator. I will keep the nodes running for a while longer before taking them down.

@cbeams
Copy link
Member Author

cbeams commented Jul 13, 2024

As roles maintainer, I've updated this role's assignee list to reflect the current state of BtcNodes.java

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team:ops https://bisq.wiki/Ops_Team
Projects
None yet
Development

No branches or pull requests