-
Notifications
You must be signed in to change notification settings - Fork 568
Start other network without forking #293
Comments
how about approach 1, |
with approach 2, we would be more clear on what changes ethermint does on top of cosmos-sdk standard scaffolding, currently ethermint scaffolding is significantly different from cosmos-sdk one, I'm not sure which part is necessary which part is accidental. With this approach we can also do our own customization, for example add other native modules. Actually I'd like to try approach 2, and record the change list we have to do for ethermint to run. |
what are the chain parameters that you would like to change? |
Normally just these things https://github.com/tharsis/ethermint/blob/main/app/app.go#L109:
But for the testnet, we decide not change, the decision for the mainnet is not made yet. |
but you can change those by defining them in your |
Do you mean embed the Another issue is the cli commands is defined in main package, which seems to be not importable. |
Proposal: Run other networks without forking
Current behavior: Several chain parameters are static constants, not easy to change if not fork or significant copy-paste code.
Desired behavior: easy to start another network by import ethermint as a module
Use case: start other network with ethermint codebase.
Approach 1
New network re-use the whole ethermint scaffolding, just make some constants customizable, mainly these things.
Approach 2
New network start with cosmos-sdk simapp standard scaffolding, possibly with it's own customization, only add necessary stuff for ethermint to run, mainly:
The text was updated successfully, but these errors were encountered: