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

Separate out code for EVM network substate #152

Closed
ehildenb opened this issue Mar 11, 2018 · 0 comments
Closed

Separate out code for EVM network substate #152

ehildenb opened this issue Mar 11, 2018 · 0 comments

Comments

@ehildenb
Copy link
Member

Perhaps we could achieve cleaner separation of all the files by pulling out the subconfiguration for the network into its own file.

We would add an extra cell, networkCommands, which is used to communicate between the two configurations. It would only deal with looking up/retrieving network data. Operators like #newAccount and the like would be defined there, and the various loaders/checkers could be as well.

Long term this would help with factoring out the network semantics from the KEVM, KIELE, and KWASM semantics so that they share a modular blockchain semantics.

@dwightguth ?

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

No branches or pull requests

1 participant