Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BIP 144: Segregated Witness (Peer Services) #272

Merged
merged 10 commits into from
Jan 8, 2016

Conversation

CodeShark
Copy link
Contributor

Needs BIP number

@btcdrak
Copy link
Contributor

btcdrak commented Jan 7, 2016

Looks like "spellcheck as you type" was enabled when creating the diagram giving the squiggly red lines.

=== Handshake ===
A new message 'havewitness' is sent after receiving 'verack' to
indicate that a node can provide witness if requested (similar to
'sendheaders') (Note: it might be better to signal this with a services bit in the version message)
Copy link
Contributor

Choose a reason for hiding this comment

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

Yes, please, consider using the services bit. Implementation wise, a client wanting to connect to a segwit supported node, don't want the need to wait for a magic timeout period to know if the node support segwit before trying the next one.

Using a message 'havewitness' will make peer discovery magnitude time longer.

@luke-jr luke-jr self-assigned this Jan 8, 2016
@luke-jr luke-jr changed the title Segwit peer services BIP 144: Segregated Witness (Peer Services) Jan 8, 2016
@luke-jr luke-jr merged commit d0ad38f into bitcoin:master Jan 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
4 participants