-
Notifications
You must be signed in to change notification settings - Fork 17
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
feat!: create native blob struct #74
Conversation
I haven't added a maximum size check to the length of the signer. |
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.
LGTM, great work
Co-authored-by: Rootul P <[email protected]>
if err != nil { | ||
// TODO: we should look at having a go native BlobTx type | ||
// that we have already verified instead of doing it twice here | ||
panic(fmt.Sprintf("invalid blob %d: %v", idx, err)) | ||
} |
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.
Turning this into an issue
if err != nil { | ||
// TODO: we should look at having a go native BlobTx type | ||
// that we have already verified instead of doing it twice here | ||
panic(fmt.Sprintf("invalid blob %d: %v", idx, err)) |
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.
[not blocking nit]
can we add add a comment to this issue to indicate that it requires that all blobs passed to it are valid?
either that or add a new method / break this api that allows for error handling. my personal preference is that we panic as high in the stack as possible as that makes the problem that much clearer.
This builds on #72
Closes: #70
Note: this does not touch any of the share construction yet