this post was submitted on 01 May 2025
184 points (100.0% liked)

Technology

38603 readers
477 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Hirom@beehaw.org 1 points 8 hours ago* (last edited 1 hour ago)

same on all chains. All have a proposal, discussion, implementation, waiting period (for code to be deployed), and activation

I though most of those steps didn't occur on-chain in the case of bitcoin. But I could be mistaken.

Would you mind sharing a link with the equivalent information on bitcoin, ie its governance process and how each governance operation (proposal, vote, activation ) is handled by the chain?

I'm looking at BIP-1. It explains how to submit a proposal via mailing list and versioned repository, ie off-chain.

Also looking at BIP-9. It does rely on the chain for governance, and allow polling for the most popular soft-fork. But it focus on exclusively on testing soft forks, which severely limit its usefulness.

allowing multiple backward-compatible changes (further called "soft forks") to be deployed in parallel.

It seems BIP-9 doesn't provide a solution to propose/vote/activate the larger non-backward-compatible changes, ie doesn't help prevent hard forks. And big social and environmental issues affecting bitcoin probably require such large change.