tests, trezor: Assert scriptPubKey failure for Trezor in test_big_tx #580
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Soon there will be a security tightening in
Trezor
making sure that device will refuse to sign a transaction trying to spend inputs that do not belong to the wallet (thescriptPubKey
of the input does not correspond to private keys in the wallet).Connected PR, that will (most probably) merge these changes into
master
- trezor/trezor-firmware#2081.Making appropriate changes in
test_big_tx
testcase, that is generating inputs that are not spendable by Trezor's private keys. (Seems that could be the same case as withcoldcard
?)To still test Trezor's capability of signing big transaction, we might create inputs corresponding to slip-14 standard, which the wallet (inputted with
all all all...
seed) will be able to sign. That is up to discussion (we could supply the test vectors from our tests).