9063 localChain metadata by agoricNames #9464
Merged
Conversation
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
Deploying agoric-sdk with
|
| Latest commit: |
3cab037
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://4dcb4feb.agoric-sdk.pages.dev |
| Branch Preview URL: | https://9063-agoricinfo.agoric-sdk.pages.dev |
dckc
approved these changes
Jun 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
refs: #9063
Description
More progress on #9063
Following up on #9459
Next I think I'll set up a tool to grab the chain-registry info for the chains in the checklist and bring them into agoricNames
In parallel, @dckc is populating agoricNames with the chain connection info which can be appended to even after the chain (graph node) is defined.
Security Considerations
no changes
Scaling Considerations
no changes
Documentation Considerations
no need
Testing Considerations
CI, including A3P proposal update
Upgrade Considerations
no yet deployed