This repository has been archived by the owner on Jun 17, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 272
signature/address: support for high recovery and chain IDs #290
Merged
Merged
Changes from 4 commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
0f87416
signature: add support for very high recovery IDs
jochem-brouwer db8d736
signature: add test of failing tx on YoloV3
jochem-brouwer 1c9d742
Added Buffer to BNLike type, PrefixedHexString in types, use BNLike f…
holgerd77 5c80ce8
Added BNLike chainId input and return types for ecsign, added tests
holgerd77 24279bf
Limited ecsign v return value to Buffer on extended input types, addi…
holgerd77 abe0aff
Added BNLike input type for chain IDs in toChecksumAddress() and isVa…
holgerd77 b3ba3ee
Added BNLike input type for v and chain IDs in toRpcSig() and isValid…
holgerd77 243fd47
add `toType` helper with 0x-prefix and MAX_SAFE_INTEGER checks
ryanio 059ce3b
add tests for `toType`
ryanio db4ee77
improve ecsign logic
ryanio 46415c1
dev ex: remove lint from `npm run test` and add as a separate step to ci
ryanio File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
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 assuming that originally we expected these strings to be
0x
prefixed?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.
yeah actually
PrefixedHexString
is simply a string type right now, maybe in the future typescript will give us some way to enforce that the first two characters are0x
.