From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp4.osuosl.org (smtp4.osuosl.org [IPv6:2605:bc80:3010::137]) by lists.linuxfoundation.org (Postfix) with ESMTP id 06167C0070 for ; Fri, 23 Dec 2022 09:46:30 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp4.osuosl.org (Postfix) with ESMTP id A704D4171C for ; Fri, 23 Dec 2022 09:46:29 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org A704D4171C Authentication-Results: smtp4.osuosl.org; dkim=pass (2048-bit key, unprotected) header.d=messagingengine.com header.i=@messagingengine.com header.a=rsa-sha256 header.s=fm2 header.b=UxHiJTJ0 X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -1.602 X-Spam-Level: X-Spam-Status: No, score=-1.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, BITCOIN_OBFU_SUBJ=1, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no Received: from smtp4.osuosl.org ([127.0.0.1]) by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UqeVbsoOvwA5 for ; Fri, 23 Dec 2022 09:46:28 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org DB3BA416F7 Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) by smtp4.osuosl.org (Postfix) with ESMTPS id DB3BA416F7 for ; Fri, 23 Dec 2022 09:46:27 +0000 (UTC) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id DEEFD3200902; Fri, 23 Dec 2022 04:46:24 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Fri, 23 Dec 2022 04:46:25 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:date:feedback-id:feedback-id:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; t=1671788784; x=1671875184; bh=L aoaUP1NQHymiA7e/k6xAPXXN1Yxub7RnLNViak5Glg=; b=UxHiJTJ0H0JS7o5Bk E2WOQnDEhHSGEX/D0oyo8pRypFGRjVt+O776ZUOrjEZww1yXNW8Z/ey6U+Lkta3S MjIG18JGUXR9AWELZCHMEySCDS8RlN/ha9Ipv/bhkTNka8tRK91CG0HxX+rhg+RW nF7weJSjCEhw+tEP+uhCLQAFaMlrddRCAd3D+F5y3L/PJNS4G9K80j6fLV+f3YjN OrcELdsnQ4twgIW7pPu7kFI+icOTV67yeh0uxlFmODStRoG89KgTUh3Rn6LIkHiU HA4332ius6SNPc/2MduiT6LrI8hCqUvDB4EQMVRu7XcE2UD9KfmsGcxv0chdRjW8 yrQJg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrhedvgddtiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvufgfjghfkfggtgfgsehtqhhmtddtreejnecuhfhrohhmpefrvghtvghr ucfvohguugcuoehpvghtvgesphgvthgvrhhtohguugdrohhrgheqnecuggftrfgrthhtvg hrnhephfetueelffdvudejjeetjeejgfejfeelieeijeduieeivdeugefffeeugeelgfeu necuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepphgvth gvsehpvghtvghrthhouggurdhorhhg X-ME-Proxy: Feedback-ID: i525146e8:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 23 Dec 2022 04:46:22 -0500 (EST) Date: Fri, 23 Dec 2022 03:46:19 -0600 From: Peter Todd To: vd@freebsd.org, Vasil Dimov , Bitcoin Protocol Discussion User-Agent: K-9 Mail for Android In-Reply-To: References: Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [bitcoin-dev] onion addresses to try [At least 17% of Bitcoin Core 24.x listening nodes are running full-rbf] X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Dec 2022 09:46:30 -0000 On December 23, 2022 1:39:13 AM CST, Vasil Dimov wrote: >On Thu, Dec 22, 2022 at 22:06:03 -0500, Peter Todd via bitcoin-dev wrote: >[=2E=2E=2E] >> a lack of a convenient source of onion addresses to try >[=2E=2E=2E] > >$ bitcoin-cli getnodeaddresses 0 |jq -r 'map(select(=2Enetwork =3D=3D "on= ion")) | =2E[]=2Eaddress' It's not that simple=2E Because onion addresses cost close to nothing noth= ing to obtain it's dubious to just try some on a one time basis without che= cking to see if they actually have a longer term track record of actually e= xisting=2E You could end up trying addresses of a one time Sybil attack=2E 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 rea= l nodes=2E But my DNS seed doesn't happen to be setup to track nodes using = Tor right now=2E