Some modules have their own module account. Think of this as a wallet that can only be controlled by that module. Below is a table of modules, their respective wallet addresses and permissions:
List of Module Accounts
burnerpermission means this account has the permission to burn or destroy tokens.
minterpermission means this account has permission to mint or create new tokens.
stakingpermission means this account has permission to stake tokens on behalf of its owner.
IBC Module Accounts
Additionally, there are module accounts associated with IBC transfers.
For each IBC connection, there's an account of type
ModuleAccount used to escrow the transferred coins when Evmos is the source chain.
Their addresses are derived using the first 20 bytes of the SHA256 checksum of the account name and following the format as outlined in ADR 028:
// accountName is composed by the current version the IBC transfer module supports (in this case, ics20-1), the portID (transfer) and the channelID
accountName := Version + "\0" + portID + "/" + channelID
addr := sha256.Sum256(accountName)[:20]
// example for channel-0
addr := sha256.Sum256("ics20-1\0transfer/channel-0")[:20]
This can be calculated with the
GetEscrowAccount function on IBC-go.
Note: These escrow accounts are not listed when performing the query:
evmosd q auth module-accounts
This happens because the
GetModuleAccount function used on the query considers only the accounts on the
permAddrs map of the
This address map is set at compile time and cannot be changed on runtime.