Also, in case of the amount, the user can verify it, because it's human-readable.
Aliases r readable too.
Problem is aliases need to be looked up, and you have to be sure no one is poisoning the alias lookup with fake info (associated id). So you have to do at least 5+ lookups from different peers to be sure that the ID is correct.. (Is this correct?) - That's not very fast and you won't reach 10,000 tps (or however many you want) this way. I may be wrong.
Is this really correct? My understanding was:
- If you tell the nxwork "send X nxt to alias Y" then there is no need for anything other than the forging node to do an alias lookup; and what the forging node forges is by definition either truth or eventually discarded as a wrong fork, so zero chance of fake alias info.
- If your client is looking up up alias Y and translating it to a nxt account and then creating a transaction based on that, it's doing it wrong.
Needs network support for sending to alias, of course.