-
Notifications
You must be signed in to change notification settings - Fork 0
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
refactor(core/cardano): decouple address parameters validation #60
Conversation
6789fb4
to
f8aa420
Compare
a2e97e9
to
57081a4
Compare
b5c1ee5
to
b0f1ca4
Compare
In the end I decided to add the check that I also added a commit for checking that outputs don't contain both |
@janmazak please take another look at this. |
I've also added the commit which reintroduces max tx output size to this PR ac66518. I think it should be better for Trezor guys to have a single PR which contains multiple small fixes than three tiny PRs. |
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.
Only two minor things.
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.
just a few improvement ideas and clarifying questions
Output size is currently limited to 4000 bytes at protocol level. Given the maximum transaction size Trezor can handle (~9kB), we also want to enforce this size limit here so that when the limit is raised at protocol level again, Trezor would still not be able to produce larger outputs than it could reliably spend. Once Cardano-transaction signing is refactored to be completely streamed and maximum supported transaction size is thus raised, this limit can be lifted.
a09056c
to
a006e8a
Compare
Merged via trezor#1606. |
Closes #59