From: Andrew Chow <achow101-lists@achow101.com>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] bitcoinj fork with Taproot support
Date: Wed, 17 Nov 2021 18:07:07 +0000 [thread overview]
Message-ID: <ff9aecf5-70ad-f532-49f3-513b5a6beee9@achow101.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1042 bytes --]
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.
On 11/16/2021 10:17 PM, n1ms0s via bitcoin-dev wrote:
> Hello all,
> I am currently working on a fork of bitcoinj with basic Taproot support. Currently it supports basic sending and receiving with Taproot addresses using a bitcoinj SPV wallet.
> See here: https://github.com/n1ms0s/bitcoinj
>
> It supports the above along with public/private key tweaking. Feel free to take a look, and leave feedback or even work on it yourself and submit a pull request.
>
> One issue I am running into right now though is when broadcasting a Taproot transaction to older nodes (old as in ~0.18.0) I get an error response of "Witness version reserved for soft-fork upgrades". Anyone have any idea why this happens? I have a stackexchange question open here for it:
> https://bitcoin.stackexchange.com/questions/110787/issue-when-broadcasting-taproot-transaction-to-older-nodes
>
> n1ms0s
[-- Attachment #2: Type: text/html, Size: 2360 bytes --]
next reply other threads:[~2021-11-17 18:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 18:07 Andrew Chow [this message]
2021-11-17 19:00 ` [bitcoin-dev] bitcoinj fork with Taproot support Pieter Wuille
2021-11-17 20:05 ` n1ms0s
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=ff9aecf5-70ad-f532-49f3-513b5a6beee9@achow101.com \
--to=achow101-lists@achow101.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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