From: Peter Todd <pete@petertodd•org>
To: vd@freebsd•org, Vasil Dimov <vd@freebsd•org>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] onion addresses to try [At least 17% of Bitcoin Core 24.x listening nodes are running full-rbf]
Date: Fri, 23 Dec 2022 03:46:19 -0600 [thread overview]
Message-ID: <F0B752D1-223E-42C5-ABE0-8D055D8E5BF7@petertodd.org> (raw)
In-Reply-To: <Y6VbIeCp2F+jF/70@smle>
On December 23, 2022 1:39:13 AM CST, Vasil Dimov <vd@freebsd•org> wrote:
>On Thu, Dec 22, 2022 at 22:06:03 -0500, Peter Todd via bitcoin-dev wrote:
>[...]
>> a lack of a convenient source of onion addresses to try
>[...]
>
>$ bitcoin-cli getnodeaddresses 0 |jq -r 'map(select(.network == "onion")) | .[].address'
It's not that simple. Because onion addresses cost close to nothing nothing to obtain it's dubious to just try some on a one time basis without checking to see if they actually have a longer term track record of actually existing. You could end up trying addresses of a one time Sybil attack.
The advantage of using the DNS seed records is those addresses are tested over long time frames, so you have a better chance of them representing real nodes. But my DNS seed doesn't happen to be setup to track nodes using Tor right now.
prev parent reply other threads:[~2022-12-23 9:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 3:06 [bitcoin-dev] At least 17% of Bitcoin Core 24.x listening nodes are running full-rbf Peter Todd
2022-12-23 7:39 ` [bitcoin-dev] onion addresses to try [At least 17% of Bitcoin Core 24.x listening nodes are running full-rbf] Vasil Dimov
2022-12-23 9:46 ` Peter Todd [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F0B752D1-223E-42C5-ABE0-8D055D8E5BF7@petertodd.org \
--to=pete@petertodd$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=vd@freebsd$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox