No, I did not conflate contributors and maintainers. In Bitcoin Core nothing gets merged until it has been reviewed by several regular contributors, usually several times. Sure, one of the five maintainers (who are part of the regular contributors) is usually the last reviewer and will merge a PR if it has had enough review and they're satisfied, but they don't merge things that haven't been reviewed by other knowledgeable developers, mostly from those 40 regulars.
nostr:npub1j5mp526z5fkz9wkrk6mt5nzu43xndyrwkr8mnqngdqwytgcpc5vqcnsd5c post contains a critical oversight in conflating contributors with maintainers (most of the world has the same misconception or wrong perception as well). Bitcoin Core currently has just 5 maintainers with commit access (Hennadii Stepanov, Michael Ford, Andrew Chow, Marco Falke, and Gloria Zhao [just two years ago Gloria told me they were eight contributors then.]), not the "40 regular contributors" mentioned. This distinction matters profoundly for decentralization.
The maintainer exodus is concerning - Wladimir van der Laan (lead for 9+ years), Samuel Dobson, and Jonas Schnelli have all departed. These maintainers serve as gatekeepers with actual power to merge code, while contributors merely propose changes. This is a topic rarely discussed because the core of Core is not something you want the world to know about regarding their politics, risks, and threats. That's the main maintenance garage for the only workable money vehicle in human history.
Both Core and Knots ultimately represent centralized decision-making structures:Core with its 5-person bottleneck and Knots with its single-developer approach. The recent OP_RETURN controversy perfectly illustrates this tension, with Core's removal of the 80b limit triggering a 137% surge in Knots nodes (from 674 to 1,890 nostr:npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk nostr:npub1wnlu28xrq9gv77dkevck6ws4euej4v568rlvn66gf2c428tdrptqq3n3wr nostr:npub1rxysxnjkhrmqd3ey73dp9n5y5yvyzcs64acc9g0k2epcpwwyya4spvhnp8 ) as users actively choose which monetary values they want preserved.
While Bitcoin Core currently benefits from nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m 's principled funding (providing over 60% of its $8.4 million annual development budget), this centralized patronage model fundamentally contradicts Bitcoin's sovereign design and creates vulnerability to future influence shifts. The passionate debates between Bitcoin Core and Knots supporters may appear toxic to outsiders, but these confrontations serve as essential alarm bells that educate the ecosystem about threats to Bitcoin's monetary properties.
This is Bitcoin's true governance at work. While development teams may act as centralized decision-makers, ultimate power rests with individual Bitcoiners who collectively determine which vision prevails through their choice of software. Every node operator independently decides which implementation best preserves the monetary properties they value - whether that's #Core 's more permissive approach or #Knots ' stricter filters against non-monetary uses. This symbiotic relationship between Bitcoin and its most principled defenders ensures long-term resilience against changes that might compromise its fundamental value proposition. demonstrating that #Bitcoin needs sound money maximalists, imo, as much as maxis need Bitcoin to preserve the world's only truly sound money.
Discussion
Appreciate sharing the exact process Murch. What if the maintainer isn’t “satisfied”?
If a pull request doesn't pass review, the reviewers leave feedback on what to improve until it becomes ready for merge or work on it is discontinued. When pull requests run into well-reasoned opposition they tend to get closed to curb review time spent on things that are unlikely to be merged.
And since there has been no merge on PR #32359 how is it likely to play out iyo?