-
Notifications
You must be signed in to change notification settings - Fork 5
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
Use logic from commons #264
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.
Minor suggestions other than LGTM.
signedDatas: Record<BeaconId, SignedData>; | ||
signedApiUrls: Record<ChainId, Record<ProviderName, SignedApiUrl[]>>; | ||
derivedSponsorWallets: Record<string /* dAPI name or data feed ID */, Hex /* Private key */>; | ||
signedDatas: Record<Hex /* Beacon ID */, SignedData>; |
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.
Keccak256Hash for beacon Ids?
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.
TBH I am not a great fan of that type. It's quite verbose to read/type and I don't see the benefit compared to Hex
. I'd just stick with Hex
unless there is a better reason for swithcing.
Also, TS will treat the Hex
and Keccak256Hash
as the same - so in the future if these are mixed it may cause unnecessary confusion.
Closes #250
Rationale
While implementing the issue I realised there is some more code that should be reused from commons. Each commit focuses on a particular feature implemented in commons.