Hi!
as an additional safety feature, it would be smart to see a recipent's monKey on the transaction-confirmation screen.
This allows fast and easy comparison of the intended recipent with the actual recipent. instead of reading and comparing addresses, a quick look at the well recognizable monkey icon is enough. This can also be helpful for people suffering dyslexia and gives them more safety.
Adding this to the confirmation screen makes more sense than to the "send" screen. Malware could change the input field on click with the send button.
Would that be feasible? as far as I understand all you need to do is generate a monkey.banano.cc address from the recipient's address in the form of https://monkey.banano.cc/api/v1/monkey/ban_1fubjpwejb6tb7ju7gexp6aii9issc8cme3g9p3ipffmzq4et6ona18p1xyt?svc=kalium
I imagine this to look more or less like in this mockup https://imgur.com/a/iBBzeCo
Cheers!
Hi!
as an additional safety feature, it would be smart to see a recipent's monKey on the transaction-confirmation screen.
This allows fast and easy comparison of the intended recipent with the actual recipent. instead of reading and comparing addresses, a quick look at the well recognizable monkey icon is enough. This can also be helpful for people suffering dyslexia and gives them more safety.
Adding this to the confirmation screen makes more sense than to the "send" screen. Malware could change the input field on click with the send button.
Would that be feasible? as far as I understand all you need to do is generate a monkey.banano.cc address from the recipient's address in the form of https://monkey.banano.cc/api/v1/monkey/ban_1fubjpwejb6tb7ju7gexp6aii9issc8cme3g9p3ipffmzq4et6ona18p1xyt?svc=kalium
I imagine this to look more or less like in this mockup https://imgur.com/a/iBBzeCo
Cheers!