fix: fix evm config init

[driftluo]

What this PR does / why we need it?

This PR fixes evm config init with hardfork features

What is the impact of this PR?

No Breaking Change

PR relation:

• Ref #

CI Settings

CI Usage

Tip: Check the CI you want to run below, and then comment /run-ci.

CI Switch

• Web3 Compatible Tests
• OCT 1-5 And 12-15
• OCT 6-10
• OCT 11
• OCT 16-19
• v3 Core Tests

CI Description

CI Name	Description
Web3 Compatible Test	Test the Web3 compatibility of Axon
v3 Core Test	Run the compatibility tests provided by Uniswap V3
OCT 1-5 | 6-10 | 11 | 12-15 | 16-19	Run the compatibility tests provided by OpenZeppelin

[sunchengzhu]

This commit (371579d) fixed the issue where max_contract_limit was not taking effect when starting the axon node with hardforks = []. However, the problem still persists when starting with hardforks = ["None"]. Please check. @driftluo

[sunchengzhu]

This commit (17c7a66) has been successfully verified locally. @driftluo @KaoImin
Regardless of starting the Axon node with the configuration hardforks = [] or hardforks = ["None"], attempting to deploy a contract that exceeds the max_contract_limit size will result in the following error:

jsonRpcResponse: {
  jsonrpc: '2.0',
  error: {
    code: -49998,
    message: 'CKB-VM error execution reverted: ',
    data: 'CreateContractLimit'
  },
  id: 2
}

[yangby-cryptape]

jsonRpcResponse: {
  jsonrpc: '2.0',
  error: {
    code: -49998,
    message: 'CKB-VM error execution reverted: ',
    data: 'CreateContractLimit'
  },
  id: 2
}

Has nothing to do with the current PR.
Not issue of current PR, it's an already existed issue.

I have already point that in #1457 but be ingored: Why the error message is related to CKB-VM?
I tried some other EVM contracts which must be failed, and they could got the same messages sometimes.

[driftluo]

I have already point that in #1457 but be ingored: Why the error message is related to CKB-VM? I tried some other EVM contracts which must be failed, and they could got the same messages sometimes.

https://github.com/axonweb3/axon/blob/main/core/api/src/jsonrpc/error.rs#L57
It should be a display problem, this is the display setting returned by rpc

[KaoImin]

I have already point that in #1457 but be ingored: Why the error message is related to CKB-VM? I tried some other EVM contracts which must be failed, and they could got the same messages sometimes.

main/core/api/src/jsonrpc/error.rs#L57 It should be a display problem, this is the display setting returned by rpc

axon/core/api/src/jsonrpc/error.rs

Lines 57 to 58 in a2d8e04

	#[display(fmt = "CKB-VM error {}", "decode_revert_msg(&_0.ret)")]
	VM(TxResp),

The error display should be changed as following:

    #[display(fmt = "EVM error {}", "decode_revert_msg(&_0.ret)")] 
    EVM(TxResp), 

[github-actions]

CI tests run on commit:

• commit id: 5ba15fe

CI test list:

• Web3 Compatible Tests

Please check ci test results later.

[github-actions]

CI tests run on commit:

• commit id: fe64e40

CI test list:

• Web3 Compatible Tests

Please check ci test results later.

[github-actions]

CI tests run on commit:

• commit id: fe64e40

CI test list:

• Web3 Compatible Tests

Please check ci test results later.

[sunchengzhu]

The error message returned by commit (fe64e40) is as follows:

jsonRpcResponse: {
  jsonrpc: '2.0',
  error: {
    code: -49998,
    message: 'EVM error execution reverted: ',
    data: 'CreateContractLimit'
  },
  id: 2
}

[Flouse]

Is it better to use fn default_max_contract_limit instead of hardcoding 0x6000?