RT JJS (@JJS36038159)Nick, there are THREE different concepts being conflated in this discussion.Let me distinguish them:TYPE 1: Standard Pruning (Already Exists)Deletes entire old blocks after validation. Keeps only recent blocks + UTXO set. Reduces storage from ~650GB to ~10GB.Limitation: Cannot bootstrap new nodes (missing historical blocks).Status: Built into Bitcoin Core since 2015TYPE 2: OP_RETURN-Specific Pruning (What Ghost Describes)Keeps block structure and transaction history, but removes only OP ...

RT Schmidty (@bitschmidty)> datacarriersize in a broken stateI assume this refers to the change to allow multiple op_returns, but maintain the total “payload” (arbitrary data) totaled across those op_returns. So the same op_return setting value in a previous Bitcoin Core version would allow the same payload as it would in Bitcoin Core v30. Greg summarizes the rationale as “The motivation for doing this is for situations where you cannot commit to all data efficiently otherwise. Think SIGHASH_SINGLE | ACP sc ...

Bitcoin Development & Community - The Bitcoin Core vs Knots debate has caused a vitriolic rift among Bitcoin devs and node runners [1] - An OG Bitcoiner who's largely NEUTRAL is breaking down the Core-v-Knots debate [1] Media Coverage - @BitcoinPierre explains Core-v-Knots with historic context on @Cointelegraph CHAINREACTION [1]

RT Robert Baggs (@rkbaggs)Do you really understand the Bitcoin Core vs Knots debate? I wouldn't blame you if you don't, but you're only about 30 minutes away from that knowledge.@gazza_jenks and I unpack the problem with one of our all-time favourite Bitcoiners, @BitcoinPierre!https://t.co/UEB9QIoUHR ...

Bitcoin Technology & Development - The debate centers around Bitcoin Core versus Bitcoin Knots [1] - The discussion involves unpacking the core of this contentious Bitcoin debate [1] Industry Experts & Platforms - Key individuals like @BitcoinPierre are involved in the discussion [1] - The discussion is hosted on Cointelegraph's CHAINREACTION platform [1]