You misunderstand what BIP-110 actually does. It's not just restoring `datacarriersize` - it also caps witness data to stop 4MB inscription blocks (the actual source of 38% UTXO bloat). Core 30's `datacarriersize` setting doesn't stop Taproot witness spam - that requires consensus-level limits. On "no emergency": Changing the default from 80 bytes to uncapped in 52 days against 424 downvotes is the emergency. Yes, you can override it in `bitcoin.conf` (PR #33453 undeprecated it after backlash), but defaults matter. Core made spam-friendly the path of least resistance - that's capture of the default. BIP-110 doesn't remove alternatives - it's a soft fork. If hashrate doesn't hit 55%, nothing changes. You can run Core 30 forever and ignore it. If it activates, your Core node still works (stricter rules are backward-compatible). You don't get forked off - the spam does. "Luke coin" is just signaling you don't like the messenger. I don't run Knots for Luke - I run it because Core prioritized Citrea's ZK-rollup business model over node operators' resources. Run Core 30 with your `datacarriersize=80` if you want. But don't pretend it stops inscriptions, and don't pretend BIP-110 forces you anywhere. It's opt-in enforcement - exactly what you claim to want. Your move.