Implement storage of Ephemereal Headers #3058

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

Open

kdeme opened this issue Feb 10, 2025 · 0 comments

Labels

Fluffy portal-history

Contributor

kdeme commented Feb 10, 2025

The content type has been added already, but validation/storage currently is not done. Needs to be implemented.

On the database side this means a separate sql table with functionality to access the content as it is required for the network requests.

kdeme added Fluffy portal-history labels

kdeme mentioned this issue

Adjust contentdb to be able to keep track of headers without a proof for later purging #2207

Closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment