-
Notifications
You must be signed in to change notification settings - Fork 17
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
feat: add limited key option #150
Conversation
19fd627
to
395e0b1
Compare
395e0b1
to
6e44925
Compare
CI is failing to load relayer docker image. Looking into that. |
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.
Bar one comment LGTM
.into_iter() | ||
.find(|ak| ak.public_key.to_string() != user_public_key) | ||
.find(|ak| { |
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.
I'm a bit confused by this, why are we searching for both the FA and the LA key, then assuming we found the FA key?
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.
Because we are creating an account with FA Key A and LA Key B. FA Key C (recovery) is added on the serverside.
So, if we will get all 3 keys, remove FA A and LA B, it should be FA C.
* chore: clarify deploy guide (#151) * chore: pull relayer image from Github Container Registry (#152) * chore: fix logging (#154) * feat: add limited key option (#150) * add limited key support --------- Co-authored-by: David Millar-Durrant <dmillardurrant@gmail.com> Co-authored-by: Serhii Volovyk <SergeyVolovyk@gmail.com> --------- Co-authored-by: Daniyar Itegulov <ditegulov@gmail.com> Co-authored-by: David Millar-Durrant <dmillardurrant@gmail.com>
No description provided.