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

les: use eth64 instead of 63 #21980

Closed
wants to merge 1 commit into from
Closed

les: use eth64 instead of 63 #21980

wants to merge 1 commit into from

Conversation

holiman
Copy link
Contributor

@holiman holiman commented Dec 9, 2020

We're dropping support for 63 with 1.10, so would be good to have this in for the upcoming release

@holiman holiman added this to the 1.9.25 milestone Dec 9, 2020
@holiman
Copy link
Contributor Author

holiman commented Dec 9, 2020

... actually, I guess we should just use 65 instead?

Copy link
Member

@rjl493456442 rjl493456442 left a comment

Choose a reason for hiding this comment

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

It looks good to me. But It's really weird that we put a hardcoded ETH version. I will try to fix it later.

@holiman
Copy link
Contributor Author

holiman commented Dec 9, 2020

This fix is moot -- it's what the les server registers it's light-peers with in the downloader. So what matters is only that we're internally consistent, it doesn't matter what the remote client peer actually sends. So as long as we fix this in #21482 , that's fine

@holiman holiman closed this Dec 9, 2020
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