-
Notifications
You must be signed in to change notification settings - Fork 9
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
Pass fee and crossover in execute to fix wrong transaction hash #85
Conversation
Use the same exact rng provide when generating output notes
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.
Some things I'd like to see changed or addressed. I second @Neotamandua 's comment.
assets/dusk_wallet_core.wasm
Outdated
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.
This is a build artifact isn't it? As such it should not be added in this commit
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.
There's still an artifact here. Do we really want to keep it?
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 decided to keep it because one of the tests uses it
70078b1
to
e9ab926
Compare
Fix clippy warnings
1211c63
to
dbaa79f
Compare
We will need to regenerate the wasm with this PR and then release @ureeves Ready for re-review |
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.
@Daksh14 and I had a talk and decided that the Type
suffix is definitely a *nit, and since the WASM payload was already there, we can deal with it in a subsequent PR. Since those were the only two objections, I'm approving. LGTM!
Follow up #94 |
Use the same exact rng provided when generating output notes
Closes #84