The public key that was first used to create the account. You can replace the key used for signing the account’s transactions with a different public key, but the original account ID will always be used to identify the account.
The number of HCXs held by the account. The balance is denominated in 1/10,000,000th of a HCX, the smallest divisible unit of a HCX.
The current transaction sequence number of the account. This number starts equal to the ledger number at which the account was created.
Number of other entries the account owns. This number is used to calculate the account’s minimum balance.
(optional) Account designated to receive inflation. Every account can vote to send inflation to a destination account.
Currently there are three flags, used by issuers of assets.
A domain name that can optionally be added to the account. Clients can look up a HCNet.toml from this domain. This should be in the format of a fully qualified domain name such as example.com.
The mapping protocol can use the home domain to look up more details about a transaction’s memo or address details about an account. For more on mapping, see the Mapping guide.
Operations have varying levels of access. This field specifies thresholds for low-, medium-, and high-access levels, as well as the weight of the master key. For more info, see multi-sig.
Used for multi-sig. This field lists other public keys and their weights, which can be used to authorize transactions for this account.
Starting in protocol version 10, each account also tracks its HCX liabilities. Buying liabilities equal the total amount of HCX offered to buy aggregated over all offers owned by this account, and selling liabilities equal the total amount of HCX offered to sell aggregated over all offers owned by this account. An account must always have balance sufficiently above the minimum reserve to satisfy its HCX selling liabilities, and a balance sufficiently below the maximum to accommodate its HCX buying liabilities.