From: n1ms0s <n1ms0s@protonmail•com>
To: Pieter Wuille <bitcoin-dev@wuille•net>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] bitcoinj fork with Taproot support
Date: Wed, 17 Nov 2021 20:05:55 +0000 [thread overview]
Message-ID: <cgu5Br8FsrOR7Ly3W5YBg__byG9CdtuhCDnZ8fwN7wBha3G9-kGrooK5gyN-SESmgCHweZzXfpt843Y1yka_yx-ANmYEmF64Xg1o1OJjcG4=@protonmail.com> (raw)
In-Reply-To: <pkT64UkQSpTNVJGb12FQK5RTkD8SDOuyWiGOfIQmdX77_eCqBvCzfOerRCPElADFZqqcwfUZhUaRM_SXRKgvO7fXHftDBCybkreTBLahbFc=@wuille.net>
[-- Attachment #1: Type: text/plain, Size: 871 bytes --]
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.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Wednesday, November 17, 2021 7:00 PM, Pieter Wuille via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
> On Wednesday, November 17th, 2021 at 1:07 PM, Andrew Chow via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
>
>> Prior to 0.19.0, creating outputs with an unknown witness version was considered non-standard. This was a violation of BIP 173 and was fixed for 0.19.0+ in PR #15846.
>
> That's correct, but I think OP's problem is with getting P2TR _spends_ to relay. Those will be rejected by all post-segwit pre-taproot Bitcoin Core releases, as far as I know.
>
> --
> Pieter
[-- Attachment #2: Type: text/html, Size: 1219 bytes --]
next prev parent reply other threads:[~2021-11-17 20:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 18:07 Andrew Chow
2021-11-17 19:00 ` Pieter Wuille
2021-11-17 20:05 ` n1ms0s [this message]
2021-11-21 6:31 ` [bitcoin-dev] Finding peers that relay taproot spends, was " David A. Harding
-- strict thread matches above, loose matches on Subject: below --
2021-11-17 3:17 [bitcoin-dev] " n1ms0s
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='cgu5Br8FsrOR7Ly3W5YBg__byG9CdtuhCDnZ8fwN7wBha3G9-kGrooK5gyN-SESmgCHweZzXfpt843Y1yka_yx-ANmYEmF64Xg1o1OJjcG4=@protonmail.com' \
--to=n1ms0s@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=bitcoin-dev@wuille$(echo .)net \
/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