Perhaps - but can you clarify how this works? Does the client (or node that initially creates the transaction) lookup the alias at time of transaction to get the account ID, and then create a transaction with that account ID as recipient; or does it create a transaction with that alias as recipient (with the forging node doing the alias lookup when the block is forged)? If it is the latter, what format does the API expect the alias to be? E.g. '123456789', 'acct:123456789', 'acct:123456789@nxt', etc? Could it handle more complex alias URIs that bundle not only account number but also email address, web address, etc?