add verified data transfer ingest report #421
Merged
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
The difference between valid and invalid up to this point. - Valid :: dc has been burned for the transfer event. - Invalid :: We don't know one of the entities involced. The invalid report will no longer be written. It is being replaced by Verified. All data transfer events that pass muster, we know the entities, it's not a duplicated, etc,. are written as Verified. Valid still means dc was burned.
bbalser
approved these changes
Oct 7, 2024
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.
The difference between valid and invalid up to this point.
The invalid report will no longer be written. It is being replaced by Verified. All data transfer events that pass muster, we know the entities, it's not a duplicated, etc,. are written as Verified. Valid still means dc was burned.