Skip to content

Allow block responses to MSG_CMPCT_BLOCK requests#406

Merged
luke-jr merged 1 commit intobitcoin:masterfrom
TheBlueMatt:master
Jun 17, 2016
Merged

Allow block responses to MSG_CMPCT_BLOCK requests#406
luke-jr merged 1 commit intobitcoin:masterfrom
TheBlueMatt:master

Conversation

@TheBlueMatt
Copy link
Copy Markdown
Contributor

No description provided.

@TheBlueMatt TheBlueMatt force-pushed the master branch 2 times, most recently from 1f80377 to fe18050 Compare June 17, 2016 00:43
@luke-jr luke-jr merged commit 97dbb89 into bitcoin:master Jun 17, 2016
Comment thread bip-0152.mediawiki
# getdata messages may now contain requests for MSG_CMPCT_BLOCK objects.
# Upon receipt of a getdata containing a request for a MSG_CMPCT_BLOCK object with the hash of a block which was recently announced and after having sent the requesting peer a sendcmpct message, nodes MUST respond with a cmpctblock message containing appropriate data representing the block being requested.
# Upon receipt of a getdata containing a request for a MSG_CMPCT_BLOCK object with the hash of a block which was recently announced and is close to the tip of the best chain of the receiver and after having sent the requesting peer a sendcmpct message, nodes MUST respond with a cmpctblock message containing appropriate data representing the block being requested.
# Upon receipt of a getdata containing a request for a MSG_CMPCT_BLOCK object for which a cmpctblock message is not sent in response, a block message containing the requested block in non-compact form MUST be sent.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How is it determined when it's not sent?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants