chore(fast-usdc): beta oracle addresses #10996
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: |
ce41d7a
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://553f6df2.agoric-sdk.pages.dev |
| Branch Preview URL: | https://dc-fu-beta.agoric-sdk.pages.dev |
and USDC-on-osmosis is not needed
turadg
approved these changes
Feb 13, 2025
| @@ -80,10 +79,11 @@ export const configurations = { | |||
| assetInfo: agoricAssetInfo, | |||
| }, | |||
| MAINNET: { | |||
| // per JVC 12 Feb 2025 | |||
- limit assetInfo in proposal to mimic rest of of test (just usdc on agoric)
0xpatrickdev
approved these changes
Feb 13, 2025
There was a problem hiding this comment.
Looks good. The current CI flake is not appearing when running locally.
Please cherry-pick 07c49fd so we also have the same assetInfo subset in multichain-testing (this is what I tested against, btw)
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: #10978
Description
Update OCW addrs
assetInfo need not vary across configurations, so no more "default".
Security Considerations
Production key management considerations apply.
Scaling Considerations
n/a
Documentation Considerations
The addresses of the operators are perhaps worth sharing in the community governance thread.
Testing Considerations
DRY out referenced to old oracle addrs in a test.
Upgrade Considerations
not yet deployed