pull down to refresh
340 sats \ 19 replies \ @optimism 11h \ on: Bitcoin devs cheer block reconstruction stats, ignore security budget concerns bitcoin
There seems to be a bit of a disconnect between the cheering around technical achievements and the economic reality that surrounds it, yes.
But if I look at both the comments and the article, then there's also a disconnect there: if you want quick block reconstruction by already knowing all the txs in the block beforehand, then it is useful to know... all the txs that are mined in the block, beforehand.
This is why not tracking transactions that you could know of is self-defeating. Whereas not mining transactions you consider undesired, is only unwise from a profit-maximalist perspective.
Technically, you can create any rules you desire for inclusion in your block templates without unnecessarily limiting your mempool's contents. All it takes is taking a step back and realize that you can be spam hating and censorship hating at the same time. This is the challenge to all that seem to be polarizing themselves over something as retarded as BRC-20.
The core dev team is too centralized
Paychecks from same company
Work in same office
We need knots and a third major client implementation too
reply
In my perception Bitcoin Core is the most decentralized it has ever been since the Gavin days.
reply
I don't think that it matters, because the problem isn't actual decentralization, but an accusation of conspiracy. And that's impossible to defend against. All you can do is not be trapped into reacting to it in any way 1
But I don't think that the "3rd fork" idea that has recently been re-popularized (e.g. #1223880) is such a bad idea; it can help lift some of the pressure and spotlight off of current Bitcoin Core contributors.
Footnotes
-
I have personally been in that situation - more than once - and I know very well that it truly sucks to have to let the punches land and not hit back in any way. It's also why I am an anon on SN and won't hesitate for a moment to burn and move on if I have to; I don't want to have to deal with that shit ever again on any other project than past ones I still, some days grudgingly, contribute to. ↩
reply
Yeah, don't get me wrong, I am in favour of a future where different clients are in a mad max like standoff, constantly trying to out compete each other, optimising for different use cases and targetting different audiences. It's great to see people seriously thinking about this.
reply
reply
The current core devs have only been there since about 2021 correct?
What are they responsible for in that time from the user’s perspective?
Inscriptions, forcing filter changes and now a 20% rebellion from the repo?
Inscriptions, forcing filter changes and now a 20% rebellion from the repo?
What is the track record that ya’ll are so eager to defend?
reply
reply
reply
reply
reply
reply