Return-Path: <0100017d413154f5-866f57e9-5545-4f92-83d9-d2d28649713a-000000@amazonses.com> Received: from smtp3.osuosl.org (smtp3.osuosl.org [IPv6:2605:bc80:3010::136]) by lists.linuxfoundation.org (Postfix) with ESMTP id AA3CBC0012 for ; Sun, 21 Nov 2021 06:31:34 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp3.osuosl.org (Postfix) with ESMTP id 9B9C7606CF for ; Sun, 21 Nov 2021 06:31:34 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -1.85 X-Spam-Level: X-Spam-Status: No, score=-1.85 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: smtp3.osuosl.org (amavisd-new); dkim=pass (1024-bit key) header.d=dtrt.org header.b="g2HOuZQ7"; dkim=pass (1024-bit key) header.d=amazonses.com header.b="IwWOs2g2" Received: from smtp3.osuosl.org ([127.0.0.1]) by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EN-MdM3LfoYn for ; Sun, 21 Nov 2021 06:31:33 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0 Received: from a8-190.smtp-out.amazonses.com (a8-190.smtp-out.amazonses.com [54.240.8.190]) by smtp3.osuosl.org (Postfix) with ESMTPS id 671776062E for ; Sun, 21 Nov 2021 06:31:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=smjumfhvj4y563qynmbhq4si3vd5r74k; d=dtrt.org; t=1637476292; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version:Content-Type:In-Reply-To; bh=pDBZFWVISQEbHI8/ONqc0rgYhqhv2eq4wOtMC2cNxZk=; b=g2HOuZQ7IiErQow+8/ZU6BMfrH9sEw6YzGBWP/NJqjfzCeDVFDsM6MhvgvsNFD7P Kr10gopZiH2MW4ROmmxMcgUpkpW9DRIAkn6IfAKj8g3Uu5qTYVZ9tIRti8BX2oAIfpI Fh6f5h00aaSkrTyhlpvbkG2MKxmQ1Zek9eLV99lc= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=ug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=amazonses.com; t=1637476292; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version:Content-Type:In-Reply-To:Feedback-ID; bh=pDBZFWVISQEbHI8/ONqc0rgYhqhv2eq4wOtMC2cNxZk=; b=IwWOs2g2wyc8I/oN7thjUBQXu7TjyruaiLarOHG4jZADS4heN2VonvQL/R9SO66s dxThpePwUpk58g/nlcE+ux/PVmXtzAGTW+3NFcI+Exzge/6F7ofe5nkG0H6TWmiYBe1 jovuskkKrPtIIy3E3OfLyaLyDLT1n0C1hG+qamtg= Date: Sun, 21 Nov 2021 06:31:31 +0000 From: "David A. Harding" To: n1ms0s , Bitcoin Protocol Discussion Message-ID: <0100017d413154f5-866f57e9-5545-4f92-83d9-d2d28649713a-000000@email.amazonses.com> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="jnjsqfhmekfjba5o" Content-Disposition: inline In-Reply-To: Feedback-ID: 1.us-east-1.n0oE+7mPCT3oYHRtIkpRsZClsaxS9eYOjymWOETvbbI=:AmazonSES X-SES-Outgoing: 2021.11.21-54.240.8.190 Subject: [bitcoin-dev] Finding peers that relay taproot spends, was Re: bitcoinj fork with Taproot support 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: Sun, 21 Nov 2021 06:31:34 -0000 --jnjsqfhmekfjba5o Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Nov 17, 2021 at 08:05:55PM +0000, n1ms0s via bitcoin-dev wrote: > This seems to be the case. I saw your reply on Bitcoin StackExchange > as well. In bitcoinj I just made it so the client only connects to > nodes with at least protocol version 70016. Seems to work well. Hi, This is a clever solution, but when I looked into this I found that P2P protocol version 70016 was introduced in Bitcoin Core version 0.21.0[1]. This release will not ever relay taproot spends because it doesn't contain taproot activation parameters[2]. So this heuristic is imperfect: it only works when it happens to connect to the 0.21.1 and 22.0 versions of Bitcoin Core (or compatible nodes) which were programmed to begin relaying taproot spends starting one block before activation. Can anyone recommend a better heuristic lite wallets can use to ensure they're connecting to a taproot-activated node? (If not, maybe this is something we want nodes to advertise during activation of future protocol extensions.) Thanks, -Dave [1] https://github.com/bitcoin/bitcoin/commit/ccef10261efc235c8fcc8aad54556615b0cc23be https://bitcoincore.org/en/releases/0.21.0/ [2] https://github.com/bitcoin/bitcoin/pull/20165 --jnjsqfhmekfjba5o Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEgxUkqkMp0LnoXjCr2dtBqWwiadMFAmGZ50MACgkQ2dtBqWwi adNT7A/8CIcZ0duPKWVmXeQzWRmlfa9i0q4LvxlRdEB1kaa2ZrpnwOBcXx87g0Gy yypLVbRaTO8AE9cjcM1+3E1Eqg5fbjip+6QSJ0lDEA2DZ5VMf7jPwcR+nPI37FPE TXbaK5YVvh+kvGCnHXRovKiyl4A2CXbTfetgXSVsGGguhLs2Pst71nd4q64MAB2m e0X0R5rpJNpJQwdQWf0iwX4rlL7wtozzEkPd67vyQnavQ8xYTPL8YhQCmp9inUtM uj2YrwOMvtoemlf15szee1Qqr1uPEbgOBIeRNq6AnOeR15VXDaNQfhNbpOCYCcqo 549Z7XSekvGOr73v89+BiYovaA7Y3p8tq46l06xzGJXKIZmEW3Fhv41Nhkda1tyJ klSP2oJS5RWBG7TWwnxyo82AX7dyylmpGWOOZRcyNl0habaoF895enO7hZsXMkl9 POiafFkiKhlfD+PD/h6pK0ukvdZBjyBK/B2Os541ZQCxnYCCwPtJLZEqh5DaLl0N wCEnD7W01Y73s7YQ7PlemH3TyJNbnStVVpmAsPETtBQjpyRQD1gFWQFuL77/EuMT fcejcW511PU/0anX1yf0bpL8t4Jvwy33+3am7XTJ+jz4xdfoyim1H1oK8MfUaxlc N+x2mkxgH0MpHjHQaXMQv0b1vigG9YGHHkrPLW3EpcBkb+uuheM= =XhM7 -----END PGP SIGNATURE----- --jnjsqfhmekfjba5o--