-
Notifications
You must be signed in to change notification settings - Fork 49
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
Run the emulator from a snapshot of Testnet or Mainnet #26
Comments
I think what's required to make this work is an AN function to read individual register keys at a specific block height. Then, the emulator's storage layer would transparently fetch the registers from another AN (e.g. testnet), and store the results locally. Basically, |
@turbolent sounds like this might take a while to implement? What about a set of scripts that automate deploying some of the contracts on the emulator, in the meantime? |
During an internal sync on how to tackle this, two ideas emerged:
|
Closing in favour of buildathlon task. |
I'm curious... how does launching a development wallet help with this issue? I'm a bit new to Flow, so I don't get what scenarios having a FCL development wallet would help! |
Issue To Be Solved
Some applications will want to build on top of other applications already deployed on Flow.
This is difficult, given currently there is no way to simulate live network contracts and their state besides manually deploying those contracts on the Emulator, and generating interactions to arrive at the desired starting state.
(Optional): Suggest A Solution
Ability to load a slice of time/block delineated protocol state (Testnet or Mainnet) into the Emulator using a cli command.
The text was updated successfully, but these errors were encountered: