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

Trin should gossip content before it drops it from storage #981

Closed
njgheorghita opened this issue Oct 11, 2023 · 2 comments · Fixed by #1341
Closed

Trin should gossip content before it drops it from storage #981

njgheorghita opened this issue Oct 11, 2023 · 2 comments · Fixed by #1341
Labels
enhancement New feature or request shelf-stable Will not be closed by stale-bot

Comments

@njgheorghita
Copy link
Collaborator

A possible enhancement came to mind during a recent chat with @carver that it would be worthwhile to gossip content as it gets dropped from storage. This won't help in situations when the network is over capacity, but in all other situations it should help maintain data availability in the network, as new nodes might have recently come online that would be interested in the data.

@njgheorghita njgheorghita added the enhancement New feature or request label Oct 11, 2023
@pipermerriam
Copy link
Member

I love this. Seems like it belongs in a section of the specs that would be focused on best practices for client implementations.

@njgheorghita njgheorghita added this to the EIP 4444 Network milestone Jan 19, 2024
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 Jul 18, 2024
@njgheorghita njgheorghita added shelf-stable Will not be closed by stale-bot and removed stale labels Jul 19, 2024
@njgheorghita njgheorghita mentioned this issue Aug 5, 2024
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request shelf-stable Will not be closed by stale-bot
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants