-
Notifications
You must be signed in to change notification settings - Fork 214
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
chore(a3p): setup the oracle and push price for ATOM and stATOM at use
phase of f:replace-price-feeds
#10296
Conversation
Deploying agoric-sdk with Cloudflare Pages
|
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.
I think this will be unnecessary once #10317 is approved and merged.
Hey @Chris-Hibbert , I cannot see where the oracles are registered and a quote is produced durably in #10317. Could you elaborate on how this PR will be unnecessary? I can see that |
I thought we had already set up a price push in the use phase of |
a4c52d1
to
d59c30e
Compare
d59c30e
to
573c565
Compare
573c565
to
8d45260
Compare
closes: https://github.com/Agoric/BytePitchPartnerEng/issues/26
refs: https://github.com/Agoric/BytePitchPartnerEng/issues/22
Description
This PR introduces a new script,
verifyPushedPrice
, which is executed during theuse
phase of then:upgrade-next
proposal.The purpose of this script is to set up the oracle and push an initial price for key brands such as Atom and stAtom. This functionality ensures that a price quote is available for the subsequent proposals and acceptance tests.
Security Considerations
Scaling Considerations
Documentation Considerations
Testing Considerations
The existing test file,
priceFeedUpdate.test.js
, has been updated to account for the new price feed calls made during the use phase, as well as take advantage of the new helper functions built.Upgrade Considerations