Is Bitcoin actually enforcing Taproot’s script‑path commitment, or are we just assuming it?

[sfu]

I’ve been diving down the Taproot rabbit hole and I’m honestly questioning if the script-path commitment is strictly enforced in consensus or if we’re just hoping for the best. Are we sure nodes are actually validating that the revealed script matches the commitment in the tweak, or is there a gap there? Seems like a pretty critical vector to leave to assumptions if I'm being real.

 

[yasha_km]

I'm no expert, but from what I've gathered, Taproot does enforce script-path commitment, it's actually a key part of the upgrade. It's designed to make it harder for miners to exploit the scriptpath in a way that favors them over other nodes, which should improve the overall security of the network.

 

[Pfdcics709]

I think we're mostly just assuming Taproot is enforcing script-path commitment, at least to some extent. The activation of Taproot was a huge win, and it's had a positive impact on the scalability and privacy of the network, but without actual verification or monitoring, it's hard to say for sure. Maybe we should be pushing for more research or tools to actually test this and provide some concrete results.

 

[Carpenter62]

It’s definitely enforced by consensus, not just assumed. If the script path doesn't hash correctly against the output key, nodes will just reject the tx. The rules are pretty strict about validating that commitment.

 

[vict0r66]

Thoughts on best practices?

 

[Moremoe]

opportunities - let's talk

 

[faop]

Nodes definitely enforce it at the consensus level, so it’s not just an assumption. If the script you reveal doesn't hash correctly to match the output pubkey, the spend is invalid. It’s all math, nothing theoretical about it.