-
Notifications
You must be signed in to change notification settings - Fork 6
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 key_version to sign call #4
Conversation
Thanks for this! My understanding is that, for now, there is only one key version. Since we are currently completely reworking the key management system, would it be workable to just... hardcode the key version in the MPC contract |
Yea that would make the changes here much less invasive. Also what do you think about me splitting the PR into:
|
Ok, so I hard coded the |
06318c0
to
75414cd
Compare
75414cd
to
46bd0cf
Compare
I split the PR into two. The test fixing should be merged first so I can baser this on there and test the real changes. |
3c72a0d
to
76af6bb
Compare
76af6bb
to
5c539c6
Compare
Looks awesome, thanks! |
If approved, this PR closes #3.
The
key_version
field was made mandatory on the MPC-recovery contract (cf near/mpc#509). So now this contract needs to pass along key version.It was suggested to simply hard code the value in the call-site, but we also had to update function signatures.Note that we also fixed some unrelated broken tests and the changes have been made of two commits (for easier reviewing).
I would also be willing to add a CI file to this project (in a follow up PR)
cc @encody