-
Notifications
You must be signed in to change notification settings - Fork 20
ethereum utility library #2404
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
ethereum utility library #2404
Conversation
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.
LGTM, but I mostly reviewed only the .github/workflows/
changes. You might want to ask someone else also to review.
verifyingContract: '0xCcCCccccCCCCcCCCCCCcCcCccCcCCCcCcccccccC', | ||
}; | ||
|
||
export const ADD_PROVIDER_DEFINITION = { |
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.
Again, I don't think so, but I wonder if we need to version these in any way? I guess we can later add _V2
on the end without issue.
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 would say, any structs that already are at "V2" should get _V2
appended to the const name 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.
If it the only version based on our existing convention I didn't add any version but all versions > 1
should have the version in the name unless there's been a mistake (just like what Joe suggested)
@@ -97,50 +97,6 @@ export function signPayload(keys: KeyringPair, data: Codec): MultiSignatureType | |||
} | |||
} | |||
|
|||
/** |
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.
Yay!
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.
A few questions, but nothing blocking. Good work.
@@ -0,0 +1 @@ | |||
nodejs 20.12.2 |
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: e2e tests are using 22.12.0.
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.
correct, but I think since we have other clients that are using node 20 it made sense to use the older version since this is going to be a dependency for those.
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.
+1
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.
👍 great!
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.
- Read through changes.
- Nice work!
🚢 it!
Goal
The goal of this PR is to create a ethereum utility library which can help us dealing with ethereum addresses and signatures and etc.
Closes #2281
What is added?
Checklist