• Welcome to the Online Discussion Groups, Guest.

    Please introduce yourself here. We'd love to hear from you!

    If you are a CompTIA member you can find your regional community here and get posting.

    This notification is dismissable and will disappear once you've made a couple of posts.
  • We will be shutting down for a brief period of time on 9/24 at around 8 AM CST to perform necessary software updates and maintenance; please plan accordingly!

Brianna White

Administrator
Staff member
Jul 30, 2019
4,654
3,454
The crypto world is known for its volatility, and hard forks—blockchain updates with security patches or other changes in the code—reinforce this perceived lack of stability. With updates like the recent Ethereum London hard fork, resistors are left behind on an obsolete, outdated fork. In perhaps the most famous example of a hard fork, Bitcoin Cash, the adopters didn’t quite steal the show. The split still, however, followed a series of debates within the Bitcoin community, with tensions still high today. 
A better solution is needed to keep communities united while still allowing for blockchains to be updated. One major feature setting Polkadot’s “Layer 0” blockchain apart from others is its choice to be forkless, meaning there’s no need to create a fork in order to update the blockchain. As the crypto community continues to expand, a forkless future is the only way forward.
Blockchain is a decentralized system with anonymity. Therefore, it’s difficult to coordinate updates that will be agreed upon by the whole community, especially when it’s not always clear who is running the software. While blockchain upgrades are necessary for technological innovation, they lead to tensions within their respective communities, with endless debates on the necessity and timing of specific improvements. 
Continue reading: https://www.nasdaq.com/articles/no-more-forks%3A-a-case-for-the-polkadot-approach-to-blockchain-upgrades-2021-09-09
 

Attachments

  • p0004692.m04363.nasdaq.jpg
    p0004692.m04363.nasdaq.jpg
    2.5 KB · Views: 50