š
Original date posted:2021-11-21
š Original message:On Wed, Nov 17, 2021 at 08:05:55PM +0000, n1ms0s via bitcoin-dev wrote:
> 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.
Hi,
This is a clever solution, but when I looked into this I found that P2P
protocol version 70016 was introduced in Bitcoin Core version 0.21.0[1].
This release will not ever relay taproot spends because it doesn't
contain taproot activation parameters[2]. So this heuristic is
imperfect: it only works when it happens to connect to the 0.21.1 and
22.0 versions of Bitcoin Core (or compatible nodes) which were
programmed to begin relaying taproot spends starting one block before
activation.
Can anyone recommend a better heuristic lite wallets can use to ensure
they're connecting to a taproot-activated node? (If not, maybe this is
something we want nodes to advertise during activation of future
protocol extensions.)
Thanks,
-Dave
[1] https://github.com/bitcoin/bitcoin/commit/ccef10261efc235c8fcc8aad54556615b0cc23be
https://bitcoincore.org/en/releases/0.21.0/
[2] https://github.com/bitcoin/bitcoin/pull/20165
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20211121/d3dda5b4/attachment.sig>;
David A. Harding [ARCHIVE] /
npub16dā¦x4wrd
2023-06-07 23:00:38
in reply to nevent1qā¦3rnl
Author Public Key
npub16dt55fpq3a8r6zpphd9xngxr46zzqs75gna9cj5vf8pknyv2d7equx4wrdPublished at
2023-06-07 23:00:38Event JSON
{
"id": "2738f123a7d5408fcd3979bcc4541c98df68fcc37a5dd9922cac58e27e1b46c2",
"pubkey": "d3574a24208f4e3d0821bb4a69a0c3ae842043d444fa5c4a8c49c369918a6fb2",
"created_at": 1686178838,
"kind": 1,
"tags": [
[
"e",
"2893fc32fb2cb6c18f068f5dbd5c0f04a34906acad5f8456851956c683a3e121",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "š
Original date posted:2021-11-21\nš Original message:On Wed, Nov 17, 2021 at 08:05:55PM +0000, n1ms0s via bitcoin-dev wrote:\n\u003e This seems to be the case. I saw your reply on Bitcoin StackExchange\n\u003e as well. In bitcoinj I just made it so the client only connects to\n\u003e nodes with at least protocol version 70016. Seems to work well.\n\nHi,\n\nThis is a clever solution, but when I looked into this I found that P2P\nprotocol version 70016 was introduced in Bitcoin Core version 0.21.0[1].\nThis release will not ever relay taproot spends because it doesn't\ncontain taproot activation parameters[2]. So this heuristic is\nimperfect: it only works when it happens to connect to the 0.21.1 and\n22.0 versions of Bitcoin Core (or compatible nodes) which were\nprogrammed to begin relaying taproot spends starting one block before\nactivation.\n\nCan anyone recommend a better heuristic lite wallets can use to ensure\nthey're connecting to a taproot-activated node? (If not, maybe this is\nsomething we want nodes to advertise during activation of future\nprotocol extensions.)\n\nThanks,\n\n-Dave\n\n[1] https://github.com/bitcoin/bitcoin/commit/ccef10261efc235c8fcc8aad54556615b0cc23be\n https://bitcoincore.org/en/releases/0.21.0/\n\n[2] https://github.com/bitcoin/bitcoin/pull/20165\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 833 bytes\nDesc: not available\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20211121/d3dda5b4/attachment.sig\u003e",
"sig": "a2292ce1ac04e9f8b088cb262a5ba523d38620b93cf2bfb6229383c04c4f2bd8f12307a2743f0011fe3ad4337d3203883dfbdb431cd69d956f07cd9afe78b5d2"
}