https://nostr.ae https://nostr.ae/npub1ykn7v3e2fxvmzpjvyd6fd8u5aavhxvc0s65nn87d0ck6alwfq0gswlzh0y https://nostr.ae/nevent1qqs2w8ypjqtxcvjdxyl87c27vu5jldr2phdsmk4p52qqfjmt7yy33zczyqj60ej89fyenvgxfs3hf95ljnh4juenp7r2jwvle4lzmthaeypazdy6vyr In reply to <a href='/nevent1qqsy8ql20f4j3cd2c8celgklgx49usg44pz27a4uj00vvsxqqgf4xcgy8nt4t'>nevent1q…nt4t</a><br/>_________________________<br/><br/>📅 Original date posted:2021-11-17<br/>📝 Original message:Hello all,<br/>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.<br/>See here: <a href="https://github.com/n1ms0s/bitcoinj">https://github.com/n1ms0s/bitcoinj</a><br/><br/>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.<br/><br/>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:<br/><a href="https://bitcoin.stackexchange.com/questions/110787/issue-when-broadcasting-taproot-transaction-to-older-nodes">https://bitcoin.stackexchange.com/questions/110787/issue-when-broadcasting-taproot-transaction-to-older-nodes</a><br/><br/>n1ms0s<br/>-------------- next part --------------<br/>An HTML attachment was scrubbed...<br/>URL: &lt;<a href="http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20211117/8e78d0c2/attachment.html&gt">http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20211117/8e78d0c2/attachment.html&gt</a>; 2023-06-07T23:00:36Z