Module Accounts
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
Name | Address | Permissions |
---|---|---|
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
Account Permisions
The
burner
permission means this account has the permission to burn or destroy tokens.The
minter
permission means this account has permission to mint or create new tokens.The
staking
permission means this account has permission to stake tokens on behalf of it's 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 Match 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:
This can be calculated with the GetEscrowAccount
function on IBC-go.
Note: These escrow accounts are not listed when performing the query:
This happens because the GetModuleAccount
function used on the query considers only the accounts on the permAddrs
map of the AccountKeeper
. This address map is set at compile time and cannot be changed on runtime.
Last updated