Skip to content
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

Set up mainfork environment with U16 and Oracles #9866

Closed
Tracked by #9584
Chris-Hibbert opened this issue Aug 8, 2024 · 2 comments
Closed
Tracked by #9584

Set up mainfork environment with U16 and Oracles #9866

Chris-Hibbert opened this issue Aug 8, 2024 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@Chris-Hibbert
Copy link
Contributor

What is the Problem Being Solved?

In order to ensure that the coreEval that upgrades vaults, auctions, and priceFeeds coordinates correctly with the third-party oracles, we need a realistic test environment to work in.

Description of the Design

The proposal is to create a mainFork instance (updated to upgrade 16, and set up a variation of the oracle scripts that will allow us to control the price feeds and observe the coordination between the oracles middleware and the upgraded priceFeeds.

SimplyStaking has provided instructions for setting up an oracle, but we'll need to build a test fixture that allows us to programmatically (or via a cyclic script) control the price feed. The usual path is Middleware -> CL node -> Adapter -> CL Node -> Middleware -> Chain. We want to test how CL Node -> Middleware -> Chain acts during upgrade, so we probably want to replace the adapter so we're not tied to Simply's oracle network. We may want to induce price drops to cause liquidations, so we need control of the price sources.

Security Considerations

It's a test environment, so it doesn't directly impact the chain.

Scaling Considerations

None

Test Plan

Unneeded.

Upgrade Considerations

Will be used for testing upgrade, but doesn't itself need to be upgradeable.

@LuqiPan
Copy link
Contributor

LuqiPan commented Aug 13, 2024

We're gonna conduct this test on devnet instead of on mainfork

@LuqiPan LuqiPan assigned Chris-Hibbert and unassigned LuqiPan Aug 13, 2024
@Chris-Hibbert
Copy link
Contributor Author

superseded by #9886

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants