-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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 bitcoinj Tor v3 support #5686
Add bitcoinj Tor v3 support #5686
Conversation
…f578f427d78242bc2) Conflicts: build.gradle gradle/witness/gradle-witness.gradle
@jmacxx Could you also give this bitcoinj version a spin? |
tested ACK |
@sqrrm Could you please ACK and merge this PR as well so I can create the release branch for v1.7.4? |
@Emzy Could you please provide a PR with the Tor v3 addresses for the v1.7.4 release? Thanks! |
There are still some v3 onions from nodes missing. I'm on it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK
This is atm only for those who want to help with testing our new bitcoinj fork on Regtest. If you want to test Tor v3 addresses against Mainnet only do it with a fresh data directory and DO NOT try to use it for real transactions as we haven't done intensive testing yet (only automated Regtest testing)
If you need a Bitcoin Core Node Tor v3 address for testing you can use mine (this is one of the federated Bitcoin core ndoes):
catlnkpdm454ecngktyo4z22m5dlcvfvgzz4nt5l36eeczecrafslkqd.onion
e.g. use
--btcNodes=catlnkpdm454ecngktyo4z22m5dlcvfvgzz4nt5l36eeczecrafslkqd.onion
as startup argument.Afterwards you should see following in your Network Info Tab