Skip to content

Latest commit

 

History

History
executable file
·
46 lines (32 loc) · 2.47 KB

kip_11.md

File metadata and controls

executable file
·
46 lines (32 loc) · 2.47 KB

⏎ KIP_11

Token Balances

Users of the Kira Network need ability to preview their token balances, there can be many different tokens that users can hold in their wallet.

Balances query of the Bank module can be used to fetch information about available account balances of the user. Users are identified by their public key, e.g. kira1ufak8sc7g6w7pnlmalq9adqmj7cktcrk073ctz

Token balances of the user can originate from different networks such as Kira Hub or Kira Zones. Independent networks are usually identified by different network ID's and for that reason network origin should be clear for the user. To discover network identifier (e.g. kira-1) a node_info endpoint can be used.

Token Balances

User interface must contain a list of token balances and incorporate following information

  • Graphical Symbol
  • Asset Name
  • Ticker
  • Amount (Available Balance)
  • Denomination
  • Decimals

By default list should be ordered by the amount in descending order and only contain assets that have non zero amount. Ideally it should be possible to toggle ordering of the list based on the amount and asset name.

In the Proof of Concept (PoC) we will only have access to Denomination and Amount, for this reason we need to store information about tokens such as icon within the state of the user interface as URL link to the external resource.

List of tokens and their detailed information that will be available in the PoC:

Name        | Ticker | Denom | Decimals
------------|--------|-------|---------
Kira        | KEX    | ukex  | 6
Bitcoin     | BTC    | ubtc  | 6
Cosmos      | ATOM   | uatom | 6
Sentinel    | SENT   | usent | 6
Ethereum    | ETH    | ueth  | 6
e-money USD | eUSD   | ueusd | 6
e-money EUR | eEUR   | ueeur | 6

Deposit Address

KEX token balance should be presented as first within the token balances table right below the network id and "deposit address" of the user along the gravatar to ensure that users can easily identify their account address and deposit tokens.

It would be ideal to incorporate a one click copy button and QR code view. The gravatar could be used as the the copy button.

Transactions

Application should also display a table informing the user about all deposit transactions relevant to the current account along their timestamps & hashes. Such transactions can be queried using /txs endpoint.