Ceyhun Onur

My opinions: 1- we should not use lowercase for subnet and uppercase for EVM. I.e `subnet-EVM` or `subnet EVM` etc. They should both start uppercase or lowercase at the same...

Seems this is resolved.

the method name is `avm.issueTx` not `avax.issueTx`: https://docs.avax.network/apis/avalanchego/apis/x-chain/#avmissuetx

Could you enable profiling and send your results? https://docs.avax.network/build/references/command-line-interface/#continuous-profiling

You can create a key in memory (not persisted) with `staking-ephemeral-cert-enabled`, it would create a different cert in each run. Thanks for the feedback, we will look into this further....

@jummy123 Take a look at rate-limiting CLI configs: https://docs.avax.network/build/references/command-line-interface#message-rate-limiting https://docs.avax.network/build/references/command-line-interface#connection-rate-limiting

Thank you for reporting this. We will look into this.

Changes in this PR does not change any observable behavior. It just skips some additional calculation overhead before returning the error. Would you like me to add a test that...

Answered on https://github.com/ava-labs/avalanchego/issues/1147 > They recently upgraded their network with network upgrades in subnet-evm. Check their [upgrade.json ](https://github.com/ava-labs/subnet-evm/blob/master/networks/mainnet/53935/upgrade.json)file and put that into the chain configuration under `$HOME/.avalanchego/configs/chains/q2aTwKuyzgs8pynF7UXBZCU7DejbZbZ6EUyHr3JQzYgwNPUPi` I assumed you...

converting this to draft until we get a full coreth + avalanchego release