NEAR amounts formatting for corner cases about near-api-js HOT 4 CLOSED

Looks like we have a flexible way to format N amount here:
https://github.com/near/near-api-js/blob/master/src/utils/format.ts
@frol if you feel like we need something more specific - feel free to reopen this issue.

from near-api-js.

• We need to design how this shows up in UI
  @frol do you mind providing some specific requirements for near-api-js?

from near-api-js.

The main requirement is to display any amounts of NEAR in a human-readable format no matter how small or how huge the value is, we should just use all the metric prefixes, so the number is always less than 1000 and greater or equal than 1:

• 1 NEAR (N)
• 999.99 milliNEAR (mN)
• 1 yoctoNEAR (yN)
• 999 yoctoNEAR (yN)
• 1 zeptoNEAR (zN) [1000 yoctoNEAR]
• 1 kiloNEAR (kN) [1000 NEAR]

We should not round the amounts up, so 9,999,999,999 yN should be 9.99 femtoNEAR, thus we need to indicate that there is some more tokens, e.g. 9.99+ fN or 9.99~ fN.

In Explorer, we display the balances, transfers, and fees, so the amounts of tokens we need to display can be both huge and small.

from near-api-js.

The main requirement is to display any amounts of NEAR in a human-readable format

As far as user interfaces go (wallet, shell, explorer, etc) i suggest we round things off to simple values of NEAR because that's what humans are expecting (you have ~$1, not $1.00000000001). The API should surface the exact number along with a human readable value. The UI can show the human readable value with the exact number showing up as a tooltip (or similar hidden-before-reveal container)

from near-api-js.