-
Notifications
You must be signed in to change notification settings - Fork 7
Genesis Files Default to Nothing in Emulator Initialization #35
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
Comments
@Dr-Mazen-Khaddaj> interim maintainer of Indeed as you pointed out, it is not possible actually to specify custom genesis files, as the paths are defaulted to We could have the |
As I'm going to stop working on the team maintaining |
@mmontin> Should probably be assigned to you, but I can't assign you in the corresponding field 🙃 |
@smelc That's definitely something I intend to look into, depending on the permissions I'm given regarding CNE. Once the main PR is merged (should be soon) we can collectively come up with a plan forward for all the missing features and shortcomings of CNE, including default parameters and initial emulated ledger state. At the moment, it is likely the the cost models by default as well are flawed. |
@mmontin> I can assign you now 🙃 |
Description: I've been reviewing how the emulator loads Genesis files upon start and found that it defaults to Nothing. I want to clarify if this is intentional or if there's an option to provide Genesis files explicitly. If not, is there a plan to support this functionality, especially with the upcoming Conway upgrade?
Steps to Reproduce:
main
uses the default implementation (defaultNodeServerConfig
which is set to Nothing).Expected Behavior: An explicit genesis file should be required or loaded if available.
Actual Behavior: Defaults to Nothing without indicating the need for a genesis file.
Questions:
Would you happen to know if this is the intended behavior?
How does the emulator load Genesis files upon the start?
Additional Information: This could affect configurations when simulating different blockchain states during testing or development.
The text was updated successfully, but these errors were encountered: