extra eips param

x/evm/spec/04_messages.md

@@ -9,9 +9,9 @@ order: 4
 An EVM state transition can be achieved by using the `MsgEthereumTx`. This message encapsulates an
 Ethereum transaction as an SDK message and contains the necessary transaction data fields.
 
-One remark about the `MsgEthereumTx` is that it implements both the [`sdk.Msg`](https://github.com/cosmos/cosmos-sdk/blob/v0.39.1/types/tx_msg.go#L7-L29) and [`sdk.Tx`](https://github.com/cosmos/cosmos-sdk/blob/v0.39.1/types/tx_msg.go#L33-L41)
+One remark about the `MsgEthereumTx` is that it implements both the [`sdk.Msg`](https://github.com/cosmos/cosmos-sdk/blob/v0.39.2/types/tx_msg.go#L7-L29) and [`sdk.Tx`](https://github.com/cosmos/cosmos-sdk/blob/v0.39.2/types/tx_msg.go#L33-L41)
 interfaces (generally SDK messages only implement the former, while the latter is a group of
-messages bundled together). The reason of this, is because the `MsgEthereumTx` must not be included in a [`auth.StdTx`](https://github.com/cosmos/cosmos-sdk/blob/v0.39.1/x/auth/types/stdtx.go#L23-L30) (SDK's standard transaction type) as it performs gas and fee checks using the Ethereum logic from Geth instead of the Cosmos SDK checks done on the `auth` module `AnteHandler`.
+messages bundled together). The reason of this, is because the `MsgEthereumTx` must not be included in a [`auth.StdTx`](https://github.com/cosmos/cosmos-sdk/blob/v0.39.2/x/auth/types/stdtx.go#L23-L30) (SDK's standard transaction type) as it performs gas and fee checks using the Ethereum logic from Geth instead of the Cosmos SDK checks done on the `auth` module `AnteHandler`.
 
 +++ https://github.com/cosmos/ethermint/blob/v0.3.1/x/evm/types/msg.go#L117-L124
 

x/evm/spec/06_events.md

@@ -13,8 +13,8 @@ interface).
 
 | Type     | Attribute Key | Attribute Value |
 |----------|---------------|-----------------|
-| ethereum | amount        | {amount}        |
-| ethereum | recipient     | {eth_address}   |
-| message  | sender        | {eth_address}   |
-| message  | action        | ethereum        |
-| message  | module        | evm             |
+| ethereum | `"amount"`    | `{amount}`      |
+| ethereum | `"recipient"` | `{eth_address}` |
+| message  | `"sender"`    | `{eth_address}` |
+| message  | `"action"`    | `"ethereum"`    |
+| message  | `"module"`    | `"evm"`         |

x/evm/spec/07_params.md

@@ -8,9 +8,10 @@ The evm module contains the following parameters:
 
 | Key            | Type   | Default Value |
 |----------------|--------|---------------|
-| `EVMDenom`     | string | `aphoton`     |
+| `EVMDenom`     | string | `"aphoton"`   |
 | `EnableCreate` | bool   | `true`        |
 | `EnableCall`   | bool   | `true`        |
+| `ExtraEIPs`    | []int  | TBD           |
 
 ## EVM denom
 
@@ -19,10 +20,10 @@ gas consumption for EVM messages.
 
 The EVM Denom is used on the following cases:
 
-- `AnteHandler`: for calculating sufficient balance to pay for gas cost or transaction fees.
-- `journal`: to revert certain state executions (`balanceChange` and `suicideChange`).
-- `stateObject`: to track the `evm_denom` balance of the object account.
-- `CommitStateDB`: to update account balance from an existing state object.
+* `AnteHandler`: for calculating sufficient balance to pay for gas cost or transaction fees.
+* `journal`: to revert certain state executions (`balanceChange` and `suicideChange`).
+* `stateObject`: to track the `evm_denom` balance of the object account.
+* `CommitStateDB`: to update account balance from an existing state object.
 
 For example, on Ethereum, the `evm_denom` would be `ETH`. In the case of Ethermint, the default denomination is the atto photon.
 
@@ -39,3 +40,15 @@ parameter is disabled, it will prevent all contract creation functionality.
 
 The enable transfer toggles state transitions that use the `vm.Call` function. When the parameter is
 disabled, it will prevent transfers between accounts and executing a smart contract call.
+
+## Extra EIPs
+
+The extra EIPs parameter defines the set of activateable Ethereum Improvement Proposals ([EIPs](https://ethereum.org/en/eips/))
+on the Ethereum VM `Config` that apply custom jump tables.
+The supported activateable EIPS are:
+
+* [EIP 1344](https://eips.ethereum.org/EIPS/eip-1344)
+* [EIP 1884](https://eips.ethereum.org/EIPS/eip-1884)
+* [EIP 2200](https://eips.ethereum.org/EIPS/eip-2200)
+* [EIP 2315](https://eips.ethereum.org/EIPS/eip-2315)
+* [EIP 2929](https://eips.ethereum.org/EIPS/eip-2929)