bitcoin.org fork policy vague #9161

issue rebroad opened this issue on November 15, 2016
  1. rebroad commented at 4:41 AM on November 15, 2016: contributor

    https://bitcoin.org/en/posts/hard-fork-policy

    This page seems to be misleading - it seems to suggest that "hard forks" are in some way worse than "soft forks" when it seems to me that the opposite is true. This conclusion has also been reached by other bitcoin developers. Can this page be clarified? Can "contentious" be defined, for example?

    Soft forks are being proposed as bad because it makes it harder (if not impossible) for older nods to audit correctly - i.e. it intentionally creates a way for invalid transactions to appear valid to older software thereby taking away their ability to detect that they need to upgrade or change their rules. Hard forks on the other hand provide more "informed consent" being more transparent about a change in protocol.

    This arguments above (also made by other developers) seem quite logical and persuasive, and therefore if Core has equally strong logical arguments for soft forks being better/preferable, then I think the opportunity is currently being missed to put these forward in the current web page.

  2. rebroad commented at 4:44 AM on November 15, 2016: contributor

    https://medium.com/@octskyward/on-consensus-and-forks-c6a050c792e7#.apjir3k5d - an example of another developer who sees hard-forks as superior to soft-forks. I'm inclined to agree with their analysis, so far, which is why I would like to see more conclusive counter-arguments included in the bitcoin.org website.

  3. jonasschnelli commented at 5:50 AM on November 15, 2016: contributor

    Stop spamming please.

  4. jonasschnelli closed this on Nov 15, 2016

  5. luke-jr commented at 8:14 AM on November 15, 2016: member

    @rebroad A hardfork by nature must have consensus from the entire community before deployment. Attempts to deploy without such consensus transform it into an altcoin, which is clearly inappropriate for a Bitcoin webstie.

  6. rebroad commented at 8:35 AM on November 15, 2016: contributor

    https://www.reddit.com/r/btc/comments/428tjl/softforking_the_block_time_to_2_min_my_primarily/ - yet another credible developer also saying the same thing. @jonasschnelli do you know what "spam" even means? (my understanding of the term is that it has always meant unsolicited commercial email). @luke-jr I either don't understand or agree with your definition of hard-fork, nor alt-coin, for that matter. What is the point of such definitions? What does it serve?

  7. laanwj commented at 8:39 AM on November 15, 2016: member

    Stop spamming this. Bitcoin Core is a separate project from "bitcoin.org". If you have beef with anything on their site you should comment there. Though these hardfork versus softfork discussions have been done so many times and people are tired of it so I don't think people will be thankful to you for regurgitating this.

  8. rebroad commented at 8:46 AM on November 15, 2016: contributor

    @laanwj Previously this github repository was the place to report problems with bitcoin.org - I apolgise, I was not aware that it had been moved.

  9. laanwj commented at 8:49 AM on November 15, 2016: member
  10. DrahtBot locked this on Sep 8, 2021

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-22 18:15 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me