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

Add wiz's 2nd Bitcoin node #3119

Merged
merged 1 commit into from
Aug 21, 2019
Merged

Add wiz's 2nd Bitcoin node #3119

merged 1 commit into from
Aug 21, 2019

Conversation

wiz
Copy link
Contributor

@wiz wiz commented Aug 21, 2019

No description provided.

@wiz wiz requested a review from ripcurlx as a code owner August 21, 2019 09:26
@ripcurlx
Copy link
Contributor

ripcurlx commented Aug 21, 2019

@wiz Should this new node be publicly available already? I had issues connecting to it. Your other node works without any problems for me.

Copy link
Contributor

@ripcurlx ripcurlx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK - I did have issues in the beginning using bitnodes.earn.com for testing connections. Testing it with the Bisq client seems to be fine.

@ripcurlx ripcurlx merged commit 8634181 into bisq-network:master Aug 21, 2019
@wiz
Copy link
Contributor Author

wiz commented Aug 21, 2019

That site actually shows your node as "unreachable" as well, so I think it's an issue on their end. The node is ready for production use and is reachable on both clearnet and onion. Thanks for testing and merging.

@wiz wiz deleted the wiz/btcnode2 branch August 21, 2019 10:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants