BIP-FAIR: Fair Fee Accounting for On-Chain Data with Segregated OP_RETURN (segOP)
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 tran
No reviewsSpecification
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.
Discussion (0 threads)
Loading discussions...