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.

Sign up for GitHub

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

Jump to bottom

Do SignedPeerRecords need to support custom field pairs as ENRs do in nim-eth? #23

Open
emizzle opened this issue Mar 16, 2022 · 1 comment
Open

Do SignedPeerRecords need to support custom field pairs as ENRs do in nim-eth? #23

emizzle opened this issue Mar 16, 2022 · 1 comment

Comments

@emizzle
Copy link
Collaborator

emizzle commented Mar 16, 2022

No description provided.

@cskiraly
Copy link
Collaborator

No, I think we should remove that part. We need flexibility in transport addresses as it is done in PeerRecords, but I do not think we would need a generic "custom field" mechanism.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cskiraly @emizzle