rich1.0Sourcenode (npub1jf…zt047)https://yabu.me/npub1jfn4ghffz7uq7urllk6y4rle0yvz26800w4qfmn4dv0sr48rdz9qyzt047njumphttps://yabu.menostr:nprofile1qqsywt6ypu57lxtwj2scdwxnyrl3sry9typcstje65x7rw9a2e5nq8spramhxue69uhky6t5vdhkjmndv9uxjmtpd35hxarn9ehkumrfdejsz9thwden5te0v4jx2m3wdehhxarj9ekxzmnytjq0jg nostr:nprofile1qqsqfjg4mth7uwp307nng3z2em3ep2pxnljczzezg8j7dhf58ha7ejgpp4mhxue69uhkummn9ekx7mqprpmhxue69uhhqun9d45h2mfwwpexjmtpdshxuet5hgfg9w I listened to RHR397 this morning specifically to hear your take on BIP110. I still don't have a strong opinion in either direction, but I do want to understand the issue. I respect your opinion after years of seeing you stand your ground on important topics. Matt, what you said about your intentions made sense and I believe you hold the best interest of Bitcoin at heart, but much of the reasoning shared on this topic rested upon ad hominems and accusations about Luke's intentions. While you could be right, personally I don't think Luke or Mechanic are being malicious on purpose. I also believe assuming mal intent or building a case for it doesn't serve a practical purpose. I'm saying this because I've seen a lot of mud slinging on both sides of this debate and I know for certain that will not help. Any outside onlooker who enters the discussion at this point is going to see the same thing I see; nerd rage amateur hour. This week I saw devs, authors, and entrepreneurs calling each other liars like six year olds. It's a poor look and it's poor form for resolving conflict. I'm not here to tell anyone how to behave, but I think we are all capable of better behavior than that. Near the end there was a brief mention that BIP110 will not correct the issue that it sets out to correct. I'd like to hear more about the technical aspects of this topic if you have a chance to cover them in future notes or podcast episodes. Thanks for reading man. Mad respect 🤙