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

Eth Wire Protocol #167

Closed
germsvel opened this issue Jun 14, 2018 · 4 comments
Closed

Eth Wire Protocol #167

germsvel opened this issue Jun 14, 2018 · 4 comments

Comments

@germsvel
Copy link
Contributor

germsvel commented Jun 14, 2018

We are currently handling the encrypted handshake and deriving secrets needed to frame the rest of the messages.

Issue #166 will handle the DEVp2p handshake (and other messages). Once that handshake is successful, we can handle subprotocols.

The main subprotocol is the Ethereum Wire Protocol (https://github.com/ethereum/wiki/wiki/Ethereum-Wire-Protocol). We should handle this first (both v62 and v63), and then deal with Whisper (issue #105) and Swarm (issue #104) later.

@masonforest
Copy link
Contributor

Thanks for writing these! It's nice to have a better idea of where we are and where we are going.

I'd say implementing Whisper and Swarm should be postponed until other functionality is implemented because as far as I can tell they aren't part of the core protocol.

@igorbarinov you mentioned Whisper in Cincinnati. Does POA require the Whisper protocol?

Swarm seems like a separate project all together. I don't see any reference to it in Parity.

It's too bad so much of this is up in the air: part of the nature of decentralization I guess.

@germsvel
Copy link
Contributor Author

Yeah, from my point of view (which is still limited) I think we can defer Whisper and Swarm until much later. I just mentioned them in this issue because I knew we had issues for them, and I know they're mentioned around.

@masonforest
Copy link
Contributor

cool, yeah good to have them on the Radar 👍

@hayesgm
Copy link
Contributor

hayesgm commented Dec 1, 2018

This has been completed.

@hayesgm hayesgm closed this as completed Dec 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants