/bitcoin.org

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Dev Docs: Describe Soft And Hard Forks #615

Merged
merged 2 commits into from Oct 25, 2014

Conversation

Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
2 participants
@harding @saivann
@harding
Contributor

harding commented Oct 23, 2014

Preview: http://dg0.dtrt.org/en/developer-guide#consensus-rule-changes

Based on a suggestion made by @petertodd to the -devel mailing list and the discussion in that thread by him and other participants.

  • We've been using the term "consensus", but this commit introduces a formal definition for it and "consensus rules" as part of the block chain introduction.
  • Describe that consensus rules may change and may happen when they do: hard or soft forks.
  • Describe how full nodes can detect hard or soft forks, then describe how SPV clients can detect hard and soft forks using the more limited information available to them.
@saivann
Contributor

saivann commented Oct 23, 2014

@harding Maybe we could use a crossref link that points to "Detecting Forks" in the "Verifying payment" text? There's a paragraph here that refers to detecting forks.

http://dg0.dtrt.org/en/developer-guide#verifying-payment

I didn't review everything in detail, but LGTM in general! Thanks!
@harding
Contributor

harding commented Oct 23, 2014

@saivann great idea! Done in commit f157120 and preview updated. Thanks!

harding added some commits Oct 23, 2014

@harding
Describe Soft And Hard Forks 
Based on a suggestion made by @petertodd to the -devel mailing list and
the discussion in that thread by him and other participants.

* We've been using the term "consensus", but this commit introduces a
  formal definition for it and "consensus rules" as part of the block
  chain introduction.

* Describe that consensus rules may change and may happen when they
  do: hard or soft forks.

* Describe how full nodes can detect hard or soft forks, then describe
  how SPV clients can detect hard and soft forks using the more limited
  information available to them.
This commit was signed with a verified signature.
@harding harding David A. Harding
GPG key ID: 4B29C30FF29EC4B7 Learn about signing commits
2e8ceb2
@harding
Link To Detecting Forks From Verifying Payment Section (thanks @saivann… 
…!)
This commit was signed with a verified signature.
@harding harding David A. Harding
GPG key ID: 4B29C30FF29EC4B7 Learn about signing commits
a59b576
@harding
Contributor

harding commented Oct 24, 2014

Fixed a small typo in the text (a single s/upgrade/upgraded/) and updated the preview.

In the absence of critical feedback, this pull will be merged around 19:00 UTC Saturday.

@harding harding merged commit a59b576 into bitcoin-dot-org:master Oct 25, 2014

harding added a commit that referenced this pull request Oct 25, 2014

@harding
Merge branches 'consensus-forking' (pull #615) and 'byte-order' (pull #… 
…583)
This commit was signed with a verified signature.
@harding harding David A. Harding
GPG key ID: 4B29C30FF29EC4B7 Learn about signing commits
d5900e3

@harding harding deleted the harding:consensus-forking branch Feb 25, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment