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

Keeping track of missing content #310

Open
morph-dev opened this issue May 30, 2024 · 0 comments
Open

Keeping track of missing content #310

morph-dev opened this issue May 30, 2024 · 0 comments

Comments

@morph-dev
Copy link
Contributor

Idea is that each client can keep a record of content that should be, but it's missing from the network. It should also store the proof that content should be there (and some other information that is needed in order to generate such content outside of the protocol).

Details on how many content to keep and whether it should expire is up to debate.

This would be consumed by a bridge responsible for "healing" the network and potentially glados.

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

No branches or pull requests

1 participant