/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: Add Section About Headers-First IBD #736

Merged
merged 2 commits into from Feb 20, 2015

Conversation

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

harding commented Feb 5, 2015

Preview: http://dg0.dtrt.org/en/developer-guide#headers-first

This adds a short section describing headers-first Initial Block Download (IBD) to the developer guide. This was originally part of pull #660, but it has been substansially rewritten. (And, I hope, improved.) Specifics:

  • Add flowchart illustration to blocks-first section to match new headers-first flowchart
  • Add new headers-first (IBD) section
  • Revise Block Broadcasting section to describe non-IBD block transmission workflow
  • Add paragraph about how headers-first avoids handling orphan blocks to the Orphan Blocks section
@harding
Dev Docs: Add Section About Headers-First IBD 
* Add flowchart illustration to blocks-first section to match new
  headers-first flowchart

* Add new headers-first initial block download (IBD) section

* Revise Block Broadcasting section

* Add paragraph about orphan block handling in headers-first to the
  Orphan Blocks section
This commit was signed with a verified signature.
@harding harding David A. Harding
GPG key ID: 4B29C30FF29EC4B7 Learn about signing commits
72cc5f7

@harding harding added the Dev Docs label Feb 7, 2015

@saivann saivann commented on an outdated diff Feb 19, 2015

View full outdated diff
_includes/guide_p2p_network.md
{% include helpers/subhead-links.md %}
{% autocrossref %}
-At the start of a connection with a peer, both nodes send `getblocks` messages containing the hash of the latest known block. If a peer believes they have newer blocks or a longer chain, that peer will send an `inv` message which includes a list of up to 500 hashes of newer blocks, stating that it has the longer chain. The receiving node would then request these blocks using the command `getdata`, and the remote peer would reply via `block`<!--noref--> messages. After all 500 blocks have been processed, the node can request another set with `getblocks`, until the node is caught up with the network. Blocks are only accepted when validated by the receiving node.
+Bitcoin Core 0.10.0 uses a initial block download (IBD) method called
@saivann

saivann Feb 19, 2015

Contributor

@harding s/a initial/an initial/ maybe?
@saivann
Contributor

saivann commented Feb 19, 2015

@harding Very clear, thanks!
@harding
Dev Docs: Fix a->an typo (thanks Saïvann!)
This commit was signed with a verified signature.
@harding harding David A. Harding
GPG key ID: 4B29C30FF29EC4B7 Learn about signing commits
3d7ba83
@harding
Contributor

harding commented Feb 19, 2015

@saivann thanks! I fixed the typo you found.

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

@harding harding merged commit 3d7ba83 into bitcoin-dot-org:master Feb 20, 2015

harding added a commit that referenced this pull request Feb 20, 2015

@harding
Merge pull #736: Dev Docs: Add Section About Headers-First IBD
This commit was signed with a verified signature.
@harding harding David A. Harding
GPG key ID: 4B29C30FF29EC4B7 Learn about signing commits
94c1166

@harding harding deleted the harding:headers-first branch Feb 25, 2015

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