Rob Hamilton from AnchorWatch joins us to talk about the explosive BIP 444 proposal that could fork Bitcoin. We break down PortlandHodl’s original 520-byte output limit idea, LukeDashjr’s controversial technique to ban inscriptions, and the legal pressure being applied to mining pools. Rob explains why this fork will likely fail, what happens to your Bitcoin if it succeeds, and why opponents finally admitted a consensus change was needed all along.
Subscribe to the newsletter! https://newsletter.blockspacemedia.com
Notes:
• BIP 444 limits outputs to 520 bytes max
• OP_RETURN reduced from current to 84 bytes
• F2Pool controls 12% hash rate, opposes fork
• Mining pool switching costs nearly nothing
• Fork creates 2 coins: pure vs unholy Bitcoin
• Legal pressure applied to multiple pools