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
Still v2 addresses used in BitcoinJ? #5778
Comments
Getting the same warning when using the BTC node
However:
@wiz any difference in setup between |
Tor v3 support was added in Bitcoin Core v0.21 |
Ah okay, looks like this can be fixed by upgrading that one node. It was a custom build of Bitcoin Core v0.20 before the PR to get Tor v3 supported was merged so it supports both v2 and v3 but if that causes issues I can just remove it. |
Sounds good. Let me know when its upgraded, I can then check if this warning is gone. |
This has nothing to do with Tor v2 addresses. This is a new P2P message based on https://github.com/bitcoin/bips/blob/master/bip-0155.mediawiki that supports Tor v3 addresses. So the naming is a little bit confusing. I looked at the code where this logging takes place and it seems that this is sent from @wiz's node to indicate that it is preferring and understands addrv2 messages. I don't know why it only happens with @wiz node and why it is logged as a warning in that case. |
@wiz Did you change anything already with this node, as I still see this warning?
|
Fixing this is in my task queue, however as it's merely a warning in the log prints I am treating this as a low priority issue and will get to it after Taproot activation. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because of inactivity. Feel free to reopen it if you think it is still relevant. |
I see that error in the logs:
[BlockingClient network thread for wizbit5555bsslwv4ctronnsgk5vh2w2pdx7v7eyuivlyuoteejk7lid.onion:8333] WARN org.bitcoinj.core.Peer: Peer{[wizbit5555bsslwv4ctronnsgk5vh2w2pdx7v7eyuivlyuoteejk7lid.onion]:8333, version=70016, subVer=/Satoshi:0.20.99(@wiz)/, services=1037 (NETWORK, BLOOM, WITNESS, NETWORK_LIMITED), time=2021-10-23 22:28:21, height=706355}: Received unhandled message: org.bitcoinj.core.SendAddrV2Message@2f5d3a99
Looks like there is still usage of v2 addresses?
@ripcurlx any idea?
The text was updated successfully, but these errors were encountered: