# Accounts

This document describes the in-built accounts system of Evmos.

# Pre-requisite Readings

# Evmos Accounts

Evmos defines its own custom Account type that uses Ethereum's ECDSA secp256k1 curve for keys. This satisfies the EIP84 (opens new window) for full BIP44 (opens new window) paths. The root HD path for Evmos-based accounts is m/44'/60'/0'/0.

Copy // EthAccount implements the authtypes.AccountI interface and embeds an // authtypes.BaseAccount type. It is compatible with the auth AccountKeeper. type EthAccount struct { *types.BaseAccount `protobuf:"bytes,1,opt,name=base_account,json=baseAccount,proto3,embedded=base_account" json:"base_account,omitempty" yaml:"base_account"` CodeHash string `protobuf:"bytes,2,opt,name=code_hash,json=codeHash,proto3" json:"code_hash,omitempty" yaml:"code_hash"` }

# Addresses and Public Keys

BIP-0173 (opens new window) defines a new format for segregated witness output addresses that contains a human-readable part that identifies the Bech32 usage. Evmos uses the following HRP (human readable prefix) as the base HRP:

Network Mainnet Testnet Regtest
Evmos evmos evmos

There are 3 main types of HRP for the Addresses/PubKeys available by default on Evmos:

  • Addresses and Keys for accounts, which identify users (e.g. the sender of a message). They are derived using the eth_secp256k1 curve.
  • Addresses and Keys for validator operators, which identify the operators of validators. They are derived using the eth_secp256k1 curve.
  • Addresses and Keys for consensus nodes, which identify the validator nodes participating in consensus. They are derived using the ed25519 curve.
Address bech32 Prefix Pubkey bech32 Prefix Curve Address byte length Pubkey byte length
Accounts evmos evmospub eth_secp256k1 20 33 (compressed)
Validator Operator evmosvaloper evmosvaloperpub eth_secp256k1 20 33 (compressed)
Consensus Nodes evmosvalcons evmosvalconspub ed25519 20 32

# Address formats for clients

EthAccount can be represented in both Bech32 (opens new window) (evmos1...) and hex (0x...) formats 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 Cosmos sdk.AccAddress.

  • Address (Bech32): evmos1z3t55m0l9h0eupuz3dp5t5cypyv674jj7mz2jw
  • Address (EIP55 (opens new window) Hex): 0x91defC7fE5603DFA8CC9B655cF5772459BF10c6f
  • Compressed Public Key: {"@type":"/ethermint.crypto.v1.ethsecp256k1.PubKey","key":"AsV5oddeB+hkByIJo/4lZiVUgXTzNfBPKC73cZ4K1YD2"}

# Address conversion

The evmosd debug addr <address> can be used to convert an address between hex and bech32 formats. For example:

# Key output

The Cosmos SDK Keyring output (i.e evmosd keys) only supports addresses and public keys in Bech32 format.

We can use the keys show command of evmosd with the flag --bech <type> (acc|val|cons) to obtain the addresses and keys as mentioned above,

# Querying an Account

You can query an account address using the CLI, gRPC or

# Command Line Interface

Copy # NOTE: the --output (-o) flag will define the output format in JSON or YAML (text) evmosd q auth account $(evmosd keys show mykey -a) -o text | '@type': /ethermint.types.v1.EthAccount base_account: account_number: "0" address: evmos1z3t55m0l9h0eupuz3dp5t5cypyv674jj7mz2jw pub_key: '@type': /ethermint.crypto.v1.ethsecp256k1.PubKey key: AsV5oddeB+hkByIJo/4lZiVUgXTzNfBPKC73cZ4K1YD2 sequence: "1" code_hash: 0xc5d2460186f7233c927e7db2dcc703c0e500b653ca82273b7bfad8045d85a470

# Cosmos gRPC and REST

Copy # GET /cosmos/auth/v1beta1/accounts/{address} curl -X GET "http://localhost:10337/cosmos/auth/v1beta1/accounts/evmos14au322k9munkmx5wrchz9q30juf5wjgz2cfqku" -H "accept: application/json"

# JSON-RPC

To retrieve the Ethereum hex address using Web3, use the JSON-RPC eth_accounts or personal_listAccounts endpoints:

Copy # query against a local node curl -X POST --data '{"jsonrpc":"2.0","method":"eth_accounts","params":[],"id":1}' -H "Content-Type: application/json" http://localhost:8545 curl -X POST --data '{"jsonrpc":"2.0","method":"personal_listAccounts","params":[],"id":1}' -H "Content-Type: application/json" http://localhost:8545