Add Tor onion service guidance to full node page#4717
Open
KingParmenides wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a focused Tor onion service section to the Running A Full Node guide for bounty #1712.
The guidance is intentionally P2P-only:
torrcsetup for Bitcoin's P2P port83338332must not be published as a Tor onion servicegetnetworkinfoandaddnode ... onetryBounty
Addresses #1712.
BTC bounty payment address:
39Q34P8A7g375yqEr8buvNJkUbRgKfbKQZTesting
git diff --check -- en/full-node.mdFull local Jekyll build was not run because this workspace has Ruby 2.6.10 while the repository pins Ruby 2.5.8 in the Gemfile.