Teleport uses public (hex) key for destination instead of address #11910
Description
When teleporting assets (from AH back to RC) the call constructed by the app uses the public key instead of the address for the destination:
This makes the verification of the call difficult, especially on a Ledger device.
Given the address format is universal now, and especially between RC and AH, is there a reason not to use the address instead?