-
Notifications
You must be signed in to change notification settings - Fork 429
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
Streamline config shapes (typescript) #2214
Comments
@nambrot I think there are more contract addresses that would be good to share (e.g. ISM factories) |
Ahh good, point, any other ones? Feel free to add them to the PR, otherwise I can |
Closed
jmrossy
added a commit
that referenced
this issue
Jul 10, 2023
### Description - Refactor ChainMetadata types into new folder - Create metadata extensions for deployment artifacts, and agent config - Remove explicit ChainMetadata interface and infer from zod schema instead ### Related issues Implements new schema discussed in: - #1867 - #2203 - #2214 Fixes #2214 ### Backward compatibility **No**: users of chain metadata configs would need to slightly modify their shape (the `rpcUrl` field)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As a result from #1867, this ticket specifies the streamlining of our config shapes.
Specifically, explorer config becomes the merge of the existing
ChainMetadata
(with slightly modified keys) andHyperlaneDeploymentArtifacts
from https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/2203/files#diff-0dda34e51b45fcb259676791b216443495e465f6ec7c372fc77ec9abe9b8409aR90, and can be easily generated during a Hyperlane deploy and easily shared, and eventually able to be communicated to registries a la #2178 (instead of having to be manually constructed right now)To do this, probably take the above draft PR, and make sure that it compiles in the sdk and adjust the consumers of ChainMetadata
The text was updated successfully, but these errors were encountered: