<oembed><type>rich</type><version>1.0</version><author_name>npub1ykn7v3e2fxvmzpjvyd6fd8u5aavhxvc0s65nn87d0ck6alwfq0gswlzh0y</author_name><author_url>https://nostr.ae/npub1ykn7v3e2fxvmzpjvyd6fd8u5aavhxvc0s65nn87d0ck6alwfq0gswlzh0y</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2021-11-17&#xA;📝 Original message:Hello all,&#xA;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.&#xA;See here: https://github.com/n1ms0s/bitcoinj&#xA;&#xA;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.&#xA;&#xA;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 &#34;Witness version reserved for soft-fork upgrades&#34;. Anyone have any idea why this happens? I have a stackexchange question open here for it:&#xA;https://bitcoin.stackexchange.com/questions/110787/issue-when-broadcasting-taproot-transaction-to-older-nodes&#xA;&#xA;n1ms0s&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20211117/8e78d0c2/attachment.html&gt;</html></oembed>