Started doing more research on how Bitcoin Core's developers have been attacking its sovereign/Medium-of-Exchange use a while back and it's wild.

The post became too long for email just from covering:

1. SegWit (BIP141): The “Witness Discount” and Block-Weight Accounting

2. Taproot (BIP340–342): Easier Complex Scripts and Data Embedding

3. Liberalized Data-Carrier Policies (OP_RETURN and “Standardness”)

4. Replace-By-Fee (RBF): From Opt-In to Broad Default

5. Relay and Mempool Settings that favor Large Players

6. Legal-Risk Externalities shifted to Node Operators

7. Increased Block Weight → Centralization Pressure

8. Convenience Defaults: Assumevalid, Pruning, and Checkpoints

9. Deprecation of Non-Standard Scripts

10. Fee-Market “Purism” — No Priority for Payments

11. Lightning Network Bias — L1 as Settlement Only

12. Governance Activations Show Who Sets the Rules

13. Quiet Merchant De-Feature: BIP70 Payment Protocol Deprecation

14. Removal of “Priority by Coin Age” & Free Relay (historical)

15. Dust Limits & MinRelayFee Floors as Gatekeepers

16. Core v30: OP_RETURN/data-carrier expansion (policy)

17. Core v30: RBF ergonomics tilt further to replaceability (wallet/API surface)

18. Core v30: Multiple OP_RETURNs per tx

Have written this in as simple as possible terms for non-developers. Will post later when done.