From: "David A. Harding" <dave@dtrt•org>
To: n1ms0s <n1ms0s@protonmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Finding peers that relay taproot spends, was Re: bitcoinj fork with Taproot support
Date: Sun, 21 Nov 2021 06:31:31 +0000 [thread overview]
Message-ID: <0100017d413154f5-866f57e9-5545-4f92-83d9-d2d28649713a-000000@email.amazonses.com> (raw)
In-Reply-To: <cgu5Br8FsrOR7Ly3W5YBg__byG9CdtuhCDnZ8fwN7wBha3G9-kGrooK5gyN-SESmgCHweZzXfpt843Y1yka_yx-ANmYEmF64Xg1o1OJjcG4=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-11-21 6:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 18:07 [bitcoin-dev] " Andrew Chow
2021-11-17 19:00 ` Pieter Wuille
2021-11-17 20:05 ` n1ms0s
2021-11-21 6:31 ` David A. Harding [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=0100017d413154f5-866f57e9-5545-4f92-83d9-d2d28649713a-000000@email.amazonses.com \
--to=dave@dtrt$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=n1ms0s@protonmail$(echo .)com \
/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