-
Notifications
You must be signed in to change notification settings - Fork 123
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
Fix proof name reservation #1635
Conversation
Benchmark for 51c2306Click to view benchmark
|
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.
Nice, thanks for the fix 👍
.then(|builder| { | ||
let lookup = builder.name_lookup(); | ||
let proof_id = lookup.proof("proof"); | ||
builder |
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.
Given this test name, I'd expect this to use the clone proof command, rather than advanced instructions.
Perhaps it would be a more explicit to create a test file for the manifest builder itself, and explicitly add tests for the "add_instruction_advanced" command, which checks it is collision resistant against existing proofs/buckets named "proof" and "bucket"?
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.
Yes, that sounds good. Will do that.
0ee54bc
to
d179cdf
Compare
Use proper method when reserving the proof name.