Skip to content
This repository has been archived by the owner on Apr 4, 2024. It is now read-only.

fix order of eip activation #288

Merged
merged 1 commit into from
Jul 14, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion x/evm/types/params.go
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,11 @@ var (
ParamStoreKeyEnableCall = []byte("EnableCall")
ParamStoreKeyExtraEIPs = []byte("EnableExtraEIPs")
ParamStoreKeyChainConfig = []byte("ChainConfig")

// AvailableExtraEIPs define the list of all EIPs that can be enabled by the EVM interpreter. These EIPs are applied in
// order and can override the instruction sets from the latest hard fork enabled by the ChainConfig. For more info
// check: https://github.com/ethereum/go-ethereum/blob/v1.10.4/core/vm/interpreter.go#L122
AvailableExtraEIPs = []int64{1344, 1884, 2200, 2929}
)

// ParamKeyTable returns the parameter key table.
Expand All @@ -43,13 +48,14 @@ func NewParams(evmDenom string, enableCreate, enableCall bool, config ChainConfi
}

// DefaultParams returns default evm parameters
// ExtraEIPs is empty to prevent overriding the latest hard fork instruction set
func DefaultParams() Params {
return Params{
EvmDenom: DefaultEVMDenom,
EnableCreate: true,
EnableCall: true,
ExtraEIPs: []int64{2929, 2200, 1884, 1344},
ChainConfig: DefaultChainConfig(),
ExtraEIPs: nil,
}
}

Expand Down