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

p2p: Transmit ENR in RLPX handshake #19220

Closed
wants to merge 2 commits into from

Conversation

nolash
Copy link
Contributor

@nolash nolash commented Mar 6, 2019

This PR builds on the work by @fjl in including the ENR record of a node in the RLPx handshake. The implementation is unchanged, but makes necessary adjustments for the thus broken tests to pass.

It also introduces the enr record in the nodeconfig in the simulations framework, so this is externally available when setting up services for use in a simulation.

A simple POC code example for transmitting a swarm bzz key over ENR making use of these changes can be found here:

https://gist.github.com/nolash/9434ea24a71474bebcd0341c98685ff4

@fjl
Copy link
Contributor

fjl commented Mar 6, 2019

I don't want to merge this, but I'm writing an EIP at the moment that includes this change. Will post here when the EIP is submitted.

@nolash
Copy link
Contributor Author

nolash commented Mar 6, 2019

@fjl, oh, I see. So it is not at all certain that in the end the ENR record will be available over the RLPx handshake like this? (in protocol attributes, peerinfo)?

@fjl
Copy link
Contributor

fjl commented Mar 7, 2019

I definitely want it available after the handshake, but protocol changes need to go through the specification/EIP process before being included.

@nolash
Copy link
Contributor Author

nolash commented Mar 7, 2019

I definitely want it available after the handshake

Great, and with that you mean available in this way? Because if you do, I can continue the work based on the pending change.

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.

2 participants