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.

Sign up for GitHub

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

Jump to bottom

crawler: Collect Tor v3 and I2P addresses? #92

Open
laanwj opened this issue Apr 1, 2021 · 4 comments · May be fixed by #101
Open

crawler: Collect Tor v3 and I2P addresses? #92

laanwj opened this issue Apr 1, 2021 · 4 comments · May be fixed by #101

Comments

@laanwj
Copy link
Contributor

laanwj commented Apr 1, 2021

Tor v3 and I2P addresses are too large for DNS seeding, and it would be unnecessary in the first place (also because it is not possible/practical to access DNS over these networks).

However, it could still be useful to collect them for other purposes. For example, in the Bitcoin Core release process we use the text output of a DNS seeder as input for generating the hardcoded list of seeds. We are going to need some kind of crawler that supports these addresses.
@laanwj laanwj mentioned this issue Apr 5, 2021
Merged
@laanwj laanwj mentioned this issue May 28, 2021
Merged
@laanwj laanwj mentioned this issue Apr 15, 2022
Open
11 tasks
@siltribera
Copy link

I would implement BIP155 for this seeder if @sipa agrees.

Of course, addresses higher than 16 bytes would not be reported in a DNS response, but would be saved in the seeder's database and printed in the seeder dump file.

I have two options:

  1. implement addrv2 within this code base.
  2. integrate this codebase with bitcoin core master essentially having bitcoin as a git submodule and compile against it. This is to use the upstream addrv2 (de)serialization implementation.

I am open to both options, whichever @sipa agrees with if any.

@sipa
Copy link
Owner

sipa commented Aug 31, 2022

I'd go for option 1.

@jonatack
Copy link

Concept ACK, this could save a lot of time when updating the hardcoded seeds for tor v3, i2p and cjdns. We've been doing that manually for the past few releases that support these BIP155 networks.

@siltribera siltribera linked a pull request Sep 4, 2022 that will close this issue
Open
@siltribera
Copy link

BIP155 implementation is ready.

Please checkout #101.

@jonatack jonatack mentioned this issue Apr 18, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

addrv2 BIP155 support siltribera/bitcoin-seeder
6 participants
@laanwj @sipa @jonatack @siltribera and others