-
Notifications
You must be signed in to change notification settings - Fork 5
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
Add pczt inspect
command
#63
Conversation
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 except that we need a better way of identifying dummy outputs; we should consider whether this needs to go into the PCZT format as an explicit flag byte or something.
src/commands/pczt/inspect.rs
Outdated
for (index, value) in sapling_outputs.iter().enumerate() { | ||
if let Some(value) = value { | ||
if value.inner() == 0 { | ||
println!(" - Dummy Output"); |
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.
We shouldn't be using zero values on the output side to identify things as "dummies"; zero-valued outputs are valid and they may have a memo attached. We should also make sure that this isn't being done in the firmware.
src/commands/pczt/inspect.rs
Outdated
} | ||
if let Some(value) = output_value { | ||
if value.inner() == 0 { | ||
println!(" - Dummy Output"); |
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.
Ditto; we should probably have a way to specifically mark the dummies in the PCZT.
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.
utACK 4d92301
No description provided.