Federico Kunze Küllmer f7bcc8d12e

* docs: update

* update +

* txs

* update docs

* more docs

* spec update

* doc fixes

2021-08-03 17:35:31 +00:00

2.2 KiB

Raw Blame History

State

The x/evm module keeps the following objects in state:

	Key	Value
Block Height	`[]byte{1} + []byte(block.Hash)`	`BigEndian(block.Height)`
Bloom	`[]byte{2} + []byte(block.Height)`	`[]byte(Bloom)`
Tx Logs	`[]byte{3} + []byte(tx.Hash)`	`amino([]Log)`
Account Code	`[]byte{4} + []byte(code.Hash)`	`[]byte(Code)`
Account Storage	`[]byte{5} + []byte(address) + []byte(state.Key)`	`[]byte(state.Value)`
Chain Config	`[]byte{6}`	`amino(ChainConfig)`

`CommitStateDB`

StateDBs within the ethereum protocol are used to store anything within the IAVL tree. StateDBs take care of caching and storing nested states. It's the general query interface to retrieve contracts and accounts

The Ethermint CommitStateDB is a concrete type that implements the EVM StateDB interface. Instead of using a trie and database for querying and persistence, the CommitStateDB uses KVStores (key-value stores) and Cosmos SDK Keepers to facilitate state transitions.

The CommitStateDB contains a store key that allows the DB to write to a concrete subtree of the multistore that is only accessible to the EVM module.

+++ https://github.com/tharsis/ethermint/blob/v0.3.1/x/evm/types/statedb.go#L33-L85

The functionalities provided by the Ethermint StateDB are:

CRUD of stateObjects and accounts:
- Balance
- Code
- Nonce
- State
EVM module parameter getter and setter
State transition logic
- Preparation: transaction index and hash, block hash
CRUD of transaction logs
Aggregate queries
Snapshot state
- Identify current state with a revision
- Revert state to a given revision
State transition and persistence
- Preparation: tx and block context
- Commit state objects
- Finalise state objects
- Export state for upgrades
Auxiliary functions
- Copy state
- Reset state

2.2 KiB Raw Blame History

State

CommitStateDB

2.2 KiB

Raw Blame History

`CommitStateDB`