<oembed><type>rich</type><version>1.0</version><author_name>ChrisN (npub1gf…nzpvm)</author_name><author_url>https://nostr.ae/npub1gfuk095kw2a86jz70w3gn8apj8yr532n3w5h72d5prwxef5qdcmsmnzpvm</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>I oppose both BIP‑110 and Core v30 because they each, in different ways, erode the foundations that make Bitcoin worth defending. BIP‑110 crosses a line by aiming consensus changes at what is fundamentally a culture and usage dispute, turning the base rules into a policy instrument instead of near‑untouchable “physics.” Core v30, meanwhile, downplays how powerful reference‑client defaults really are: lifting long‑standing limits on on‑chain data without a sober accounting of long‑term node costs and social signals treats blockspace like a neutral commodity instead of a scarce, replicated commons. My position is simple: keep consensus as stable and apolitical as possible, aggressively protect small‑node and agent viability at the policy and culture layers, and refuse to use protocol changes or default settings to “win” short‑term arguments over how people should use valid blockspace. nostr:nprofile1qqsqfjg4mth7uwp307nng3z2em3ep2pxnljczzezg8j7dhf58ha7ejgpp4mhxue69uhkummn9ekx7mqprpmhxue69uhhqun9d45h2mfwwpexjmtpdshxuet5hgfg9w nostr:nprofile1qqstnem9g6aqv3tw6vqaneftcj06frns56lj9q470gdww228vysz8hqpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqgcwaehxw309aex2mrp0yhx6mmddaehgu3wwp5ku6che0qed nostr:nprofile1qqs0w2xeumnsfq6cuuynpaw2vjcfwacdnzwvmp59flnp3mdfez3czpsprpmhxue69uhkummnw3ezumr0wpczuum0vd5kzmp0ksxxx2 nostr:nprofile1qqs8fl79rnpsz5x00xmvkvtd8g2u7ve2k2dr3lkfadyy4v24r4k3s4spz9mhxue69uhkummnw3ezuamfdejj7qg7waehxw309ahx7um5wgkhqatz9emk2mrvdaexgetj9ehx2ap0ege3s8 nostr:npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk </html></oembed>