Unenforceable fee obligations in multiparty protocols with Taproot inputs



Summary:

On February 7th, 2023, Russell O'Connor notified the bitcoin-dev mailing list that there is a bug in Taproot where the same Tapleaf can be repeated multiple times in the same Taproot. This could lead to different Tapfee rates at different Taplevels. The countermeasure for this issue is to always know the entire Taptree when interacting with someone's Tapspend. Andrew Poelstra later clarified that in Taproot, the tapleaf hash is always covered by the signature, so signatures cannot migrate between tapbranches. The fix for the bug is to sign the entire tapbranch instead of the tapleaf. Michael Folkson pointed out that he wouldn't classify this as a bug unless there was a remedy for it that wasn't included in the Taproot design. He also mentioned that there seems to be a push to find "bugs" and "accidental blowups" in Taproot design currently.


Updated on: 2023-06-16T15:27:23.152071+00:00