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

Have the bridge use HD ephemeral identities #1228

Open
pipermerriam opened this issue Mar 23, 2024 · 3 comments
Open

Have the bridge use HD ephemeral identities #1228

pipermerriam opened this issue Mar 23, 2024 · 3 comments
Labels
shelf-stable Will not be closed by stale-bot

Comments

@pipermerriam
Copy link
Member

What is wrong

IIUC the bridge generates a new ephemeral key each time it boots up leaving us with a lot of single use entries in our census data.

How can it be fixed

ethereum/devp2p#254

I propose we default the bridge to operate using ephemeral HD identities. THere would be a single persistent "parent key". Each time the bridge runs it would randomly generate a new "path" in order to generate a child key that it would use as it's private key for that run. The ENR record would be updated to include the "parent key" and "path" so that glados would be able to link these ephemeral identities together.

@njgheorghita
Copy link
Collaborator

Is there another motivation for implementing this? Aka, testing out this scheme for the case where a single user with 100gb available storage spins up 10 x 10gb nodes derived from a parent key...

There have been some concerns in the past about letting the ENR grow too large, even adding a single character for the client type wasn't quickly adopted.

The simplest fix in this scenario is to simply use a consistent private key for the bridge, which we already support, it's just not enabled in our deployment scripts.

@pipermerriam
Copy link
Member Author

Yes, this would also be part of supporting ethereum/portal-network-specs#283

Copy link
Contributor

This issue is stale because it has been open for 180 days with no activity.

@github-actions github-actions bot added the stale label Sep 30, 2024
@morph-dev morph-dev added shelf-stable Will not be closed by stale-bot and removed stale labels Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
shelf-stable Will not be closed by stale-bot
Projects
None yet
Development

No branches or pull requests

3 participants