Skip to content
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: pass options to secp256k1 signBuffer #71

Merged
merged 7 commits into from
Mar 1, 2024

Conversation

feri42
Copy link
Contributor

@feri42 feri42 commented Feb 28, 2024

For signing ETH transactions we need to pass the canonical option to ec.sign. Also, using the DER format of the signature can be quite challenging as there is no simple function to pick it apart. With this change we can get the raw signature. It would be better if signBuffer didn't return the DER encoded value at all.

Fixtures for the new test were created using the ethereumjs library.

diegomura
diegomura previously approved these changes Feb 28, 2024
Copy link
Contributor

@diegomura diegomura left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK

kewde
kewde previously approved these changes Feb 29, 2024
Copy link
Contributor

@kewde kewde left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK - but I would prefer we restrict ecOptions to canonical unless we need more.

Copy link
Contributor

@kewde kewde left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK

@feri42
Copy link
Contributor Author

feri42 commented Feb 29, 2024

Anything else here?

Copy link
Contributor

@sparten11740 sparten11740 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK

Copy link

@maksim-iv-exodus maksim-iv-exodus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK

@mvayngrib mvayngrib merged commit a951bbd into master Mar 1, 2024
7 checks passed
@mvayngrib mvayngrib deleted the f/pass-options-tosign-buffer branch March 1, 2024 13:35
@mvayngrib
Copy link
Collaborator

@feri42 merged, but the multi-seed keychain is still being integrated all over the place. Do you want this also backported to the single-seed keychain for now?

@feri42
Copy link
Contributor Author

feri42 commented Mar 1, 2024

@mvayngrib , yes definitely. Where is the single-seed keychain located? I need to import this into the platforms to finish the whole POC.

@sparten11740
Copy link
Contributor

Where is the single-seed keychain located?

in a commit from ages long bygone

@mvayngrib
Copy link
Collaborator

@feri42 it's keychain 5.x, i'll see if i can create a branch and release from there

@feri42
Copy link
Contributor Author

feri42 commented Mar 1, 2024

Mobile has keychain 4.x. Seeing this is 5.x, will it be a reasonable effort to bump keychain there?

@mvayngrib
Copy link
Collaborator

shouldn't be, @sparten11740 can u grab bumping keychain on mobile?

mvayngrib added a commit that referenced this pull request Mar 1, 2024
Co-authored-by: Ferenc Kiraly <feri@feridot.com>
@mvayngrib
Copy link
Collaborator

backported + released to @exodus/keychain@5.1.0

r4vn pushed a commit that referenced this pull request Apr 2, 2024
Co-authored-by: Ferenc Kiraly <feri@feridot.com>
r4vn added a commit that referenced this pull request Apr 2, 2024
Co-authored-by: Mark Vayngrib <mvayngrib@gmail.com>
Co-authored-by: Ferenc Kiraly <feri@feridot.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants