Wallet does not properly reflect the decimals of FT in the post conditions correctly

So in our app https://mia.derupt.io Users can interact with the Derupt smart contract. When doing so they are supposed to be transferring exactly 100 MIA per action. (when creating a New Chime, Liking an existing Chime, or Disliking an existing Chime.)

When clicking a button to invoke the action and thus present the Hiro Web Wallet popup window, it will show 100 MIA to be transferred as expected. However when viewing the transaction on the explorer it shows only the 0.0001 MIA is the post condition amount.

No matter what, we can’t seem to get the Hiro Web Wallet popup window and the actual amount per the explorer to both be indicative of 100 MIA.

In our source code we set my amount with new BigNum(100000000); The transaction per the Explorer settles correctly, eg 100 MIA is transferred as intended. HOWEVER during this instance the Hiro window says the user is its going to xfer 100000000 MIA instead. Which most def will create cause for pause as a user.

The best we can tell is that the Hiro Web Wallet does not properly reflect the decimals of FT in the post conditions correctly during the confirmation popup window.

[cryptocracy]

Thanks for this report, even if it it did seem to automatically resolve itself. Is it possible that the relevant contract had been very recently deployed and the API that the wallet uses to load standardized contract data may not have loaded the decimals data in time for your initial testing? Or had the contract been deployed for awhile already?

The contract in question that I was calling is our derupt alpha version 11 contract. SP3T3JC6V4S94PPB7WFEK17863HPG3EYP6CJ65E7M.derupt-mia-alpha-v11 which was deployed over 4months ago.

[cryptocracy]

Trying to educate users about decimal precision errors outside of our control does make for a good UX, …can’t just be like “trust me bro…”