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

Configure client to put most recent BlobParams version in BlobHeader #1274

Open
litt3 opened this issue Feb 13, 2025 · 0 comments
Open

Configure client to put most recent BlobParams version in BlobHeader #1274

litt3 opened this issue Feb 13, 2025 · 0 comments

Comments

@litt3
Copy link
Contributor

litt3 commented Feb 13, 2025

Description

  • When deciding what value to put in the version field of the BlobHeader, the dispersing client should request the most recent BlobParams version from the eigenDA owned contract, and put that in the header
Image

Assumptions

  • We must be able to guarantee that no newly added BlobParams can feasibly be insecure
Image

Future Considerations

  • Given the assumption that no BlobParams configuration can possibly be insecure, it might make sense to eventually move the version out of the BlobHeader, and into the BlobCertificate, where it would be set by the disperser
    • The logic behind this is: "why should the dispersing client have to set a value that it doesn't care about?"
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
1 participant
@litt3