-
Notifications
You must be signed in to change notification settings - Fork 106
chore: remove library check for MAX_INPUTS_PER_NOTE
#2231
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -33,9 +33,6 @@ const ERR_PROLOGUE_NOTE_INPUTS_LEN_EXCEEDED_LIMIT="number of note inputs exceede | |
| #! | ||
| #! Invocation: exec | ||
| pub proc compute_inputs_commitment | ||
| # check that number of inputs is less than or equal to MAX_INPUTS_PER_NOTE | ||
| dup.1 push.MAX_INPUTS_PER_NOTE u32assert2.err=ERR_PROLOGUE_NOTE_INPUTS_LEN_EXCEEDED_LIMIT | ||
| u32lte assert.err=ERR_PROLOGUE_NOTE_INPUTS_LEN_EXCEEDED_LIMIT | ||
| # => [inputs_ptr, num_inputs] | ||
|
|
||
| # compute the inputs commitment | ||
|
|
@@ -47,9 +44,6 @@ pub proc compute_inputs_commitment | |
| # => [INPUTS_COMMITMENT] | ||
| end | ||
|
|
||
| # Re-export the max inputs per note constant. | ||
| pub use ::miden::protocol::util::note::MAX_INPUTS_PER_NOTE | ||
|
Comment on lines
-50
to
-51
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Let's move this to the top of the file - maybe after the "errors" section (create a new "constants" section). Also, not related to this PR, but we should update the docs. Specifically, here we no longer have |
||
|
|
||
| #! Writes the assets data stored in the advice map to the memory specified by the provided | ||
| #! destination pointer. | ||
| #! | ||
|
|
||
This file was deleted.
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 think we should still keep this check - the use case for this is different from what we do in the prologue. Specifically, this procedure is used to build note inputs for output notes. So, we still want to make sure here that the user doesn't compute invalid note input commitment.