nostr relay proxy

event page

What are the odds that core devs screw up again with something but way more significant than this? Not fixing datacarrier size was the major red flag. Majority of bitcoiners decided to be complacent with that and now core devs broke BIP85 for no reason. Nobody asked for this change. Not sure when bitcoiners will realize that this is one of the major attack vectors to #bitcoin. There are almost no influencers who criticize #bitcoin core as much as they deserve to be criticized. If you are pleb like myself (who don't know how to code) and if you want to show your frustration, I would strongly run my own node with Knots instead of original #bitcoin core. I get that some of the changes you can't prevent it from implementing it because knots is not built from scratch but it would likely help us to get rid of some of these incompetent (& compromised) core devs. If we really want to see #bitcoin as a unit of account, I don't see how we can get there with the current state of #bitcoin core. I am not sure if it's feasible or not but it's a high time that nostr:npub10pensatlcfwktnvjjw2dtem38n6rvw8g6fv73h84cuacxn4c28eqyfn34f (cc nostr:npub1qny3tkh0acurzla8x3zy4nhrjz5zd8l9sy9jys09umwng00manysew95gx) and other open source funding organizations MUST stop funding core and maybe provide more funding to knots or people/entities who are willing to create new bitcoin client from scratch. #BITCOIN CORE CANNOT BE TRUSTED ANYMORE. #STOPRUNNINGCORE https://github.com/bitcoin/bips/pull/1673#pullrequestreview-2349350804

rendered in 3.539288ms