BIP-FAIR: Fair Fee Accounting for On-Chain Data with Segregated OP_RETURN (segOP)

[defenwycke]

Author: defenwycke defenwycke@icloud.com

This BIP removes the 75% witness discount for non-script data, introduces segOP as a clean, Merkle-rooted data section, and enforces a 100 KB total data cap per transaction.

Key Rules

• Data: OP_RETURN, segOP, or witness items >520 B (Taproot max push size)
• Fee: Full 4 wu/byte for data (weight += data_size * 3)
• Cap: 100,000 bytes total per tx
• segOP: Post-witness, structured, verifiable via Merkle root

Normal financial transactions are unaffected. Spam becomes uneconomical.

Soft fork via BIP 9 (bit 5). Reference implementation included.

Feedback welcome.

[jonatack]

Hi @defenwycke, has this proposal been previously discussed with the community in a dedicated thread on the mail list?

Please see BIP 2 for the process -- suggest searching in it for sections containing the term "list".

[defenwycke]

Hi @jonatack. I sent an email earlier to the dev group email.

[jonatack]

Hi @jonatack. I sent an email earlier to the dev group email.

Thanks @defenwycke. In that case, this PR was opened prematurely. Please carefully read and follow the process described in BIP2.

[defenwycke]

Hey @jonatack. Yes - noted.

[jonatack]

Please do not use AI/LLMs. See https://github.com/bitcoin/bips/pull/2006/files for more.

[jonatack]

Closing for the reasons in #2024 (comment) and #2024 (comment). You are free to retry via correctly following the process described in BIPs 2 / 3 and without using AI. Regards.