Bitcoin TLDR

[BIP Proposal] Limit ScriptPubkey Size >= 520 Bytes Consensus.

By [BIP Proposal] Limit ScriptPubkey Size >= 520 Bytes Consensus PortlandHODL

bitcoin-dev

Involving Greg Maxwell, /dev /fd0+21 others

Original post on October 2, 2025 20:42 UTC

Last reply on October 22, 2025 08:07 UTC

bitcoin-dev

Brandon Black proposes a Bitcoin soft fork to declare large outpoints as invalid.
The proposal aims to enhance network security and address scalability issues.
It seeks feedback on balancing innovation and security within Bitcoin's evolution.

[BIP Proposal] Reduced Data Temporary Softfork

By [BIP Proposal] Reduced Data Temporary Softfork dathonohm

bitcoin-dev

Involving dathonohm, Jameson Lopp+9 others

Original post on October 25, 2025 20:43 UTC

Last reply on October 30, 2025 00:31 UTC

bitcoin-dev

The proposal aims to limit data at the consensus level through a temporary soft fork.
It introduces two activation methods, set to expire after one year for a lasting solution.
Community support is encouraged for swift activation and feedback, with a call for technical contributions.

[BIP Proposal] Soft Fork Compromise on op_return to Resolve Current Bitcoin Controversies

By [BIP Proposal] Soft Fork Compromise on op_return to Resolve Current Bitcoin Controversies Majorian

bitcoin-dev

Involving Martin Habovštiak, Russell O'Connor'+5 others

Original post on October 28, 2025 16:01 UTC

Last reply on October 29, 2025 15:03 UTC

bitcoin-dev

Majorian proposes a soft fork to resolve Bitcoin controversies by revising OP_RETURN usage.
The proposal limits OP_RETURN data to 83 bytes and allows only one output per transaction.
Aimed at community healing, it calls for minimal code changes and seeks feedback for a BIP.

Active Discussions