Measure allocations in priceFeeds #9867
Closed
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
replace scaledPriceAuthority
This PR had been trying to add stTIA, stOSMO and stkATOM to the list of brands in A3P, to match those in mainNet, but that was a mistake. This drops those. It was previously adding priceFeeds, but not scaledPriceAuthorities.
yarn build -m upgrade-next yarn test -m upgrade-next grep log for "SURVEY". Feed those rows into a spreadsheet. use INTERESTING_VATS in upgradeVaults.test.js to label the columns. The first column is 'kernel'
Chris-Hibbert
force-pushed
the
9584-upgradeVaults
branch
2 times, most recently
from
e69fe85 to
659c016
Compare
|
See #9595 |
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.
closes: #9595
Description
Tools for measuring allocations (in A3P) in the pricefeeds as upgraded by #9748.
Security Considerations
Only to be used in test environments. No direct security implications.
Scaling Considerations
Measure scaling impacts.
Documentation Considerations
None.
Testing Considerations
Runs in a test environment.
Upgrade Considerations
Yeah, it's about the consequences of upgrading.