📅 Original date posted:2023-02-07
🗒️ Summary of this message: A bug in Taproot allows the same Tapleaf to be repeated multiple times, incurring different Tapfee rates; countermeasures include knowing the entire Taptree and implementing RBF.
📝 Original message:On Tue, Feb 07, 2023 at 01:35:12PM -0500, Russell O'Connor via bitcoin-dev wrote:
> There is a bug in Taproot that allows the same Tapleaf to be repeated
> multiple times in the same Taproot, potentially at different Taplevels
> incurring different Tapfee rates.
>
> The countermeasure is that you should always know the entire Taptree when
> interacting with someone's Tapspend.
Another countermeasure could be to implement RBF on taproot witnesses, allowing
transactions with deeper, less efficient, tapleaf scripts to be replaced with
shallower, more efficient, tapleafs. If implemented by giving your peer some
kind of delta encoded update, the bandwidth efficiency may be sufficient to
always allow such updates.
--
https://petertodd.org 'peter'[:-1]@petertodd.org
-------------- 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/20230207/38829718/attachment.sig>;
Peter Todd [ARCHIVE] /
npub1m2…a2np2
2023-06-07 23:19:27
in reply to nevent1q…fuwh
Author Public Key
npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2Published at
2023-06-07 23:19:27Event JSON
{
"id": "2e76c281c2fe0b58a7aa2f66fafdf0dc18b581aec9c3e2a5e8d5a9b796c5f4d9",
"pubkey": "daa2fc676a25e3b5b45644540bcbd1e1168b111427cd0e3cf19c56194fb231aa",
"created_at": 1686179967,
"kind": 1,
"tags": [
[
"e",
"1cb271826c48de88a6304ac8ffedd6340167a6ad4b82c11ba779c915dfc4192e",
"",
"root"
],
[
"e",
"ab58106809a9dbfa89df3171077a3cb0696f850a6ab029e850d9d6ec3adc6f17",
"",
"reply"
],
[
"p",
"6b8e77368804013d7126ba4b77c7963bcfeff909135791531097d7a0f03ca85d"
]
],
"content": "📅 Original date posted:2023-02-07\n🗒️ Summary of this message: A bug in Taproot allows the same Tapleaf to be repeated multiple times, incurring different Tapfee rates; countermeasures include knowing the entire Taptree and implementing RBF.\n📝 Original message:On Tue, Feb 07, 2023 at 01:35:12PM -0500, Russell O'Connor via bitcoin-dev wrote:\n\u003e There is a bug in Taproot that allows the same Tapleaf to be repeated\n\u003e multiple times in the same Taproot, potentially at different Taplevels\n\u003e incurring different Tapfee rates.\n\u003e \n\u003e The countermeasure is that you should always know the entire Taptree when\n\u003e interacting with someone's Tapspend.\n\nAnother countermeasure could be to implement RBF on taproot witnesses, allowing\ntransactions with deeper, less efficient, tapleaf scripts to be replaced with\nshallower, more efficient, tapleafs. If implemented by giving your peer some\nkind of delta encoded update, the bandwidth efficiency may be sufficient to\nalways allow such updates.\n\n-- \nhttps://petertodd.org 'peter'[:-1]@petertodd.org\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/20230207/38829718/attachment.sig\u003e",
"sig": "3b6c9dacf59b79154e1c6144d80e81cf84477192bdc37639cfc3777c616f408850e13c2032b70a9bec71cc9ed0d14e74bbf836e1e3920b93205bab16ddd7b07e"
}