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

Connecting node with old pubkey #83

Open
Elfoniok opened this issue Sep 26, 2017 · 0 comments
Open

Connecting node with old pubkey #83

Elfoniok opened this issue Sep 26, 2017 · 0 comments

Comments

@Elfoniok
Copy link

There is a problem when connecting to node who's public key (so enode address also) changed.

If node change its address, it will be still addressed by others with its old address, but since it doesn't use old one it is impossible to decode messages sent to him and thus results in errors.

Previously it was asserts, now there are mostly format errors:
9cd6fbf

So right now it's handled but its hard to know what is happening, actual error was just hidden under the carpet. There could be some kind of logic when someone is trying to sent you messages using old enode address to simply notify the user.

There is also possibility of improvements? For example maybe nodes should broadcast whenever its enode address will 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

No branches or pull requests

1 participant