Get a list of operators which exited the system (either due to opt-out, churn, or booting) within the last 14 days. #131
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
December 15, 2023 14:38
…t, churn, or booting) within the last 14 days.
jianoaix
reviewed
Dec 18, 2023
wmb-software-consulting
force-pushed
the
feat/get-operators-exited-system
branch
from
435c04c to
d5ad482
Compare
jianoaix
approved these changes
Dec 19, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why are these changes needed?
After an operator is no longer a member of EigenDA network (due to opt-out, churn or booting), they will stop receiving dispersal traffic (i.e. stop attesting the blobs). However, they are still held responsible for serving the blobs that they have signed until the blobs get expired (14 days after signing).
Checks