-
Notifications
You must be signed in to change notification settings - Fork 14
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
Send to self #118
Send to self #118
Conversation
Can be used to check if e.g. the firmware displays the expected confirmations to the user. Similar to BitBoxSwiss/bitbox-wallet-app@e2ef679.
Can only make use of it starting v9.22.0. The .proto messages have been pulled from https://github.com/BitBoxSwiss/bitbox02-firmware/tree/c35647384740683ab06309ff34b3395d5c026d58/messages and the .pb.go files generated from it according to this repo's README instructions. When sending coins to an address of the same keystore, but different account, you can provide the script config of the other account in the `outputScriptConfigs` and link the output to it.
Marked the wrong one as the simulator test.
Previous commit pulled in the new firmware protobuf messages, so we can add a test for it now.
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
@@ -614,6 +617,7 @@ func TestSimulatorBTCSignSilentPayment(t *testing.T) { | |||
Keypath: accountKeypath, | |||
}, | |||
}, | |||
nil, |
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.
nit (here and in some other file too): The BTCSign func signature will only be changed in the next commit. Probably it isn't worth the time needed to fix, tho.
No description provided.