Bitcoin’s developer community is in civil war again ⚔️ A simple code change has split devs over what Bitcoin should be. On @unchained_pod, @adam3us & @cguida6 debate: 🔥 Why a 10-year-old “spam” filter has reignited developer wars 💾 How NFTs & “image spam” triggered the split ⚙️ Whether forcing protocols into "fake pub keys" makes things worse Timestamps: 🎬 0:00 Intro ⚙️ 1:37 What the #Core vs. #Knots debate is really about 🧩 4:46 Why “spam” filtering and “censorship” aren’t the same 💾 7:28 How #NFTs, #ordinals, and #BRC20s created the “spam” problem 🧱 8:51 The Genesis block message vs. today’s onchain data 🔍 13:27 What #OP_Return does and why its size limit matters ⚔️ 22:04 Why the proposed change has split the Bitcoin community 📈 26:25 Can #Bitcoin stay censorship-resistant while filtering “spam”? 💣 30:26 Do economic incentives make “spam” filters useless? 🧰 34:17 Why some believe filters still work to protect blockspace 💰 36:05 Would higher fees from non-payment data help miners secure Bitcoin? 🧮 42:06 Does more data make it harder to run a node? 🧭 46:04 Can Bitcoin fight storage data without hurting its core principles? ⚡ 50:37 What counts as a “real” layer 2 on Bitcoin 🧱 55:55 How much support the Knots software actually has 🧩 1:00:35 Could this debate cause a Bitcoin chain split? 🔚 1:04:22 Closing thoughts on what’s next for the network