I looked into it further, and it looks like bitcoind actually does confiscate some pre-P2SH outputs. For the sake of "simplicity," it applies the p2sh rules to all transactions in all blocks (including pre-P2SH blocks) except ones occurring in one specific block that the devs made a single exception for. Thus, the other exceptional outputs are now unspendable.

Source: https://github.com/bitcoin/bitcoin/blob/13891a8a685d255cb13dd5018e3d5ccc18b07c34/src/validation.cpp#L2305

nostr:nevent1qqs9ff54agldr9fyuudyg35qapnqr3cn69zgyxjfv36ytsq0kpqx7hcppemhxue69uhkummn9ekx7mp0qgszrqlfgavys8g0zf8mmy79dn92ghn723wwawx49py0nqjn7jtmjagrqsqqqqqpgwcgz5

Reply to this note

Please Login to reply.

Discussion

Bad news for spammers, looks like The Cat is not setting any precedent when it comes to freezing certain UTXOs. I’d imagine this will result in lots of crying and coping when it makes the rounds on Twitter.

nostr:nevent1qqs2crcktegr40k5nf0j30dp4v3dqxff9cm6due230qt42t3kjm8gtspz3mhxue69uhkummnw3ezummcw3ezuer9wc2gukfp

Which UTXOs specifically were confiscated by this? How do I spend to an output that would have been valid before this but is now unspendable due to this change? Otherwise there is no comparison.

A complete list of affected utxos are provided in the stack exchange post I linked to. You would spend them before bybprovoding the preimage to the hash160 hash as the only thing in your redeem script. After the change, you also have to hope the preimage is a valid bitcoin script and then hope you can provide any requisite arguments required by that script to make it return true, and provide those in your redeem script as well.

Thanks for the extra context. Sorry missed the stackexchange link.