This document describes the in-built accounts system of Ethermint.
# Pre-requisite Readings
# Ethermint Accounts
Ethermint defines its own custom
Account type that uses Ethereum's ECDSA secp256k1 curve for keys. This
satisfies the EIP84 for full BIP44 paths.
The root HD path for Ethermint-based accounts is
# Addresses and Public Keys
There are 3 main types of
PubKeys available by default on Ethermint:
- Addresses and Keys for accounts, which identify users (e.g. the sender of a
message). They are derived using the
- Addresses and Keys for validator operators, which identify the operators of validators. They are derived using the
- Addresses and Keys for consensus nodes, which identify the validator nodes participating in consensus. They are derived using the
|Address bech32 Prefix||Pubkey bech32 Prefix||Curve||Address byte length||Pubkey byte length|
|Accounts|| || || || |
|Validator Operator|| || || || |
|Consensus Nodes|| || || || |
# Address formats for clients
EthAccounts can be represented in both Bech32 and hex format for Ethereum's Web3 tooling compatibility.
The Bech32 format is the default format for Cosmos-SDK queries and transactions through CLI and REST
clients. The hex format on the other hand, is the Ethereum
common.Address representation of a
- Address (Bech32):
- Address (EIP55 Hex):
- Compressed Public Key (Bech32):
You can query an account address using the Cosmos CLI or REST clients:
The Cosmos SDK Keyring output (i.e
ethermintcli keys) only supports addresses and public keys in Bech32 format.
To retrieve the Ethereum hex address using Web3, use the JSON-RPC
Learn about Ethermint transactions