Update and add exemptions and limits for Miniscript/covenants/BitVM/…

[JonnyFJi]

…Update and add exemptions and limits for Miniscript/covenants/BitVM/…Taproot Assets/L2 and L2 anchors

Add exemptions for Miniscript/covenants/BitVM/Taproot Assets/L2 while preserving anti-spam focus. Discussed on bitcoindev ML. Tested on Knots/testnet4

[JonnyFJi]

Add exemptions for Miniscript/covenants/BitVM/Taproot Assets/L2 while preserving anti-spam focus. Discussed on bitcoindev ML. Tested on Knots/testnet4...

[murchandamus]

I don’t think this proposed change make sense as proposed. Firstly, it doesn’t fit at all into the flow of the document, and secondly, some of these directly contradict design goals of BIP 110—e.g. you reintroduce inscription envelopes.

@dathonohm, could you please take a look at these proposed changes to your document? Please feel free to simply reject this suggestion, if it makes no sense to you either.

[dathonohm]

@murchandamus I agree, this change would significantly weaken BIP-110's rejection of data storage, and the author has not sufficiently explained what the benefits would be. Feel free to close it.

[JonnyFJi]

BIP-110 is temporary, but to minimize impacts on developments such as Miniscript, covenants, BitVM, Taproot Assets, quantum-resistant (e.g., BIP-360) and L2, adjustments to limits or specific exemptions are proposed without altering its anti-data focus.

[murchandamus]

@JonnyFJi: Please don’t create busywork here.

[dathonohm]

@JonnyFJi BIP-110 does not interfere with development for any of those things, besides prohibiting them from activating on Bitcoin mainnet before September 2027, at the latest. Development can still proceed anywhere besides mainnet. All of this is already covered in BIP-110.