-
Notifications
You must be signed in to change notification settings - Fork 193
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
Validate batch merkle root #312
Validate batch merkle root #312
Conversation
core/validator.go
Outdated
type ChunkValidator interface { | ||
ValidateBatch([]*BlobMessage, *OperatorState, common.WorkerPool) error | ||
ValidateBlob(*BlobMessage, *OperatorState) error | ||
type DataValidator interface { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
shall we create a name for data that's received by node (e.g. shard, BlobShard)? This naming may be more specific
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you suggesting changing BlobMessage
into BlobShard
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm suggesting "DataValidator" to something more specific such as "BlobShardValidator"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
DataMessageValidator? Shard stands out too much
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about just ShardValidator
?
Why are these changes needed?
Why is it needed, indeed.
Checks