Thanks for the correction. I've seen both sides misrepresent this now in arguing over what does/doesn't get stored. Think this gives me an idea to hit AI with.

It definitely seems like it was an overreaction to the announcement of the out-of-band offerings like Mara's SlipStream.

Was it really encouraging it though? Or was it hoping that those misusing other, non-pruneable fields like witness data would take the olive branch and move their data use there so at least it could be pruned by those not running full archival nodes? Again, probably another overreaction that came out of the temporary Ordinal craze.

This is something we both can agree on. I do wish we would see more Bitcoin node implementations and I've held that belief for quite awhile.

You are correct. I blew away my old install, slapped 0.4b9 on it and now v31 is synching.

Start9 is saying it should work fine and my OS isn’t current. I checked that first and it said current so I may have bigger issues with my node.

May need to completely blow it away and reinstall from scratch.

I assume all of the miner support is just hiding until the last minute, right?

https://wickedsmartbitcoin.com/bip110_signaling

Which is still non-monetary use. Luke, Mechanic, et al have publicly stated multiple times Bitcoin should not be used for non-monetary transactions. They've also stated on Spaces they will continue to squeeze until they find a working solution. So they are the judge, jury and executioner of how block space can be used?

The ultimate point is BIP-110 solves nothing. Now instead of having the ability to prune that data out of the larger op_return, "bad actors" will be forced to chunk it across multiple fields/UTXOs which will then be immutable. I lose optionality as a node runner. So if they truly believed the CSAM talking point, they now guarantee it will exist.

Finally, it also keeps the same core issues they point to with the larger op_return field: 1) greater fees; and 2) blockchain bloat. When you mention this, they state the fees would then be the filter which is exactly what non BIP-110 people have been saying about the current implementation.

They've pivoted from CSAM.

It was expensive a couple years back when Ordinals, Inscriptions, et al were the shiny new toys. Then people realized all of it was garbage and fees went reverted back down to where we're at. But they paid it.

By moving it out of op_return, you will force them to chunk it across multiple UTXOs which will push fees up again. If they deem it important, they will pay it again.