Hardforking evmos to cronos

[zenodeapp]

Hi, I was wondering if it's possible to perform a hard fork at a specific height to cronos. I managed to get this to work by setting a specific halt-height in my app.toml file of the evmos binary, installing the cronos binary after it halted and allowing it to continue.

I wonder if this would cause issues with older transactions/account balances etc. I'll test this out soon, though wanted to ask if this approach is somewhat valid since I was looking at the Cronos docs and saw that you guys perform hard forks more often (https://docs.cronos.org/for-node-hosts/running-nodes/cronos-mainnet#step-0-notes-on-huygen-network-upgrade).

And if this approach is okay, could this process also be automated via, let's say, migration/upgrade handlers put in place in the app.go file of the evmos binary?

The idea is to not jump to a new chain, but rather continue a running evmos forked chain as a cronos fork.

---

I'm still learning and have nearly scratched the surface of the inner workings of cosmos chains, so it would be great if someone could give some pointers or directions. And if this approach isn't going to work out, how should I tackle the issue?

[yihuang]

you just need to handle the state migration in upgrade handler, otherwise, it should work just like the other upgrades(hard-forks).

For how cosmos chains handling upgrades(hard-forks) in general, you can check the doc of upgrade module

[zenodeapp]

Just one final question:
How would I know what I should set as BaseFee, MinGasPrice, Elasticity, etc?

The chain's coin will be in 18 decimals (so: sdk.DefaultPowerReduction = sdk.NewIntFromUint64(1000000000000000000))

		params := app.FeeMarketKeeper.GetParams(ctx)
		params.BaseFeeChangeDenominator = 300
		params.ElasticityMultiplier = 4
		params.BaseFee = sdk.NewInt(10000000000000)
		params.MinGasPrice = sdk.NewDec(10000000000000)
		app.FeeMarketKeeper.SetParams(ctx, params)

I'm getting a gas to suggest must be positive error and I got a feeling this is caused by decimals. Cronos was how many decimals?

[zenodeapp]

Hmm interesting, this error appeared when I had Rosetta turned on (on v1.0.14). Now it's gone when I turn that off.

https://github.com/cosmos/rosetta/blob/main/config.go#L130-L132.

[yihuang]

Cronos was how many decimals?

cro has 18 decimals on cronos.

[zenodeapp]

Hi @yihuang, I've been creating scripts and writing documentations to make the onboarding happen more swiftly. The code itself is somewhat ready, but just need to fix some things (like gas configurations, which I have to discuss more with the community, validators and devs).

I just have a couple questions, which are more so related to making it ready for release and that you perhaps know a lot more about:

• Is it wise to edit the go.mod file and relink everything to our own repo instead of the crypto-org-chain? And how would this work with different branches? (see repo: genesis-crypto for a bit more context). Would I also have to edit individual files to achieve this?
• The releases you guys make for multiple architectures, do you use the release-dry-run script for this? I'm atm building via that, though not sure if that's the actual approach. Takes quite some time also (the release-dry-run command in the Makefile is what I ran, which let me install nix and also configure this: error: experimental Nix feature 'nix-command' is disabled; use '--extra-experimental-features nix-command' to override srid/emanote#300 (comment)). Unsure if I'm going at it the right way. It's still building as I'm typing this, so can't conclude what it's exactly creating.

Trial and error can be fun, but could also take a lot more time and is more prone to errors 😣!

[zenodeapp]

Alright hehe, figured both out. Just don't have a Darwin-based system to create such releases. Next prob to deal with :)...