We don't integrate some sort of CRC because of saving a tiny bit of memory in the core code and because sort-of-CRC could be done in a/the client, right?
No, because in the core and when sending across the network the transactions are already signed with the sender public key. Any corruption in the transaction content would automatically invalidate the signature.
Sounds reasonable. And what are the options for the client software for user-made input-errors?
Spontanious idea: The client software can handle "#account" and "#account"+"account alias" receiver-adresses. The second could be checked by the client before it is signed. It would be convenient and the user felt kinda save.
Mmhh, other ideas please?