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

Technology

41139 readers
431 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
[–] locuester@lemmy.zip 1 points 8 months ago (1 children)

It’s no different. A new version of the consensus code needs written and deployed.

That page you linked is the same on all chains. All have a proposal, discussion, implementation, waiting period (for code to be deployed), and activation. That’s just blockchain 101

[–] Hirom@beehaw.org 1 points 8 months ago* (last edited 8 months 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.

Woule 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 9 and its stated goal is to support soft forks

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

This imply BIP-9 doens't help with non-backward-compatible changes, ie doesn't help prevent hard forks.