<unnamed>

Public Key

npub1ykn7v3e2fxvmzpjvyd6fd8u5aavhxvc0s65nn87d0ck6alwfq0gswlzh0y

Profile Code

nprofile1qqsztflxgu4ynxd3qexzxaykn72w7ktnxv8cd2fenlxhutdwlhys85gpz4mhxue69uhhyetvv9ujumn0wd68ytnwv46qz9rhwden5te0wfjkccte9ejxzmt4wvhxjmcpp4mhxue69uhkummn9ekx7mqphz9p7

Publishing to

relay.nostr.net

relay.damus.io

nos.lol

Last Notes

2023-06-08 01:00:36 CEST

- reply

📅 Original date posted:2021-11-17
📝 Original message: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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20211117/8e78d0c2/attachment.html>